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-6) Create an OSLC Shape Document for PROMCODE Resources

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

Kazuhiro Funakoshi commented on OSLCPROMCO-6:

Thank you, Arthur.
Clearly I had a major misunderstanding for Resource Shape.
In its Listing.4 (5.3.3 Example of a Shape for Bugs), property title and status are defined in the resource ChangeRequest, not the namespace of ChangeRequest.
So what we should do here, if we chose the naive way, is to define ResourceShape resource for each of our resources, and each of properties in each of them, right?
Then we can have isPartOf property for different subclasses.

Let me confirm the usage of ext:extendsShape. Consider we have WorkItem and ManagedItem, in ResouceShape of ManagedItem we write the base constraints and in ResourceShape of WorkItem we declare a Property ext:extendsShape to its base, ManagedItem, isn't it?

> Create an OSLC Shape Document for PROMCODE Resources
> ----------------------------------------------------
>                 Key: OSLCPROMCO-6
>                 URL: https://issues.oasis-open.org/browse/OSLCPROMCO-6
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Task
>            Reporter: Arthur Ryman
>            Assignee: Kazuhiro Funakoshi
> The resources defined by PROMCODE should be documented by OSLC Resource Shapes.

This message was sent by Atlassian JIRA

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