Have played around a little and without any limitations in terms of backward compatibility, we can add
"@Context": "http://purl.org/dc/terms/"
to all SpecIF data sets without problem; the SpecIF schema v1.1 supports it as is. This would take away any ambiguity where our property names come from.
There are some interesting questions ahead, for example using @id, @type as well as additional namespaces like schema.org or INCOSE for systems engineering terms.
Have played around a little and without any limitations in terms of backward compatibility, we can add "@Context": "http://purl.org/dc/terms/" to all SpecIF data sets without problem; the SpecIF schema v1.1 supports it as is. This would take away any ambiguity where our property names come from.
There are some interesting questions ahead, for example using @id, @type as well as additional namespaces like schema.org or INCOSE for systems engineering terms.
This is for v1.2 or v2.0 ...