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: Re: [oslc-core] [OASIS Issue Tracker] (OSLCCORE-30) OSLC3 does not currently include oslc:representation in the resource shapes


oslc:representation has nothing to do with XML. It has to do with the
triples that are present in an RDF graph, e.g. in an HTTP request or

For example, suppose you are posting tables of data to a server. Then
the table cell contents should be oslc:Inline, i.e. the cell contents
are present in the RDF graph.

However, if you are posting a bug report and the bug report refers to
a failed test case, then the test case in not present in the RDF
graph, ie. it is oslc:Reference.

The OASIS PROMCODE TC is using oslc:representation in its shapes.

-- Arthur

On Tue, Aug 18, 2015 at 1:42 AM, OASIS Issues Tracker
<workgroup_mailer@lists.oasis-open.org> wrote:
> James Amsden created OSLCCORE-30:
> ------------------------------------
>              Summary: 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)
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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