OASIS OSLC PROMCODE TC Meeting Note – Jun, 10
Attendees
Attendees [A: Absence]
- Mikio Aoyama (Nanzan University) TC Chair
- Kazuo Yabuta (Fujitsu Limited) Member
- Hiroyuki Yoshida (Fujitsu Limited) Member
- Tom Kamimura (IBM) Member
- Sean Kennedy (IBM) Member
A Robert LaRochelle (IBM) Member
- Arthur Ryman (IBM) Member
- Masaki Wakao (IBM) Member
- Fan JIANG Funakoshi (NEC Corporation) Member
A Shigeru Hosono (NEC Corporation) Member
- Nobuhiko Kishinoue (NEC Corporation) Member
- Shigeaki Matsumoto (NEC Corporation) Member
A Lonnie VanZandt (Sodius SAS) Member
Discussions
1. Ad-hoc Innovate Meet-up
- Went through the minutes posted into mailing list by Wakao
- https://www.oasis-open.org/apps/org/workgroup/oslc-promcode/email/archives/201406/msg00009.html
Comments:
- Issue 8: Relationship with existing resources in other domains
- We should have use cases how PROMCODE resources are exchanged and referred.
- After that, we should reconsider the resource type again.
- May be able to utilize a quad file and make each triple scope to the document to exchange.
- Small team will make draft use cases and post to TC. We will discuss based on the draft use cases.
- Issue 5: Vocabulary Document
- Still two links (produces and producedBy) between WorkItem and Artifact in the specification.
- We need both links. The semantics are different from each other.
- In that case, we should have more explicit term.
- dcterms:partOf might be better than promcode:composedBy
- relationship between Issue and ManagedItem:
- Candidates: need to be determined – Arthur will open an Issue
- dcterms:related : too generic
- Issue promcode:involves ManagedItem
- ManagedItem promcode:raises Issue
- Issue promcode:raisedBy ManagedItem
- WorkItem: phase
- PROMCODE: String vs. E&M: URI
- Resource for contract between Supplier and Acquire
- What is the top level resource for that?
- Candidates: need to be determined
- ScopeItem
- New resource type Plan or Contract
- project property
- Artifact
- How about having a link property to actual content
- Issue 7: Measurement
- Couple of differences with definitions in E&M.
- Combining plan and actual
- dcterms:type
- Conceptual measure vs unit of measure
- Arthur will explain more in the next meeting
- E&M spec status: Not finalized because implementation has not bee done. Performance & Monitoring spec adopted the vocabularies.
Next Meeting: Next on Jun 24, 8pm EST. Jun 25, 9am JST