Meeting 46 Agenda – 18 September 2009
OASIS Product Life Cycle Support Technical Committee
Meeting 46 – Teleconference – 18 September 2009 - 1600 CET, 1500 UK, 1400 GMT, 1000 US Eastern, and 0700 US Pacific Time - for maximum 90 minutes.
Dial-in numbers & passcodes:
PARTICIPANTS PIN NUMBER:499596 #
Country / NumberFrance / 0805 110 496
Germany / 0800 101 4935
Italy / 800 985 528
Norway / 21033439
Spain / 900 998 979
Sweden / 0200 895 376
USA / 1866 874 0924
UK Local Call / 0845 144 0023
Std Int Dial In / +44 (0) 1452 542 437
Objective
The principal objectives of this session will be to update the TC members on progress with the active tasks in Phase 2 of the DEX activity, and continuing efforts to identify new resources to address the unassigned tasks. Members will be invited to highlight new DEX development projects. Other agenda items will be covered as time permits.
1. Welcome by Chair
2. Roll call
3. Report of Technical Oversight Group (Tor Arne Irgens)
• Report of TOG telecons
Action item 44/1: TOG to list competencies for TOG membership (TOG)
4. Report on second phase (Howard Mason)
• Review of resource commitments
See revised spreadsheet for breakdown of tasks and commitments. (Phase_II_v8.xls) (http://www.oasis-open.org/apps/org/workgroup/plcs/download.php/29624/Phase_II_v8.xls)
Action item 45/1: Develop cost proposal within next week (Chris Kreiler/Howard Mason/Mats Nilsson)
• Implementer’s Forum
Action item 37/2: Pull together the revised proposal for the implementers forum for discussion for the next telecom. (Howard Mason and Nils Sandsmark)
• New DEX proposals (Standing Action item 37/5)
Members are invited to present information on any new DEX developments they are undertaking.
• TDP proposal update (N.Figay)
Action item 41/2: Members interested in developing the Airbus TDP DEX are requested to contact Melanie Baudisch at EADS MAS +49 84 59 81 78 943 (All)
5. Ballot comment resolution of first DEX package (Jim Colson)
• Aviation Maintenance DEX
• Task DEX
Action item 41/3: CORE Team members are requested to work with Bryant Allen and Trine Hansen to resolve comments (CORE Team)
For information - from Clause 3.2 of the TC procedures
Before the TC can approve its Committee Draft as a Committee Specification the TC must conduct a public review of the work. The decision by the TC to submit the specification for public review requires a Full Majority Vote, and must be accompanied by a recommendation from the TC of external stakeholders who should be notified of the review. The Committee Draft approved to go to review shall be called a Public Review Draft. The public review must be announced by the TC Administrator to the OASIS Membership list and optionally on other public mail lists; the TC Administrator shall at the same time issue a call for IPR disclosure.
Comments from non-TC Members must be collected via the TC’s archived public comment facility; comments made through any other means shall not be accepted. The TC must acknowledge the receipt of each comment, track the comments received, and publish to its primary e-mail list the disposition of each comment at the end of the review period.
No changes may be made to the Public Review Draft during a review. If changes are required the specification must be withdrawn from review then resubmitted.
The TC may conduct any number of review cycles (i.e. approval to send a Committee Draft to Public Review, collecting comments, making edits to the specification, etc.). The first public review of a specification must take place for a minimum of 60 days, and any subsequent reviews must be held for a minimum of 15 days. Changes made to a specification after a review must be clearly identified in any subsequent review, and the subsequent review shall be limited in scope to changes made in the previous review. Before starting another review cycle the specification must be re-approved as a Committee Draft and then approved to go to public review by the TC.
If Substantive Changes are made to the specification after the public review, whether as a result of public review comments or from TC Member input, then the TC must conduct another review cycle. The specification may not be considered for approval by the TC as a Committee Specification until it has undergone a review cycle during which it has received no comments that result in Substantive Changes to the specification.
6. Reference data (Mats Nilsson)
• Report of activities on PLCS Reference Data
Action item 41/4: Reference data library project review ballot comments for project applicability and send out historical documents for review and comment (Mats Nilsson)
7. AP239 ed 2 (Phil Rutland / Rob Bodington)
• Report of activities on PLCS AP 239 ed 2
• Integration with other APs - Change request accepted
• Resources for supporting the ballot/resolution activities
8. PLCS Web Services Report (Rob Bodington)
Publication of PLCS Web Services as an OASIS standard - review of new draft
Action item 27/4: Establish contact with OASIS Web Services TC and make PLCS Web Services visible within OASIS (Howard Mason, Rob Bodington, and Nigel Shaw)
Action item 27/5: Review and comment on the level of granularity for PLCS Web Services (All)
Action item 27/6: Determine publication method for PLCS Web Services (Chair, Rob Bodington)
Action item 42/2: Check on next release date for PLCS Web Services (Nigel Shaw)
9. Feedback from Implementations
Action item 33/2: Members are requested to develop a one-page information sheet on their implementation projects for posting on the OASIS PLCS TC website (All)
Members are invited to present recent pilot activities.
· Feedback on PLCS success stories.
· Tangible business benefits.
· Issues and requirements
a) Norwegian Deployment
b) Swedish activities
c) UKMoD LCIA and CBIS
d) LOGSA
e) AIA Engineering Data Interoperability Project
f) ASD - AeroSpace and Defence Industries Association of Europe
10. Promotional activities
Action item 42/4: Send list of events and dates to Secretariat for posting on OASIS website. (All)
· Outreach
o Future events
o Recent past events
o www.et.gov - (waiting DEX availability)
Action 19/8: Nigel Shaw to look into the types of XML schemas being covered by et.gov, and provide feedback on whether the OASIS PLCS TC should offer material to et.gov. (Nigel Shaw)
Action 22/12: Recheck to see if posting material and a link to the PLCS ePortal would be beneficial. (Nigel Shaw)
o “Presentations and General Information” folder
· Marketing Links
Action 15/20: Chair (Howard Mason) to check with OASIS, James Clark, to see if list of organizations that provide PLCS services can be done
11. Liaisons
· SC4 (Tim King)
Action item 37/7: SC4 experts to monitor impact of cross AP implementation project.
· Other OASIS TCs
o Codelist (Nigel Shaw)
Action 26/1: Continue to track activities of OASIS Codelist TC for impact on reference data requirements (Nigel Shaw)
· ASD (Carl Wilen/Howard Mason)
· POSC/CAESAR (Nils Sandsmark)
· GEIA (Bryant Allen)
· Life Cycle Information Management AC/327 (Tor Arne Irgens)
· MoU between PLCS, SCORM, and S1000D
12. OASIS Administration
· Web site
13. Future meeting schedule, hosts
14. Any Other Business
15. Open Action Items
Meeting Date and Number / Action Item # / Action Item / Responsibility / Closed /14 Apr 2005 / 15 / 20 / Chair(Howard Mason) to check with OASIS, James Clark, to see if list of organizations that provide PLCS services can be done / Howard Mason / OPEN
29 Sep 2005 / 19 / 8 / Nigel Shaw to look into the types of XML schemas being covered by et.gov, and given the changing state of P28e2, provide feedback on whether the OASIS PLCS TC should offer material to et.gov. / Nigel Shaw / Awaiting first DEX
10 Jan 2006 / 22 / 12 / Recheck to see if posting material and a link to the PLCS ePortal would be beneficial / Nigel Shaw / Awaiting first DEX
7 Sep 2006 / 26 / 1 / Continue to track activities of OASIS Codelist TC for impact on reference data requirements / Nigel Shaw / OPEN
31 Oct 2006 / 27 / 4 / Establish contact with OASIS Web Services TC and make PLCS Web Services visible within OASIS / Howard Mason
Rob Bodington
Nigel Shaw / OPEN
31 Oct 2006 / 27 / 5 / Review and comment on the level of granularity for PLCS Web Services / All / OPEN
31 Oct 2006 / 27 / 6 / Determine publication method for PLCS Web Services / Howard Mason
Rob Bodington / OPEN
30 Aug 2007 / 33 / 2 / Members are requested to develop a one-page information sheet on their implementation projects for posting on the OASIS PLCS TC website / All / STANDING ACTION
11 Mar 2008 / 37 / 2 / Pull together the revised proposal for the implementers’ forum for discussion for the next telecom. / Howard Mason Nils Sandsmark / OPEN
11 Mar 2008 / 37 / 5 / Document DEX development proposals / All / STANDING ACTION
11 Mar 2008 / 37 / 7 / SC4 experts to monitor impact of cross AP implementation project. / SC4 Experts / OPEN
23 Oct 2008 / 41 / 2 / Members interested in developing the Airbus TDP DEX are requested to contact Melanie Baudisch at EADS MAS +49 84 59 81 78 943 / All / OPEN
23 Oct 2008 / 41 / 3 / CORE Team members are requested to work with Bryant Allen and Trine Hansen to resolve comments / CORE Team / OPEN
23 Oct 2008 / 41 / 4 / Reference data library project review ballot comments for project applicability and send out historical documents for review and comment / Mats Nilsson / OPEN
15 Dec 2008 / 42 / 2 / Check on next release date for PLCS Web Services / Nigel Shaw / OPEN
15 Dec 2008 / 42 / 4 / Send list of events and dates to Secretariat for posting on OASIS website. / All / STANDING ACTION
6 Apr 2009 / 44 / 1 / TOG to list competencies for TOG membership / TOG
10 Jun 2009 / 45 / 1 / Develop cost proposal within next week / Howard Mason, Chris Kreiler, Mats Nilsson
Page 1 of 6