1 All Rights Reserved, Copyright, Mikio Aoyama, 2014 OASIS OSLC PROMCODE TC Issues Discussed at The Ad Hoc Meeting during Innovate 2014 Memorandum Submitted to the Meeting Attendees: Mikio Aoyama, Tsutomu Kamimura, Sean Kennedy, Go Mizushima, Arthur Ryman, Steve Speicher, and Masaki Wakao Mikio Aoyama Nanzan University 2014/06/04, 2014/06/10 OASIS OSLC PROMCODE TC Issues Discussed at The Ad Hoc Meeting during Innovate 2014 Memorandum Submitted to the Meeting Attendees: Mikio Aoyama, Tsutomu Kamimura, Sean Kennedy, Go Mizushima, Arthur Ryman, Steve Speicher, and Masaki Wakao Mikio Aoyama Nanzan University 2014/06/04, 2014/06/10

2 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Issues under discussion  1: Simplify RDF vocabulary [Arthur]  Change to uni-directional vocabulary  One remaining bi-directional association between “Change” and “ManagedItem”: Supersedes/sededBy needs to simplify?  Solution: Use uni-directional association and vocabulary  2: Determine the proper name space [Sean, Robin Cover ]  OSLC Core name space policy by Sean    PROMCODE namespace = OSLC Core name space URI + /PROMCODE/ ? -> OK  Note: the namespace of OSLC Core is under discussion: OSLC or OASIS  Name of Prefix(Short-hand): Oslc_pmc?-> promcode

3 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Issues under discussion Change management scenario  3: Change management scenario [Wakao]  Along with the progress, actual*Time in WorkItem is set, Artifact is measured, Issues are submitted  WorkItem, etc.: project status change -> snapshot  WorkItem, etc.: of project plan change  ScopeItem: scope change  Out of PROMCODE’s scope, refer OSLC CCM  Eliminate “Change” from PROMCODE Domain Model  Comparison with CCM  Snapshot in PROMCODE is the same instance, only attributes changes  Version control uses property value

4 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Issues under discussion  4: Liaison to Core TC [Sean]  Join one member to Core TC: Aoyama  Bi-weekly 11:00 pm on Friday  5: Create an RDF Vocabulary Document [Arthur]  We need to create an RDF vocabulary document for all the terms defined by PROMCODE

5 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Issues under discussion  6: Create an OSLC Shape Document for PROMCODE Resources [Arthur]  The resources defined by PROMCODE should be documented by OSLC Resource Shapes  W3C Resource Shape 2.0, Feb [Arthur]   Open Services for Lifecycle Collaboration Core Specification Version 2.0 Appendix A: Common Properties, oslc:ResourceShape Resource  services.net/bin/view/Main/OSLCCoreSpecAppendixA#oslc_ResourceSh ape_Resource  Resource Shape defines: The Shapes specification provides for properties to be constrained by value type, range, and several other aspects. The term “shape” is used because it is often useful to visualize an RDF document as a topological object, namely as a graph consisting of nodes interconnected by arcs.  the contents and meaning of shape resources, and  how to associate shape resources with resources and services  Being able to specify with URI

6 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Proposed Revision to PROMCODE Domain Model measures ManagedItem +identifier +title +description ScopeItem +plannedSize +actualSize Measure +plannedValue +actualValue relates requiredBy 0..1 produces Measurement +date Person composedBy producedBy composedBy producedBy WorkItem +phase +plannedStartDate +plannedEndDate +actualStartDate +actualEndDate representedBy 0..1 Issue composedBy Artifact observes 6

7 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Issues under discussion  7: Explore Reuse of OSLC Estimation and Measurement Vocabulary (EMS)  Estimation-and-Measurement-Vocabulary/  Structure  Measurement ->(observe) measure は OK  Planned/Actual  Definition  EMS: Measurement is referred by URI  PROMCODE is defined by a subclass -> Referred  Use subclass of Measure or instance of resource  Based on rdf:type ?  If Core V2 uses rdf:type, PROMCODE should use rdf:type

8 All Rights Reserved, Copyright, Mikio Aoyama, 2014 Drafting OASIS Specification  Clarification of Issues  Related Concerns  ScopeItem and RM  ScopeItem is defined in PROMCODE  Artifact and Asset management  Asset management: Asset is a collection of Artifact  Vocabulary Relationship to Core  Person, Issue: Any type  Vocabulary Definition in OASIS OSLC  Independency(Modularity) of Specification  Clear Definition  Drafting the Specification

9 All Rights Reserved, Copyright, Mikio Aoyama, 2014 References [ 1] R. Cyganiak, et al. (eds.), RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation, 25 February 2014, concepts /#dfn-iri [ 2] R. Cyganiak, An RDF Design Pattern: Inverse Property Labels, Jun. 2006, property-labels/. [ 3] A. G. Ryman, OSLC Resource Shape: A Language for Defining Constraints on Linked Data,. [ 4] A. Rynam, Vocabulary Annotation Vocabulary, Sep. 2013, [ 5] A. Ryman, Resource Shape 2.0, W3C Member Submission, Feb. 2014,