Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple language tag strings vs OSLC property cardinality #569

Open
berezovskyi opened this issue Mar 3, 2022 · 5 comments
Open

Multiple language tag strings vs OSLC property cardinality #569

berezovskyi opened this issue Mar 3, 2022 · 5 comments

Comments

@berezovskyi
Copy link
Member

@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
Copy link
Member Author

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
Copy link

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
Copy link

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
Copy link
Member Author

@berezovskyi
Copy link
Member Author

@frejfrej please feel free to report technical details on eclipse-lyo/lyo#261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants