[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-109) Query spec describes rdf:resource in example
[ https://issues.oasis-open.org/browse/OSLCCORE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68079#comment-68079 ] James Amsden commented on OSLCCORE-109: --------------------------------------- This example would be a lot clearer if it 1) used existing CM and QM domain vocabulary terms, and 2) showed the query results. qm:testcase is intended to be a property of cm:bug. So the query is attempting to follow a property of a cm resource defined by a qm vocabulary using a specific URI for the target test case. All these examples should be redone using existing, common OSLC domain vocabularies, and should show the results. > Query spec describes rdf:resource in example > -------------------------------------------- > > Key: OSLCCORE-109 > URL: https://issues.oasis-open.org/browse/OSLCCORE-109 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Task > Components: Query > Reporter: David Honey > Assignee: James Amsden > > https://open-services.net/bin/view/Main/OSLCCoreSpecQuery has the following text for an example: > "Property values will often refer to or be other resources (in RDF/XML the rdf:resource attribute is used to identify the resource). Suppose bugs are linked to testcases using a property name qm:testcase where the prefix qm: stands for the URI http://qm.example.com/ns. The following query finds all bugs that are linked to testcase http://example.com/tests/31459: " > I don't think it's appropriate for the spec to define an arcane referencce to rdf:resource that is solely a feature of RDF/XML serialization. -- 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]