| From | Sent On | Attachments |
|---|---|---|
| Chri...@mantech.com | Sep 10, 2010 10:20 am | .ics |
| Subject: | [plcs] Groups - PLCS Teleconference Meeting 53 modified | |
|---|---|---|
| From: | Chri...@mantech.com (Chri...@mantech.com) | |
| Date: | Sep 10, 2010 10:20:53 am | |
| List: | org.oasis-open.lists.plcs | |
| Attachments: | ![]() ical_26984.ics - 2k | |
PLCS Teleconference Meeting 53 has been modified by Mr. Christopher Kreiler
Date: Wednesday, 08 September 2010 Time: 02:00pm - 03:30pm GMT
Event Description:
Meeting 53 Teleconference 8 September 2010 - 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 Number France 0805 110 496 Germany 0800 101 4935 Italy 800 985 528 Norway 21033439 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 are to review any comments resulting
from the Public Review and decide next steps if any are substantive comments.
Agenda: Objective
The initial objective of this session is to review any comments resulting from
the Public Review and decide next steps if there are any substantive comments
that would prevent progress to Committee Specification ballot. The meeting will
then consider ongoing actions for the major development streams under the TC,
and the resources available. This will pick up the bulk of the outstanding
actions.
1. Welcome by Chair
2. Roll call
Members are invited to highlight any news of relevance to the TC
3. Comments received from OASIS Public Review period (Secretariat)
4. Launch of ballot on Task DEX as a Committee Specification
5. Report from TOG (Tor Arne Irgens)
Action item 46/1: Provide Tor Arne with any inputs to expand the PLCS Activity
Model (All)
Action item 52/3: Explore potential dates for TOG/CORE Team face-to-face meeting
(Tor Arne Irgens)
6. Way forward (Chair)
o Process development (TOG)
Recommendations from TOG based on lessons learned from Task DEX and earlier
project.
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)
o Further DEX standardisation (All)
Members are invited to present information on any new DEX developments they are
undertaking, (Standing Action item 37/5)
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
mela...@eads.com (All)
Action item 48/1: Explore opportunity for ASD DEXes to be published by OASIS and
referenced from S3000L (Leif Gyllstrom)
Action item 52/2: PLCS TC members are requested to send their priorities for the
next DEX to be standardised, with an indication of whether DEX is supported by
funded projects (All)
o Implementors Forum (Jim Colson)
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)
Action item 50/1: Flag issues and requirements for implementers' forum. Send to
Jim Colson (All)
Action item 50/2: Estimate of costs and business model on how this will be
self-sustaining (Jim Colson and TOG)
o Web services
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)
o Resources
Action item 46/2: Provide inputs and estimates for the resource spreadsheet
including resolution of ballot comments, additional one-off costs, development
of reference data, capabilities, and templates, and any additional items for
completion of core Tasks (CORE Team)
Action item 47/1: Finish TC core activities with time and costs spreadsheet to
include DEX development costs (Chris Kreiler / Rob Bodington)
7. AP 239 e2 status
8. Liaisons
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)
www.et.gov
Action 19/8&22/12: 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)
ASD (Carl Wilen/Howard Mason)
POSC/CAESAR (Nils Sandsmark)
GEIA (Jim Colson)
Life Cycle Information Management AC/327 (Tor Arne Irgens)
MoU between PLCS, SCORM, and S1000D
9. Promotional opportunities
Action item 42/4: Send list of events and dates to Secretariat for posting on
OASIS website. (All)
10. OASIS Administration
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. Future meeting schedule, hosts
12. Any Other Business
13. 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 5 Document DEX development proposals All STANDING ACTION
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
mela...@eads.com All 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 OPEN
18 Sep 2009 46 1 Provide Tor Arne with any inputs to expand the PLCS Activity
Model All OPEN
18 Sep 2009 46 2 Provide inputs and estimates for the resource spreadsheet
including resolution of ballot comments, additional one-off costs, development
of reference data, capabilities, and templates, and any additional items for
completion of CORE Tasks CORE Team OPEN
20 Oct 2009 47 1 Finish TC core activities with time and costs spreadsheet to
include DEX development costs Chris Kreiler
Rob Bodington OPEN
25 Nov 2009 48 1 Explore opportunity for ASD DEXes to be published by OASIS and
referenced from S3000L (Leif Gyllstrom) Leif Gyllstrom OPEN
25 Feb 2010 50 1 Flag issues and requirements for implementers' forum. Send to
Jim Colson All OPEN
25 Feb 2010 50 2 Estimate of costs and business model on how this will be
self-sustaining Jim Colson and TOG OPEN
13 Apr 2010 52 1 Secretariat to submit corrected Task DEX document to OASIS Mary
McRae for 15-day OASIS Public Review Chris Kreiler Completed
13 Apr 2010 52 2 PLCS TC members are requested to send their priorities for the
next DEX to be standardised, with an indication of whether DEX is supported by
funded projects All
13 Apr 2010 52 3 Explore potential dates for TOG/CORE Team face-to-face meeting
Tor Arne Irgens
Minutes: OASIS Product Life Cycle Support Technical Committee
Meeting 53 Teleconference 8 September 2010 - 1600 CET, 1500 UK, 1400 GMT, 1000
US Eastern, and 0700 US Pacific Time - for maximum 90 minutes.
Objective
The initial objective of this session was to review any comments resulting from
the Public Review and decide next steps if there are any substantive comments
that would prevent progress to Committee Specification ballot. The meeting then
considered ongoing actions for the major development streams under the TC, and
the resources available.
1. Welcome by Chair
Chair welcomed everyone to the teleconference 2. Roll call See Attendance_plcs_Mtg53_2010-09-08.xls The meeting did achieve a quorum
Meeting Statistics Quorum rule 51% of voting members Achieved quorum true Counts toward voter eligibility true Individual Attendance Members: 22 of 100 (22%) Voting Members: 13 of 15 (86%) (used for quorum calculation) Company Attendance Companies: 14 of 24 (58%) Voting Companies: 10 of 11 (90%)
Meeting Attendees Name Company Status Sean Barker BAE SYSTEMS plc Group Member Howard Mason BAE SYSTEMS plc Group Member Trine Hansen Det Norske Veritas (DNV)* Group Member Tore Hartvigsen Det Norske Veritas (DNV)* Group Member Fredrik Larsen Det Norske Veritas (DNV)* Group Member Jarl Magnusson DNV Guest Rob Bodington Eurostep AB* Group Member Kjell Bengtsson Jotne EPM Technology* Group Member Jochen Haenisch Jotne EPM Technology* Group Member James Martin Jotne EPM Technology* Group Member Pamela Rooney Lockheed Martin* Group Member Ann Meads LSC Group Ltd* Group Member Christopher Kreiler ManTech Enterprise Integration Center (e-IC)* Group Member Tor Arne Irgens Norwegian Defence Logistics Organization* Group Member Leif Gyllstrom Saab AB Group Member Mats Elgh Swedish Defence Materiel Administration* Group Member Mats Nilsson Swedish Defence Materiel Administration* Group Member Jay Ganguli The Boeing Company* Group Member Jim Illback The Boeing Company* Group Member Phil Rutland UK Ministry of Defence Technical Information* Group Member Jerry Smith US Department of Defense (DoD)* Group Member James Colson USAMC Logistics Support Activity* Group Member John Peer USAMC Logistics Support Activity* Group Member
Members were invited to highlight any news of relevance to the TC
o US AIA and ASD-Europe signed MOU to collaborate on all S-series specifications
o PDT Europe A technical workshop on PLCS implementations will be held on 15
November. If interested in presenting, e-mail Rob Bodington (Eurostep), Trine
Hansen (DNV), or Scot Motquin (LOGSA)
o UID Forum in progress in Orlando. Presenting demos on PLCS and UID. Taking a
re-look at Aviation Maintenance DEX for applicability to ground vehicles
o UID using item identifiers to aggregate items. Started work on item
identification DEX for IUID. Looking for standardization within a year. Allows
submission of UID and associated information to meet DoD requirements.
o UK MOD has proposal in for approval for support for the ballot resolution
process for the DIS vote on AP239ed2
o Joint US/Europe LOTAR (LOng Term Archiving and Retention) project exploring
opportunity to store information in PLCS format for moving data among PDM
systems (PDM System to DEX to PDM system). Will discuss in PLCS implementors
forum in Charleston next week
o AP242 being developed within ISO/TC 184/SC 4 to combine AP203ed2 and modular
AP214 into single standards
3. Comments received from OASIS Public Review period
Discussed comments submitted by Eurostep and response by LSC for correction.
See oasis_r4_issues_eurostep.docx and oasis_r4_issues_eurostep_anm_response.docx
Solution is to add missing template, remove disjoint rules and remove 2 OWL
classes.
Changes considered to be editorial in nature
Revised document available in a couple of days.
4. Launch of ballot on Task DEX as a Committee Specification
No substantive changes are required for comment resolution.
MOTION: The PLCS TC resolves to forward the revised TASK DEX document to OASIS
for a vote as a Committee Specification.
Motion to forward Task DEX as a Committee Specification approved by unanimous
consent
Action item 53/1: Secretariat to submit corrected Task DEX document to OASIS
Mary McRae for a committee specification vote (Chris Kreiler)
5. Report from TOG (Tor Arne Irgens)
Action item 46/1: Provide Tor Arne with any inputs to expand the PLCS Activity
Model (All)
Action item 52/3: Explore potential dates for TOG/CORE Team face-to-face meeting
(Tor Arne Irgens)
Not a lot of funded activity for TOG
Not a lot of activity due to resource constraints
Norway implementing a PDM system based on SAP. Difficult to support other
activities
No thought of holding a face-to-face meeting at this time
Agreed to refine activity model to validate against use cases
Internal (Norwegian Defense) inputs for PLCS Activity Model. Will forward at
a later date.
UK MoD has a number of DEXs that need to be validated against the PLCS
activity model.
NATO Codification primarily working with SC 4 OTD, not PLCS
Suggested that the PLCS community could support the filtering of requirements
for UID and codification
6. Way forward (Chair)
o Process development (TOG)
Recommendations from TOG to be based on lessons learned from Task DEX and
earlier project.
Harmonization activities and expanding PLCS Activity model
UK report sent to TOG on DEX development. TOG will look at it and decide
whether to make it public.
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)
No action since Mats just back from paternity leave
o Further DEX standardisation (All)
Members are invited to present information on any new DEX developments they are
undertaking, (Standing Action item 37/5) see above
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
mela...@eads.com (All)
Action item 52/2: PLCS TC members are requested to send their priorities for the
next DEX to be standardised, with an indication of whether DEX is supported by
funded projects (completed)
The earlier reports had highlighted a number of priorities
o Item identification
o Maintenance DEX uses for other classes of vehicles
o LOTAR development using PLCS
o LOGSA implementing a lot of DEXs (GEIA-00007). Manage logistics product data
in PLCS
PLCS implementers forum. May need meeting to work out issues. Moving slowly,
but moving
LOGSA will continue to support Reference Data Library activities
ASD Activity
o ASD DEXs. Two new DEXs for S3000L (Task and Product Breakdown). Finalizing
DEX 1 and will load next week for S3000L team to review. Added lots of
reference data
o Conceptual model for S2000M Chapter 1 initial provisioning DEX. Scope Bill
of Materials (BOM), parts list, provisioning information, etc.
o PLCS representation will be uploaded to DEXLib and eventually adopted as an
OASIS Specification/Standard
Action item 48/1: Explore opportunity for ASD DEXes to be published by OASIS and
referenced from S3000L (completed)
The Chair emphasised the opportunity for projects to use the TC to recognise
potential synergies and to work together to pool resources and accelerate
deliverables. There was potential to develop common DEX models applicable to
different environments by tailoring the reference data. This depended on
visibility of the development tasks and their associated schedules..
Action item 53/2: Secretariat to post a quick summary of the "Further DEX
standardisation projects on PLCS website upon receipt of information from PLCS
TC members (ALL)
o Implementors Forum (Jim Colson)
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)
Action item 50/1: Flag issues and requirements for implementers' forum. Send to
Jim Colson (All)
Action item 50/2: Estimate of costs and business model on how this will be
self-sustaining (Jim Colson and TOG)
Reminder to members to send expectations of the PLCS Implementors Forum to
Jim Colson (Action Item 50/1)
o Web services
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)
Web services still on hold
AP242 may influence the future structure and granularity of the web services
o Resources
Action item 46/2: Provide inputs and estimates for the resource spreadsheet
including resolution of ballot comments, additional one-off costs, development
of reference data, capabilities, and templates, and any additional items for
completion of core Tasks (CORE Team)
Action item 47/1: Finish TC core activities with time and costs spreadsheet to
include DEX development costs (Chris Kreiler / Rob Bodington)
CORE resources spreadsheet up-to-date with inputs received
Check against work on getting Task DEX out
Action item 53/3: Secretariat to review resource spreadsheet against work
getting Task DEX out (Chris Kreiler / Colin Tweedie)
7. AP 239 e2 status
DIS ballot scheduled to complete 2010-09-23 Resolution workshop to be scheduled for Vico Equense if necessary
8. Liaisons
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)
No report
www.et.gov
Action 19/8 & 22/12: 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)
No report
ASD (Carl Wilen/Howard Mason)
See prior items for ASD work
POSC/CAESAR (Nils Sandsmark)
No report
GEIA (Jim Colson)
LOGSA discussed Haystack for parts information
Life Cycle Information Management AC/327 (Tor Arne Irgens)
No report
MoU between PLCS, SCORM, and S1000D
No report
9. Promotional opportunities
Action item 42/4: Send list of events and dates to Secretariat for posting on
OASIS website. (All)
2010-11-15/17 PDT Europe
o Prof. Dr. Knut Blind will present on Standardsation and Innovation at PDT
Europe 2010
10. OASIS Administration
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
No report
11. Future meeting schedule, hosts
No need for face-to-face meeting. Teleconference preferred given heavy
schedules
AP239ed2 ballot comment resolution workshop planned for the SC 4 Vico Equense
meeting 2010-10-17/22
2010-11-02 Meeting 54 Teleconference. Focus on TOG feedback on processes and
schedule for DEXs
12. Any Other Business
None
13. 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 5 Document DEX development proposals All STANDING ACTION
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
mela...@eads.com All 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 OPEN
18 Sep 2009 46 1 Provide Tor Arne with any inputs to expand the PLCS Activity
Model All OPEN
18 Sep 2009 46 2 Provide inputs and estimates for the resource spreadsheet
including resolution of ballot comments, additional one-off costs, development
of reference data, capabilities, and templates, and any additional items for
completion of CORE Tasks CORE Team OPEN
20 Oct 2009 47 1 Finish TC core activities with time and costs spreadsheet to
include DEX development costs Chris Kreiler
Rob Bodington OPEN
25 Nov 2009 48 1 Explore opportunity for ASD DEXes to be published by OASIS and
referenced from S3000L (Leif Gyllstrom) Leif Gyllstrom Completed
25 Feb 2010 50 1 Flag issues and requirements for implementers' forum. Send to
Jim Colson All OPEN
25 Feb 2010 50 2 Estimate of costs and business model on how this will be
self-sustaining Jim Colson and TOG OPEN
13 Apr 2010 52 1 Secretariat to submit corrected Task DEX document to OASIS Mary
McRae for 15-day OASIS Public Review Chris Kreiler Completed
13 Apr 2010 52 2 PLCS TC members are requested to send their priorities for the
next DEX to be standardised, with an indication of whether DEX is supported by
funded projects All Completed
13 Apr 2010 52 3 Explore potential dates for TOG/CORE Team face-to-face meeting
Tor Arne Irgens
8 Sep 2010 53 1 Secretariat to submit corrected Task DEX document to OASIS Mary
McRae for a committee specification vote Chris Kreiler
8 Sep 2010 53 2 Secretariat to post a quick summary of the "Further DEX
standardisation on PLCS website upon receipt of information from PLCS TC members
All
8 Sep 2010 53 3 Secretariat to resource spreadsheet against work getting TASK
DEX out Chris Kreiler / Colin Tweedie
Reference material from "Governing the OASIS Technical Committee Process"
2.13 TC Voting
TC votes require a Simple Majority Vote to pass, except as noted elsewhere in
this Process. All TC ballots requiring a Special Majority Vote for approval must
be conducted by the TC Administrator; the TC Chair shall notify the TC
Administrator that a motion has been made which requires a Special Majority
Vote, and the TC Administrator shall set up and conduct the ballot.
Eligibility: A Member of a TC must have voting rights to make or second a
motion, and must have voting rights at the time a ballot is opened in order to
vote on that ballot. Every Voting Member of a TC has a single vote.
Organizations do not vote in TCs. Proxies shall not be allowed in TC voting.
Electronic Voting: TCs may conduct electronic ballots, either by using the TCs
general mail list or the publicly archived electronic voting functionality
provided by OASIS. The minimum period allowed for electronic voting shall be
seven days; the TC may specify a longer voting period for a particular
electronic ballot. Any Specification Ballot conducted as an electronic ballot
must permit each voter to choose "yes", "no" or "abstain."
A motion to open an electronic ballot must be made in a TC meeting unless the TC
has adopted a standing rule to allow this motion to be made on the TCs general
email list. When such a rule has been adopted, motions made on the mail list
must also be seconded and discussed on that list.
2.18 Specification Quality
All documents and other files produced by the TC, including specifications at
any level of approval, must use the OASIS file naming scheme, and must include
the OASIS copyright notice. All document files must be written using the OASIS
document authoring templates, which shall be published and maintained by the TC
Administrator. The name of any specification may not include any trademarks or
service marks not owned by OASIS.
A specification that is approved by the TC at the Public Review Draft, Committee
Specification or OASIS Standard level must include a separate section, listing a
set of numbered conformance clauses, to which any implementation of the
specification must adhere in order to claim conformance to the specification (or
any optional portion thereof).
A specification that is approved by the TC at any level must include a list of
people who participated in the development of the specification. This list shall
be initially compiled by the Chair, and any Member of the TC may add or remove
their names from the list by request.
A specification that is approved by the TC at any level must clearly indicate
whether each reference in the specification to a document or artifact is a
Normative Reference.
Editable formats of all versions of TC documents must be delivered to the TCs
document repository. TC Working Drafts may be in any format (i.e. produced by
any application). All TC-approved versions of documents (i.e. Committee Drafts,
Public Review Drafts, and Committee Specifications) must be delivered to the TCs
document repository in the (1) editable source, (2) HTML or XHTML, and (3) PDF
formats; and the TC must explicitly designate one of those delivered formats as
the authoritative document. Any links published by the TC shall be to the HTML,
XHTML and/or PDF formats stored using repositories and domain names owned by
OASIS and as approved by the TC Administrator.
All normative computer language definitions that are part of the specification,
such as XML instances, schemas and Java(TM) code, including fragments of such,
must be well-formed and valid, and must be provided in separate plain text
files. Each text file must be referenced from the specification. Where any
definition in these separate files disagrees with the definition found in the
specification, the definition in the separate file prevails.
A specification may be composed of any number of files of different types,
though any such multi-part specification must have a single specification name
and version number. Irrespective of the number and status of the constituent
parts, the specification as a whole must be approved by a single TC ballot.
Any change made to a specification requires a new version or revision number,
except for changes made to (a) the approval status, (b) the date, (c) the URIs
of the specification as appropriate, (d) the running header/footer, and (e) any
approved Designated Cross-Reference Changes, all of which must be made after the
approval of the specification as a Committee Draft, Committee Specification, or
OASIS Standard.
Section 3. Standards Approval Process
3.1 Approval of a Committee Draft
The TC may at any stage during development of a specification approve the
specification as a Committee Draft. The approval of a Committee Draft shall
require a Full Majority Vote of the TC. The TC may approve a specification,
revise it, and re-approve it any number of times as a Committee Draft.
3.2. Public Review
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 TCs 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.
3.3 Approval of a Committee Specification
After the public review of a Public Review Draft the TC may approve the
specification as a Committee Specification. If any comments have been received
during the most recent Public Review period, that vote may not commence any
earlier than 7 days after the last day of that Public Review. The approval of a
Committee Specification shall require a Special Majority Vote. The TC Chair
shall notify the TC Administrator that the TC is ready to vote on the approval
of the specification, and provide to the TC Administrator the location of the
editable versions of the specification files. The TC Administrator shall set up
and conduct the ballot to approve the Committee Specification.
View event details: http://www.oasis-open.org/apps/org/workgroup/plcs/event.php?event_id=26984
PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
Referenced Items
Date Name Type
---- ---- ----
2010-09-03 oasis_r4_issues_eurostep_anm_response.docxReference Document
2010-09-03 oasis_r4_issues_eurostep.docx Reference Document
2010-04-29 Support to OASIS DEX Completion - Project Report -
v1.1.pdfReference Document
2010-04-29 DEX_Publication_Project_Phase_I_version_2.docReference Document
2010-08-20 Agenda_Meeting_53_20100908_Rev1.docAgenda
2010-09-10 Minutes_Meeting_53_2010-09-08_Rev2.docMinutes
BEGIN:VCALENDAR METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-WR-CALNAME:My Calendar BEGIN:VEVENT CATEGORIES:MEETING STATUS:TENTATIVE DTSTAMP:20100910T000000Z DTSTART:20100908T140000Z DTEND:20100908T153000Z SEQUENCE:8 SUMMARY:PLCS Teleconference Meeting 53 DESCRIPTION:Meeting 53 Teleconference 8 September 2010 - 1600 CET\, 1500 UK\, 1400 GMT\, 1000 US Eastern\, and 0700 US Pacific Time - for maximum 90 minutes. \n\n\nDial-in numbers & passcodes\n\nPARTICIPANTS PIN NUMBER: 499596 #\n\n Country Number\nFrance 0805 110 496\nGermany 0800 101 4935\nItaly 800 985 528\nNorway 21033439\nSweden 0200 895 376\nUSA 1866 874 0924\nUK Local Call 0845 144 0023\nStd Int Dial In +44 (0) 1452 542 437\n\n\n\nObjective\n\nThe principal objectives of this session are to review any comments resulting from the Public Review and decide next steps if any are substantive comments.\n\nGroup: OASIS Product Life Cycle Support (PLCS) TC\nCreator: Mr. Christopher Kreiler URL:http://www.oasis-open.org/apps/org/workgroup/plcs/event.php?event_id=26984 UID:http://www.oasis-open.org/apps/org/workgroup/plcs/event.php?event_id=26984 END:VEVENT END:VCALENDAR
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php






.ics