[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-58) Expand oslc:valueType allowed values
[ https://issues.oasis-open.org/browse/OSLCCORE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61796#comment-61796 ] James Amsden commented on OSLCCORE-58: -------------------------------------- Extending OSLC primitive types could leading to OSLC v2.0 client breaking changes. For example, if an OSLC3 server happened to set a dcterm:created property to an xsd:date instead of xsd:dateTime, that would break an OSLC2 client since all components of dateTime are required and an xsd:date would not parse as a dateTime. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]