search

oslc-op / oslc-specs

OSLC OP specifications and notes
https://open-services.net/specifications/
25 stars 10 forks source link

Multiple language tag strings vs OSLC property cardinality #569

Open berezovskyi opened 2 years ago

berezovskyi commented 2 years ago

@frejfrej reported that certain Jazz ETM shapes have OSLC Shape Property definitions with more than one title (one without a language tag and multiple tagged with different language tags).

berezovskyi commented 2 years ago

We should make use of https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language to let users indicate the subset of languages they are interested in to keep the response short.

DavidJohnHoney commented 2 years ago

I think the original intent is that for any string property with a maximum cardinality of 1 that: 1) There should be a maximum of one plain-literal value 2) For language tagged literals, there should be a maximum of one such value for any given language.

Example of valid usage: Property name has dcterms:title with plain literal, plus one English tagged literal, plus one French tagged literal, plus one German tagged literal.

Examples of invalid usage: Property name as dcterms:title with two plain literal values. Property name as dcterms:title with two plain French tagged literal values.

DavidJohnHoney commented 2 years ago

However, there are some other concerns: For shape names and property names, the spec says XMLLiteral. That would preclude the use of palin literals or language tagged literals.

berezovskyi commented 2 years ago

See https://www.w3.org/TR/shacl/#UniqueLangConstraintComponent

berezovskyi commented 2 years ago

@frejfrej please feel free to report technical details on https://github.com/eclipse/lyo/issues/261