OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-promcode message

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

Subject: [OASIS Issue Tracker] (OSLCPROMCO-1) Simplify RDF vocabulary by eliminating redundant inverse properties

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37063#comment-37063 ] 

Shigeaki Matsumoto commented on OSLCPROMCO-1:

In our trial, all the triples are provided from a host, including inverse triples.
I guess it is the same as one document.

Since I can't find how to attach files in this disucussion, I'd like to extract two resources for example.

<promcode_pm:WorkItem rdf:about="workitem-42">
  <promcode_pm:produces rdf:resource="http://host_name/oslc-excel/rest/services/E4AA964B-37DF-48D3-9D48-652DAE3B552A/ARD_%E6%A9%9F%E8%83%BD%EF%BC%91"; /> 
  <promcode_pm:requiredBy rdf:resource="http://host_name/oslc-excel/rest/services/E4AA964B-37DF-48D3-9D48-652DAE3B552A/SIL3_%E6%A9%9F%E8%83%BD%EF%BC%91"; /> 
  <dcterms:type>Request for proposal</dcterms:type> 

<promcode_pm:Artifact rdf:about="http://host_name/oslc-excel/rest/services/E4AA964B-37DF-48D3-9D48-652DAE3B552A/ARD_%E6%A9%9F%E8%83%BD%EF%BC%91";>
  <dcterms:title>Function 1</dcterms:title> 
  <promcode_pm:measuredBy rdf:resource="http://host_name/oslc-excel/rest/services/E4AA964B-37DF-48D3-9D48-652DAE3B552A/MRD_%E6%A9%9F%E8%83%BD%EF%BC%91"; /> 
  <promcode_pm:producedBy rdf:resource="workitem-42" /> 
  <promcode_pm:producedBy rdf:resource="http://host_name/oslc-excel/rest/services/E4AA964B-37DF-48D3-9D48-652DAE3B552A/SIL3_%E6%A9%9F%E8%83%BD%EF%BC%91"; /> 

A 'workItem' resource refers to an 'artifact' resource with vocabulary such as 'produces'.
The artifact referes to the workitem with vocabulary such as 'producedBy'.

If bi-directional relation is always created,
I guess we can get the artifact by querying with {<workitem-42> :produces ?artifact}.
We also get the same artifact by querying with {?artifact :producedBy <workitem-42>}.

Because each result seem to be the same one, I couldn't understand UNION operation is necessary.

> Simplify RDF vocabulary by eliminating redundant inverse properties
> -------------------------------------------------------------------
>                 Key: OSLCPROMCO-1
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-1
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Improvement
>            Reporter: Arthur Ryman
> The current design has many pairs of mutual inverse properties. This makes writing SPARQL queries awkward since you have to include both. If you only have one way to express a fact then the queries become easier to write.

This message was sent by Atlassian JIRA

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