resolve collisions of dts and dct properties when nesting dublinCore object

[lueck]

There are still these collisions of dcterms and dts properties, when nesting the dublinCore property into the root RDF node.

Let's learn from the community, which managed to close distributed-text-services/specifications#280 !

[lueck]

The context from 8de745c cannot be used for JSON-LD framing. Using it, there is no dublinCore property at all.

Using Titanium JSON LD v1.7.0 on SEED XC 0.0.12.

[lueck]

Here is the problem: DTS Transformations for the collection endpoint and SEED DTS (both using SPARQL and other RDF-technologies) are using JSON-LD context not only as contexts on existing JSON-LD files, but also when framing JSON-LD files from RDF data, i.e. not only for declaring how to get RDF out of a JSON file, but also for getting RDF into the shape of an JSON file. We need this 2-way reversible process, not only one way. We need full conformance of the data represented in JSON with RDF (and LOD) technology.

1. context: JSON -> RDF graph
2. frame: RDF graph -> JSON

The collision of property names in DTS and DCTerms contexts (title, identifier, language) prevents using @nest on dublinCore, AFAIK. Solutions welcome!

The collision of property names seems to be a shortcoming of the DTS specs.

[lueck]

Workaround for users of DTS Transformations and SEED DTS: Make the dublinCore object a blank node or use the IRI from the document endpoint, and assert dublincore properties on this node.

In this solution, use context/modules/dct-obj.json instead of context/modules/dct-nest.json. This gives you full conformance to DTS specs.

Example SEED DTS configuration file:

https://scdh.zivgitlabpages.uni-muenster.de/doering-4esra/edition-4esra/collection.json