1. Welcome

Attendees: Gray, Jim, Sanjay, Rainer, David, Steve, Carlos, Pascal, Iain Dodds, Mike

Apologies: Nick

Welcome to Carlos Ferreira of IBM Rational as RELM jumpstart lead focusing on integrations, and Iain Dodds of GM.

2. Update on the reference model availability and feedback

Summary of site updates from Gray

3. Resource prototyping using RIO / eclipse Lyo

9/8 ACTION: Jim will update and inform Mike/Gray - done 15/8

Steve infra being setup at eclipse.org.

Jim refactor code base, including use of Mike's input

SF trunk needs review, copyright notice update

Shift to JAX when move to eclipse repository

Note: Gray has trouble with the Firefos5 and IE8 with the latest build (UI Creator not save) resort to Chrome

Mike walked through his demo of the proposed extensions:

(Recording failed apologies to all.

Using the rm server

Multiple versions and view definitions

Represent the ref model

Create all as requirements

Q? req, req version, req view definition

isViewOf

hasPart

nesting of view

Market region is a base req with no revision

Q? Use of ShortTitle?

Requirement text on the Req revision

SysML Nested classifier for structure links to the view

view isversionOf with a nested Classifier to the SysML? namespace

Structure is carried by the view

EU an US views are versioned

Variant expression applied to the link between two view (Parent and child)

Effectivity handled similarly

Q1: Variant expression on the link (vs object). How are variants resolved ?

Resource resolves option e.g. Market region = US

Q2: what is the syntax of the variant expression

Applys from the PLM XML schema ns. Teamcenter basis.

Q3: is View of Version cf dcterms

based upon dc terms subject not dcterms isVersionOf

Q4: multiple versions of the same resource, intend that URI changes when version changes. Deliberate due to higher ceremony of versioining in PLM. If always want latest then point to a base resource

View definition of req poi nts out to sub-requirements and points to the revision of the req(62)

its a version of req base version (63)

each version has a view with a URI

Q5: are view-definitions versioned

No (isn't inconsistency

Q6: What is effectivity?

Where and when are the options valid.

Version has impact on other resources when chosen options have been evaluated. Effectivity includes revision (like lot) and variants.

Q7: Why need configuration in this interface ?

This is for demo. Could extend to show in Lyo project.

Q8: is the view configured ?

No its unconfigured as 2 views are shown

Q9: Has Part ?

Child views

Q10: is the lack of versioning on a view definition inconsistent ?

Force the version (this is a business rule)

Q11: How get access to the repository ?

Zip the repo folder. Need to use localhost.

Q12: How to assess the versioning approach proposed ?

David has seen 2 approaches - Item has version and repo is versioned (resource in a repository version as SVN). Mike sees as complementary and possible to run in parallel.

Q13: CM Lyo to support

Use different ports and link through repo. UI not readily support.

Need a Web UI colleague to support. Drag and drop link would be great, or involke

Remarks: Diagrams to assist understanding would be helpful

Typically there is a release process around snapshot which is locked, basically to branch the items that are changing (copied to a delta)

Use the PLM Importer code

Challenge of alignment

Propose to produce a summary of the resource structure aligned to the ref Model.

4. Application and extension of the reference model

Gray has posted sequence diagram for prequel

http://open-services.net/bin/view/Main/PlmScenarioProductChangeOwnerassignsChangeRequesttoProductContext

Gray has posted documentation of the existing DOORS 9.3 -RTC3.0 usage of CM2.0

http://open-services.net/bin/view/Main/DoorsRtcIntegration

5. Responding to new OSLC Specs and concepts being published

We will pick up on the discussion on the proposals on the 23rd

6. Summary, actions and close

Follow up to 9/8 actions

9/8 ACTION: Gray to make a link on Front page for working extnesions - done

9/8 ACTION:Gray to ask David to share his analysis back as supporting the proposals - open

9/8 ACTION: Schedule look at Mike's TC implementation for Aug 16th - done

9/8 ACTION: Schedule the main work group for Aug 30th - scheduled

16/8 ACTION: Schedule Mike's Teamcenter walkthrough for Aug 23rd

16/8 Mike to share his RIO repo including - done

Next meeting 23rd Aug 11am ET

7. AOB

Brief look ahead to Aug 30th Main meeting and desire to present a roadmap for the Workgroup