search

iodepo / odis-arch

Development of the Ocean Data and Information System (ODIS) architecture
https://book.odis.org/
31 stars 18 forks source link

book: schema:identifier usage #471

Open smrgeoinfo opened 4 weeks ago

smrgeoinfo commented 4 weeks ago

For the record....

Example from https://book.odis.org/thematics/expinst/index.html#example-person-graph

"identifier": {
    "@id": "https://orcid.org/0000-0002-2257-9127",
    "@type": "PropertyValue",
    "propertyID": "https://registry.identifiers.org/registry/orcid",
    "url": "https://orcid.org/0000-0002-2257-9127",
    "description": "Optional description of this record..."
  },

based on recent discussions, the @id identifies a graph node (analogous to a record in a database) that is about a PropertyValue. Use of the orcid (identifier for a person) doesn't seem appropriate; with the @type, wouldn't the implication be that the thing identified by https://orcid... is a schema:PropertyValue

The propertyID is (according to https://schema.org/propertyID) an "identifier for the characteristic represented by the property". In this case wouldn't the property be 'person identifier'. The string that's there identifies an identifierScheme description, like identifierScheme or identifierType in DataCite. Schema.org does not have a slot to specify this as far as I can tell, so I understand why its there, but there should be some note that the usage is a ODIS convention.

I expected to see something like the identifier token in the schema.org value: "value":"0000-0002-2257-9127" or "https://orcid.org/0000-0002-2257-9127".

pbuttigieg commented 6 days ago

yes, that's to be updated, thanks for spotting

an exception would be if the HTML of the @id target had JSON-LD/schema.org embedded in it, but I don't think ORCID does that

pbuttigieg commented 6 days ago

yes, that's to be updated, thanks for spotting

an exception would be if the HTML of the @id target had JSON-LD/schema.org embedded in it, but I don't think ORCID does that

ORCID doesn't - would be very good if it did, and one didn't have to use a priced API for "open" data