[OASIS Issue Tracker] (OSLCCORE-58) Expand oslc:valueType allowed values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

James Amsden commented on OSLCCORE-58:
--------------------------------------

Perhaps the reasoning for the shapes specification to limit the RDF and XSD primitive types to the chosen subset was to reduce the change for interoperability issues. For example, if both xsd:int and xsd:integer were supported, different implementations could use xsd:integer while others are expecting the more constrained xsd:int. This could result in data values that cannot be shared across implementations. Since xsd:integer is larger than xsd:int, it would be the preferred integer type to avoid incompatibilities while supporting all possible integer values.

Nick also pointed out that there is a potential discrepancy between the OSLC vocabularies and the constraining shapes. The vocabularies do not constrain the primitive types while the shapes do.


> Expand oslc:valueType allowed values
> ------------------------------------
>
>                 Key: OSLCCORE-58
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-58
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: ian green
>            Assignee: James Amsden
>            Priority: Minor
>
> OSLC 2.0 defines the permitted values of oslc:valueType.  xsd:date is not one of them.  I've worked on one application that needed Date (not DateTime, which is permitted).  There is no suitable expression of a date as a dateTime, leading to a lack of expressiveness in OSLC shapes. 
> At the least, I should like to see xsd:dateTime being a permitted value in 3.0



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)