<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Stéphane, <div><br></div><div>indeed, this is a bit of a tricky issue, since accurately acknowledging attribution or authorship is a key aspect of science ethics. </div><div><br></div><div>My first answer is to clearly identify what contribution is attributed to whom. I mean: the EPNcore or ObsCore table metadata should be very explicit on what it is, and how to has been produced. The title and description has to be very clear on the content and the scope. </div><div><br></div><div>With your example:</div><div>The EPNTAP service is a "Curated catalogue of planetary observations by HST". The EPNcore metadata has been produced by Erard, et al. The original datasets used to produce the metadata are provided by the NASA/MAST database (or any other that has been used). <br><div><br></div><div>The metadata in the Registry concerns the catalog metadata, and should (must?) contain reference to the progenitor data if required, e.g., with relation like "is-metadata-for" linking to the DOI (or any identifier) of the original dataset (possibly included as a provenance statement)</div><div><br></div><div>So to me:</div><div>- the metadata of the EPNcore/Obscore table should relate to the metadata and not the original data, </div><div>- the relation to the source data should be explicitly stated and presented, both on the service description, as well as in the registry metadata.</div><div>- the EPNcore/Obscore table landing page should propose explicit citation policies ("how to cite this metadata", "how to cite the underlying datasets") </div><div><br></div><div>Cheers</div><div>Baptiste</div><div><br></div><div><br></div><div><br></div><div><br><blockquote type="cite"><div>Le 2 févr. 2025 à 11:01, Stéphane Erard via semantics <semantics@ivoa.net> a écrit :</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hello<div><br></div><div><br></div><div>I'm reviving an old request from the Solar System community but more general in scope:</div><div>What are the c<span style="font-family: Verdana; font-size: 12px;">ommon practices concerning references to data services? How do we cite creators of content (ie: </span><span style="font-family: Verdana; font-size: 12px;">data)</span><span style="font-family: Verdana; font-size: 12px;"> vs services (ie, very often: a metadata table)? Can there be 2 different roles? - this is a recurring request from our providers, and a sensitive one.</span></div><div><span style="font-family: Verdana; font-size: 12px;">Example: I'm maintaining an EPN-TAP service identifying planetary data from the HST catalog. Creating the metadata table is a significant work which deserves identification and involves a responsibility; but I can't pretend I've created the data. How do I call my role there?</span></div><div><span style="font-family: Verdana; font-size: 12px;"><br></span></div><div><span style="font-family: Verdana; font-size: 12px;">VESPA distinguishes 3 roles, following current practices: </span><span style="font-family: Verdana; font-size: 12px;">Creator, Contributor, Publisher</span></div><div><span style="font-family: Verdana; font-size: 12px;"><div>But there is an obvious ambiguity with Creator that needs to be addressed.</div><div><br></div><div>Cheers</div><div>Stéphane</div></span></div></div></div></blockquote></div><br></div></body></html>