- 🇺🇸United States smustgrave
With RDF since removed from core wonder if this is still a valid task?
As described in the JSON-LD feature explanation, JSON-LD uses URIs for properties. In order to use JSON-LD as we want to, we need to create URIs for our fields and properties.
For example, field_tags might have a URI such as http://example.com/site-vocab/node/article/field_tags
It would be nice to use a consistent URI for certain universal properties such as UUID. However, determining which properties are universal properties and which are custom to the site is difficult. It may be better to just create a URI on the site for each term.
At the very least, we want to expose this for field instances and entity subtypes (bundles). We may also want to expose schema information for field types and entity types. These could have a subProperty and subClass relationship, which could possibly enable reasoning across sites that use the same field types.
We also need to have two vocabularies for the two supported domain models.
// Prefix = site
http://example.com/site-schema/
Terms from Drupal-specific domain model:
// Temp prefix = site-cs
http://example.com/site-schema/vnd-drupal/
--or--
http://example.com/site-schema/content-staging/
Common domain model:
// Entity type
site:entity/node
// Entity subtype
site:entity/node/article
Drupal specific domain model:
// Entity type
site-cs:entity/node
// Entity subtype
site-cs:entity/node/article
Common domain model:
site:fields/node/article/field_body_value
site:fields/node/article/field_body_summary
Drupal specific domain model:
site-cs:fields/node/article/field_body
site-cs:field_types/text_textfield
site-cs:field_types/text_textfield/value
site-cs:field_types/text_textfield/summary
site-cs:field_types/text_textfield/format
Postponed: needs info
9.5
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
With RDF since removed from core wonder if this is still a valid task?