New Pattern: Samples

[pbuttigieg]

Working with the Sampling Nature RCN, and leveraging work done by Open Context on JSON-LD exchange of sample (meta)data (e.g. this record), we should create a pattern for samples using schema.org semantics and test it against some of the examples gathered during the RCN meetings.

First instinct - develop from the Product type and nest domain-level semantics in additionalProperty keys. We've alraedy done the groundwork for this here, so it's a question of adapting this to some sample examples from OpenContext

xref #309 #125

[pbuttigieg]

The exchange of some sample metadata will be subject to a wide range of license and restriction clauses. Be prepared for CARE alignment and more advanced provenance tracking in this pattern, which can be generalised across others

[pbuttigieg]

@fils should the PR target the thematics in the book directory or is the new publishing flow instantiated? Where should I create the pattern for the PR?

[ekansa]

For archaeological materials from Open Context (https://opencontext.org), we want to make sure that aggregators (search engines, ecommerce players) DO NOT interpret archaeological materials as items involved in commerce. We actively want to work AGAINST archaeological materials circulating in commerce (the antiquities trade is very destructive), so there needs to be some clear signal in the metadata that such materials are not commercially appropriate.

[pbuttigieg]

For archaeological materials from Open Context (https://opencontext.org), we want to make sure that aggregators (search engines, ecommerce players) DO NOT interpret archaeological materials as items involved in commerce. We actively want to work AGAINST archaeological materials circulating in commerce (the antiquities trade is very destructive), so there needs to be some clear signal in the metadata that such materials are not commercially appropriate.

@ekansa many thanks - there are properties where conditions of access and usage parameters can be defined.

What sort of statement or link would you like as the value of such a field?

[smrgeoinfo]

there's a proposed schema.org implementation of the iSamples metadata scheme, its in a branch in our metadata Github repo: https://github.com/isamplesorg/metadata/tree/develop/notes/schemaOrg. Its based on schema:Thing, and uses properties from a variety of entities, so the validator throws some warnings, but no errors.

[smrgeoinfo]

the mapping is also documented here: https://docs.google.com/document/d/1EZDeulvglKVphlo8cHkZAQ4xYr7-yWMF

[pbuttigieg]

@datadavev - tagging you for the iSamples federation, see also #388

[ekansa]

@pbuttigieg is there anything you'd like from me to update with Open Context itself?