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: [OASIS Issue Tracker] (OSLCCORE-171) TRS base member predicate may introduce incompatibilities with TRS 1.0


James Amsden created OSLCCORE-171:
-------------------------------------

             Summary: TRS base member predicate may introduce incompatibilities with TRS 1.0
                 Key: OSLCCORE-171
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-171
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: TRS
            Reporter: James Amsden


The TRS 1.0 specification did not define a trs:Base class, but rather referred to the object of a trs:base predicate as an "RDF container". The Base Resources does not specify and rdf:type for the base resource. The members of this RDF container are captured using rdfs:member predicates. 

TRS 2.0 also does not define a trs;Base class, it also refers to the Base resource as the target of the trs:base predicate whose range is specified to be ldp:DirectContainer. The TRS 2.0 spec does define some properties of this unspecified resource type, so when I created the resource shapes for TRS 3.0, I added a trs:Base resource shape that oslc:describes ldp:DirectContainer in order to formerly reflect what was in the 2.0 specification.

It is not clear what TRS 1.0 implementations exist, but any TRS implementations done using eclipse/Lyo oslc-trs as a reference implementation may not be entirely compatible with TRS 2.0 as specified. It appears oslc-trs does utilize LDP, but it sues ldp:Container, not ldp:DirectContainer (a subclass), and uses rdfs:member, not ldp:member (ldp:member is a subPropertyOf rdfs:member). A TRS provider I recently implemented ([https://github.com/OSLC/iotp-adaptor)] using oslc-trs does produce ldp:Container with rdfs:member, and this base is consumed without any problem by IBM LQE. 

So it appears we have a mixture of container and member specifications that we may need to maintain for backward compatibility. 

 

 



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


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