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

James Amsden commented on OSLCCORE-60:
--------------------------------------

Nick, you mean there are cases where a property constrained to be an xsd:string will have a language tag? If so, that would appear to be invalid since xsd:string can never have a language tag. Rather the string would need to be CDATA in an XML element that has a lang attribute. This is what RDF XMLLiteral supports and these are commonly used in OSLC resources.

If there is some other convention for xsd:string then it would need to be formerly defined in order to support interoperability.

In any case, if a property is of type XMLLiteral, and has cardinality exactly-one, then there could still be multiple values with different lang attributes, so your proposal is still valid.


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