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

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

Proposal:

1) Treat OSLC cardinality as applying solely to plain literals.
2) Allow OSLC data providers to include additional literals with language tags.
3) Recommend that OSLC clients that don't understand language tags should only process plain literals.

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