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=37033#comment-37033 ] 

Arthur Ryman commented on OSLCPROMCO-1:
---------------------------------------

@Sean The natural grammatical sense is to relate a dependent artifact to the artifact it depends on because the dependent artifact is normally created after the artifact it depends on. The dependent artifact is the subject and the artifact it depends on is the object. 

For example, consider a parent-child relation. The child is created after the parent. It is natural to choose hasParent, e.g. Luke hasParent Darth. With this choice, the triple "Luke hasParent Darth" would be added to the document describing Luke when that document was created.

In impact analysis, the terms upstream and downstream are used to describe the dependency relation. For example, a requirement is upstream from a test case since normally a test case is created to validate some requirement. Therefore, the preferred relation is "validates", and a triple like "testcase-137 validates requirement-42" would be added to the document for testcase-137.

> 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
(v6.1.1#6155)


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