[OASIS Issue Tracker] (OSLCCORE-60) Clarify role of language-specific literals

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61804#comment-61804 ] 

David Honey commented on OSLCCORE-60:
-------------------------------------

I agree with Nick. The obvious use case for cardinality constraints is that a client is looking for a maximum of one literal for some client locale. If the client is not interested in language specific literals, they will want one xsd:string value. If the client is interested in language specific literals, they will want to try to get one literal for their client locale, and if none exists, use a maximum of one xsd:string value. This is such a common usage pattern generally, I think OSLC should support it.

> Clarify role of language-specific literals
> ------------------------------------------
>
>                 Key: OSLCCORE-60
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-60
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: ian green
>            Assignee: James Amsden
>
> When we indicate cardinality of 1 ("exactly one") in a shape, what does this mean from the point of view of language-tagged-strings?  For example,
> :r1 a oslc:Requirement;
>      dcterms:title "my colourful requirement",
>                          "my colourful requirement"@en-GB,
>                          "my colorful requirement"@en-US,
>                          "sorry, don't speak french"@fr.
> May also be differences from RDF 1.0 to RDF 1.1 in this area.
> Where dcterms:title has cardinality 1 on a Requirement.  Do we mean "cardinality modulo language tagging"?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)