Feedback and open issues for the Core Extensions for PLM

Questions and Answers

Q1 CLOSED at V1.0: What if my tool provides a versioned container ?

ANSWER: The resource version identifies the versioned container

Q2 CLOSED at V1.0 : What if my tool doesn’t indicate predecessors ?

ANSWER: Indication of succession is a May.

Q3 OPEN at V1.0: How to identify the versioning behaviour of a resource ?

ANSWER: base will have a minimal resource shape, infer from a resource types with no “isVersionOf”, or “replaces”. Multiple approaches today – Service provider doc, Query Header.

NOTE: Request guidance from Core.

Q4 OPEN at V1.0: What is the preferred use of backlinks for “hasVersion” ?

ANSWER: Preferred approach is not to use backlinks.

NOTE: hasVersion is not included in the specification.

Q5 OPEN at V1.0: Is there a better dcterms property for succession ?

ANSWER: dcterms :replaces is ambiguous, however its definition includes succession so it is proposed as the most applicable term

Q6: CLOSED at What if the resource supports versioning but has no concept of a base resource ?

ANSWER:A base resource is an optional concept, if a resource version does not have a hosting base resource then isVersionOf is used between ResourceVersions?

NOTE: This approach needs clarification by examples

Q7: CLOSED at V1.0 What is a version is hosted by multiple base resources, in the case products when a product version is a member of e.g. different product families

ANSWER: isVersionOf refers to the base resource which created the Version. The recommended approach is that the association of a product version with multiple "hosting" products, e.g. family concepts, is handled through the ProductView? concept. So for a given ProductVersion? , multiple ProductViews? of the hosting product concepts would have hasPart associations linking back to the ProductVersion? of note

Q8: CLOSED at V1.0 What if a resource doesn’t support versioning, a resource factory for a ResourceVersion? as a SHALL is over stating the need ?

ANSWER: A creation factory service for a ResourceVersion? is an optional MAY. Note that the version creation has an open issue below.

Note: The Core extensions Spec has been updated.PM Spec draft not updated

Items to close

ISSUE 1. PROPOSAL at V1.1 Comment from Olivier Berger 17/11

http://open-services.net/pipermail/oslc-plm_open-services.net/2011-November/000066.html

ISSUE 2 PROPOSAL in V1.1 RDFType of Version

From John Arwe on resource types 22/11- 13/12 The proposal is to be adopted and then solicit feedback

http://open-services.net/pipermail/oslc-plm_open-services.net/2011-November/000065.html

and follow on by Mike Loeffler

http://open-services.net/pipermail/oslc-plm_open-services.net/2011-December/000069.html

ISSUE 3 OPEN How to create a new version

Description how to create a version- 13/12 an update will be made to the section on Create Version

Comment 3 from John Arwe on createVersion service 22/11

http://open-services.net/pipermail/oslc-plm_open-services.net/2011-November/000065.html

ISSUE 4 OPEN Comment on and show relationship to the SCM Spec- to be scehduled

ISSUE 5 OPEN RDF examples need updating for V1.1

ISSUE 6 Lyo examples need to be shown

ISSUE 7 Add description and examples of View