[OASIS Issue Tracker] (OSLCCORE-30) OSLC3 does not currently include oslc:representation in the resource shapes

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

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

James Amsden commented on OSLCCORE-30:
--------------------------------------

I have added it back into the core-vocab.ttl file. The only use of oslc:valueType of LocalResource are in the OSLC2 discovery resources which currently don't have shape.ttl files. They will be added to Discovery-shape.ttl


> OSLC3 does not currently include oslc:representation in the resource shapes
> ---------------------------------------------------------------------------
>
>                 Key: OSLCCORE-30
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-30
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> Resource Property of Resource Shape has a oslc:representation property that specifies how the property should be expressed in RDF/XML: inline, reference or either. The purpose of this was likely to control the structural format of the RDF/XML documents to facilitate simplified parsing with XML DOM or XPath by clients that don't want to use an RDF/XML parser. 
> The oslc:representation property is not include in any of the OSLC3 shapes, and is not included in the Constraints sections of the specifications generated by ReSpec.
> This may create compatibility issues with OSLC2 clients that are expecting the RDF/XML to be in a particular structural format. Although this is a bad practice, it may be commonly used. We should consider if this property needs to be retained.



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