Closed VladimirAlexiev closed 9 years ago
my preference is that people assign IRIs and annotate it with the name of the agent. that way, it can be later linked with orcid or some other identifier.
@AlasdairGray what do you think?
You could split to props and express the preference, eg dct:creator IRI SHOULD The preference is to express creators & contributors as a resource, this way they can be later linked with a resource from another dataset (eg ORCID) dc:creator xsd:string MAY
My preference is also for an IRI. However, there is no restriction on the datatype of dct:creator
and it is often used with just a string. That is why we have the entry in the table in that form.
We discussed this in the telco and decided to limit the values to IRIs (removing xsd:string as an option).
On Mon, Sep 22, 2014 at 5:08 PM, Alasdair Gray notifications@github.com wrote:
My preference is also for an IRI. However, there is no restriction on the datatype of dct:creator and it is often used with just a string. That is why we have the entry in the table in that form.
— Reply to this email directly or view it on GitHub https://github.com/joejimbo/HCLSDatasetDescriptions/issues/78#issuecomment-56387446 .
M. Scott Marshall, PhD MAASTRO clinic, http://www.maastro.nl/en/1/77/strategy-plan.aspx http://radiomics.org http://eurecaproject.eu/ http://semantic-dicom.org/ http://www.linkedin.com/pub/m-scott-marshall/5/464/a22
We need to ensure that the sentence is removed from §6.2.5 as well.
there is no restriction on the datatype of dct:creator and it is often used with just a string
The definition in DCTerms is:
dcterms:creator
a rdf:Property ;
rdfs:isDefinedBy <http://purl.org/dc/terms/> ;
rdfs:range dcterms:Agent ;
rdfs:subPropertyOf <http://purl.org/dc/elements/1.1/creator>, dcterms:contributor ;
Although it's not declared an owl:ObjectProperty, the rdfs:range shows that it is so. Whether some people use it incorrectly is a different question. Your document should not promulgate incorrect usage.
Sec 5 says:
But DCT: http://purl.org/dc/terms/ says
So I don't think using xsd:string is quite correct. If you want to allow xsd:string, use DC Elements (dc:creator&contributor)