OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Nick Crossley commented on OSLCCORE-60:

I do not know of tools that use XMLLiteral to embed language attributes in the way you describe - the result would be unnecessarily hard to parse. XMLLiteral is commonly used in OSLC properties to allow rich text markup for display, not (in my experience) for language tags. I am not aware of any tools that *currently* publish OSLC-defined string properties that use both tagged and untagged strings; the examples I mentioned in my previous comment were in vocabularies. However, we have had discussions about having tagged strings for titles, names, descriptions, and comments in some tools, and the fact that OSLC does not correctly support this was not considered - had it been, we would have considered it a bug with OSLC!

In retrospect, OSLC should have defined an oslc:valueType of 'any string' that would include xsd:string and rdf:langString.  If we stick to the strict interpretation of xsd:string, then I would argue for adding this new value in 3.0 - but it might be difficult to go back and redefine many existing OSLC shapes to use this new value in place of xsd:string.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]