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

Nick Crossley commented on OSLCCORE-60:
---------------------------------------

I believe the above interpretation of OSLC 2 is too strict. It is true that rdf:langString is not one of the documented oslc:valueType property values, so you cannot constrain a string property to be a tagged string.

While it is true that xsd:string and rdf:langString are completely different types (one of the absurdities of RDF), there is plenty of existing string data that uses both tagged and untagged strings for the same property - including data published by tools that have OSLC clients and servers. As a result, I believe we would only be admitting existing practice by explicitly describing this use of multiple languages for a property with an occurrence of zero-or-one, or exactly-one.


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