-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linked Art / Schema.org mapping? #516
Comments
Definitely yes! We're mapping our internal Bibframe representations of library resources out to schema.org already and have ambitions to do the same for Linked Art in the future. |
Some basic mappings to get the ball rolling: Baseline
Person
Group
Place
Type / Language / Material / CurrencyI can't find a good mapping beyond Thing. There is a Language class, but it has no features beyond those of Thing. |
|
DefinedTerm -- I was looking for a way to have a There's a closer fit in terms of properties: https://schema.org/Taxon but not definition as it's explicitly about biological classification. |
Is |
I think greater is more for the relationship between siblings -- the concept of "impossible" is somehow greater than the concept of "easy", but both are narrower than "difficulty" What about CreativeWork and isPartOf ? |
Not mapping questions but...
|
RE: Could we use AAT page URLs for Types and then use |
Yes |
A little late to the conversation, but I wanted to mention that we have a workflow that maps linked art to schema.org in (a roundabout way) at the Getty, both in our museum collection pages and archival research collections. But we would love a less ambiguous mapping! We would be most interested in JSON-LD -> JSON-LD mapping. We index some fields from our linked art LOD to an ElasticSearch index then generate schema.org json from those indexed documents -- below is cribbed from our implementation of Schema.org's Python helpers. We use the following schema types:
Here's some relevant parts of the code, though much of this repeats what has already been discussed above.
|
Just checked our <> a schema:DefinedTerm ;
schema:hasPart <> ;
schema:isPartOf <> ;
schema:sameAs <> ;
schema:name "" . |
And just ignore the "expected" domain and range of hasPart / isPartOf? They expect CreativeWork, but DefinedTerm is an Intangible. That's probably the best we can do, beyond asking for another property to be added to schema. |
Looks like we should refactor our implementation a little. Also logging here that the Schema.org initiative have twice decided against extending the domain of |
Should be able to round-trip data back to linked art, or understand where there are challenges. |
A little bit more noodling on the
Can we (ab)use composite classes so that broad <http://vocab.getty.edu/aat/300033618>
a schema:DefinedTerm ;
schema:name "Painting" ;
schema:inDefinedTermSet <http://vocab.getty.edu/aat/300133025> .
<http://vocab.getty.edu/aat/300133025>
a schema:DefinedTerm, schema:DefinedTermSet ;
schema:name "Work of Art" .
schema:inDefinedTermSet
schema:additionalType "http://www.w3.org/2004/02/skos/core#narrower"^^schema:URL . Actually |
What about ...
|
Object StrawpersonBaseline plus...
Missing:
|
Work StrawpersonBaseline plus ...
|
Digital Object Strawperson/type = CreativeWork, DataSet
|
Collated the mappings as they stand here: https://deploy-preview-540--linked-art.netlify.app/cookbook/mappings/schema.org/ |
Noting from discussion with @krpage and @workergnome (and others) that the Schema.Org representation needs to link to the Linked Art representation (and isn't explicit in the above mapping) |
Is the mapping ready to be deployed to https://linked.art/cookbook/mappings/schema/ ? |
At Yale we would benefit from a mapping from linked art into schema.org to generate and embed into our LUX entity pages.
e.g. if we could transform the incoming linked art into HTML and schema.org's json-ld to be embedded within the page, when google crawls it (or other systems), the schema.org structured data would make that indexing much stronger.
This seems like a useful result for the community, not just Yale, and something we could collaborate on?
The text was updated successfully, but these errors were encountered: