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

Hiroyuki Yoshida commented on OSLCPROMCO-1:

I've just uploaded a document on Domain Model Revision at 
(I wanted to attach it to this issues but couldn't find the functionality. Please tell me a right way if any).

The first page shows the current PROMCODE Domain Model included in the base document of our specification.
The second page shows a proposed revision of it based on the discussion of this issues and the local discussion with Wakao-san, Matsumoto-san, Yabuta-san, and Aoyama-san.

Changes are as follows:
Every association has only one navigable end.
The navigability is basically from the depending object to the depended object.
All names of associations are removed and all asscociations themselves are named instead.

Note that there are intentionally two associations between Artifact and WorkItem.
A WorkItem may produces several Artifacts while an Artifact may requires several Workitems.
These associations are not inverse twins of identical one.

I think more discussion should be required:
Many associations are named as xxxxxedBy  because we cannot find appropriate verbs as non-native English speakers. 
Please suggest better terminology.

A Measurement is essentially a link from a Measure to an Artifact and it is represented as a resource because it has some attributes..
Similarly a Change is a link from a superseding ManagedItem to a superseded ManagedItem and represented as a resource..
In such cases which direction of links is better?
(1) Artifact <- Measurement -> Measure / ManagedItem <- Change -> ManagedItem
(2) Artifact <- Measurement <- Measure / ManagedItem <- Change <- ManagedItem

> 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]