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

Martin Pain commented on OSLCCORE-58:
-------------------------------------

Given the recent discussion about shapes (including the shapes defined in the specs), wouldn't a dcterms:created property with a value whose type was xsd:date already be allowed? It might not be what's specified in the shape, but if the occurs in the shape is zero-or-one then the resource is free to have zero occurrences with type xsd:dateTime, and one occurrence (which is not specified by the shape) of type xsd:date.

Well-written RDF clients should check that the types of values are what they expect, and ignore it if they're not - although I expect most OSLC clients are not well-written RDF clients.

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