Terms - Githubissues

@ptsefton It was really great to hear about your work and how OLAC has been foundational to your work.

I had two comments which I thought I would jot down so that future reference would be possible.

For roles, it might be good to think about using MARC relator roles instead of OLAC roles. Their Linked data IDs can be discovered in the LOC linked data portal here: https://id.loc.gov/search/?q=cs:http://id.loc.gov/vocabulary/relators all of the terms that LOC has are available here: https://id.loc.gov/search/ Note that some of the documentation at OLAC automatically inferes canonical equivalence and no SKOS exact match value is needed.
With regards to typing and schema.org I'd be very interested in looking at some of your use case JSON-LD files which demonstrate schema.org. There has been a lot of discussion about proper typing of values in fields and controlling for that — hence my question. Some examples of where people have challenges are when schema.org calls for a type to be an object (essentially requiring an extra @ like follows for address with type PostalAddress, another thing has been dates. My team ran into date validation moving from XML to schema.org with date format checking in XML needing to be custom implemented because the dates between dublin core and schema.org needed to be in different standards. Another issue I have heard constraining schema.org application in some cases has been how things are defined in the definition files, which are kept, if I recall correctly in SKOS. This means that in some places in schema.org there is a lot of flexibility while in others there are underlying assumptions which don't always make it to the front page of the schema.org documentation.

"@context": "https://schema.org",
  "@type": "Person",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Seattle",
    "addressRegion": "WA",
    "postalCode": "98052",
    "streetAddress": "20341 Whitworth Institute 405 N. Whitworth"
  },

Great work!

Language-Research-Technology / language-data-commons-vocabs

Terms #7