[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=61797#comment-61797 ] 

James Amsden edited comment on OSLCCORE-60 at 2/18/16 9:10 PM:
---------------------------------------------------------------

OSLC currently does not support rdf:langString language tags, string literals are only xsd:string. If a language tag is needed, then an rdf:XMLLiteral can be used and the language tag can be included in an XML attribute.

Adding rdf:langString, and interpreting multiple values with unique language tags as exactly one could be a client breaking interpretation for OSLC v2.0 since a client might be expecting a single value, and get back multiple values, each with a separate language tag.

So I don't think this is an issue.

I think I misunderstood the problem in this comment - a RDF resource could have assertions whose object values are plan literals with language tags, OSLC certainly supports this since its just RDF. 

The issue is when a there are multiple assertions for an RDF property whose object values are plan literals with language tags, and the resource has an applicable shape that specifies the property should have at most one value, does the resource satisfy the constraints of its applicable shape or not.



was (Author: jamsden):
OSLC currently does not support rdf:langString language tags, string literals are only xsd:string. If a language tag is needed, then an rdf:XMLLiteral can be used and the language tag can be included in an XML attribute.

Adding rdf:langString, and interpreting multiple values with unique language tags as exactly one could be a client breaking interpretation for OSLC v2.0 since a client might be expecting a single value, and get back multiple values, each with a separate language tag.

So I don't think this is an issue.


> 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)