Minutes for OASIS SDD TC 04/10/2008 Meeting

AGENDA

Agenda:

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from April 3 meeting

2. Administrative (Julia/Brent)

3. Standardization and document/publication status

A. Specification: "Housekeeping" updates complete; ready to submit for publication and Committee Specification vote

B. Primer: Minor updates for publication ("housekeeping" + example updates to match new examples) complete; ready to submit for publication

C. Starter Profile Material: Minor updates for publication (RDDL, "housekeeping") complete; ready to submit for publication

D. Examples: minor updates for publication (to match starter profile updates) complete; ready to submit for publication

4. Remaining work

- Version 1.1: Continue discussion of items to address and prioritize those items.

5. Old/new business

** Adjourn 12:00 noon US Eastern Time

MINUTES

We have a quorum.

1. Minutes for 4/03/2008 are approved as posted without comment or objection.

2. Administrative: Brent has some new information about how the Macrovision changes have affected Quenio’s and Robert’s participation. What he has learned is that Macrovision is the OASIS member, but that Quenio and Robert are now employees of Acresso. They are pursuing membership and we hope to welcome them back sometime soon.

3. Standardization and document/publication status: Document updates, link updates, references, etc. have been made in the specification. Brent has posted these updates. Housekeeping changes are the only changes in the specification. Brent will submit the specification to OASIS today. The primer and profile docs housekeeping changes are almost completed. When Brent receives them, they will also be posted and submitted to OASIS.

4. Remaining work – 1.1 Issues Prioritization – Brent has posted a spreadsheet

Brent will update the spreadsheet as we discuss the items so the main results of todays discussion can be seen by looking at the update to the issues spreadsheet that Brent will post after the meeting. Only issues will be recorded in the minutes. Our first pass approach will be to give each item the highest priority assigned to it by any member company. High priority means we MUST have a disposition of the item before shipping 1.1; Medium priority means we should have a disposition; Low priority means we’ll address it if we get to it. We made it through all items in the spreadsheet without the need to record any issues.

TC MEMBERS: Please take a look at the new issue priorities and identify the proposals you are prepared to create or discussions you would like to lead. We will assign owners to issues next week.

Minutes for OASIS SDD TC 04/03/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from March 27 meeting

2. Administrative (Julia/Brent)

- Review ballot results (2)

3. Standardization and document/publication status

A. Primer: Need minor updates for publication ("housekeeping" + example updates to match new examples).

B. Starter Profile Material: Approval ballot passed; working on updates for publication (RDDL, "housekeeping")

C. Examples: minor updates made for publication (to match starter profile updates).

4. Remaining work

- Version 1.1: Initiate discussion of items to address and prioritize those items. Brent will post an updated list of candidate items with mapping of items to supporting use cases.

5. Old/new business

** Adjourn 12:00 noon US Eastern Time

MINUTES

We have a quorum.

5. Minutes for 3/27/2008 are approved as posted without comment or objection.

6. Administrative:

a. The examples and profile ballots passed with a couple of minor comments. This means all our expository documents are ready to be published – after minor updates of links. Merri has the pen for those updates.

b. Dell has decided to discontinue their association with OASIS so Tom Studwell and John Zhang are no longer members of the committee. We will miss their valuable contributions.

c. The Macrovision transition has completed. Brent will be finding out if there will be continued participation from Quenio and Robert. (We miss them.)

7. We briefly review the 1.1 Issues Spread sheet was posted by Brent.

a. Howard notes that A2 is not alignment with another standard even though it is in the alignment section, and that it should be simple to accomplish. Brent notes that it is still a sort of alignment so we leave it in the alignment section.

b. The virtualization support item is moved to the alignment section as OVF alignment.

c. Julia notes 3 schema issue items to add:

i. The SDD author may know a lot more about what is needed to validate a parameter than can be communicated currently in the SDD. Let’s consider additional parameter metadata and/or parameter types.

ii. Default strings may need to be non-English.

iii. Valid values and default values for parameters may vary by locale.

d. There are also issues relative to the profile – including the issue of making it normative. Julia noted 3 profile items to add to the profile bucket. More information on these will be provided later. Brent will create a profile bucket in the spread sheet.

e. One of the issues is the “media” descriptor. Julia notes that she has been looking at the SML-IF standard and thinks we may get what we need without too much work by extending SML-IF.

8. What is our 1.1 timing? We will start work on 1.1. now but wait a while to actually branch a 1.1 schema and spec. Ideally this will happen after 1.0 standardization is complete so that we won’t have two active branches. When will we finish? Randy suggests, and Jason concurs, that a significant driver of our end date should be the needs of the open source SDD runtime work (COSMOS).

9. 1.1 Prioritization – ALL TC MEMBERS – please look at the 1.1 issues list over the next week and be prepared to discuss your priorities next week. Please identify each issue as high, medium or low priority. After prioritization, we can get started working on proposals.

10. TC MEMBERS – do you know of other companies that would like to join this work? This is a good time to add contributors, so if you know of anyone potentially interested in joining, encourage them to do it now.

11. Meeting timing: Should we go to every other week? Opinions expressed on both sides with the majority being in favor of every other week. Jason proposes a middle ground. Go to every other week right now, and then if we realize that the runtime is going to need 1.1 earlier than it looks like we can be done, then we’ll go back to weekly. Randy proposes that we do as Jason suggests with the modification that we continue with weekly calls until we have the 1.1 issues list prioritized and proposals assigned. So, TC MEMBERS please do your prioritization and think about which proposals you can sign up for.

Minutes for OASIS SDD TC 03/27/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from March 20 meeting

2. Administrative (Julia/Brent)

3. Public Review is now complete!

TC vote to initiate approval of Committee Specification for PR02 revision of the specification (ballot performed by OASIS TC Administrator)

4. Remaining work

A. Primer: ballot open now for final approval.

B. Starter Profile Material: Complete (approval ballot passed); working on publication

C. Examples: ballot open now for final approval.

D. Conformance Document: Complete (approval ballot passed, content incorporated in specification)

E. Version 1.1: Initiate discussion of items to address and prioritize those items. Brent has posted a mapping of known deferred items to supporting use cases.

5. Old/new business

** Adjourn 12:00 noon US Eastern Time

MINUTES

We have a quorum.

1. Minutes for 3/20/2008 are approved as posted without comment or objection.

2. Administrative: Merri is unable to attend and has requested that her proxy vote be passed to Ed from SAS. OASIS bylaws allow this. No objections are voiced. Brent does state that we would like to limit the use of proxy votes.

3. Public Review – only two comments received. One was a simple bug fix; the second will be part of the 1.1 discussion re: the specification of version formats.

Also, conformance information has been added as explanatory information. This is not a substantive change.

The TC can vote today to open a ballot to approve this as an OASIS Committee Specification. We do not open the ballot – the OASIS staff runs this ballot. This is a vote of the TC members. This vote requires a special majortiy to pass: 2/3 vote yes and no more than ¼ vote no. This is not the last step in getting to standardization. The next step is a vote by general membership. Each OASIS member company has a designated voting rep. This vote runs for multiple weeks and requires a special majority. After the general membership vote the specification goes to the OASIS steering committee for final ratification. It is at this point that we need three statements of use.

Brent requests a roll call vote to petition OASIS to open the Committee Specification ballot on pr01-r01. Motion to petition OASIS to open the Committee …. ballot is made by Chris and seconded by Jason. No further discussion.

Howard: Yes

John: Yes

Randy: Yes

Julia: Yes

Lazaar: Yes

Chris: Yes

Robert from SAS: Yes

Jason: Yes

Ed (for Merri): Yes

Vote passes unamiously. Brent will get the final housekeeping done on the spec – producing pdf, etc. and then pass this to Merri.

4. Primer – Please vote if you have not already. This requires a full majority. If not enough people vote, it won’t pass.

5. Starter Profile – Previously approved. Still waiting for publication. Decided we need rdl documents and we are awaiting the cr

6. Examples – Please vote if you have not already. cim: discussion…

7. Conformance Document – approved and incorporated in the specification.

8. SDD Version 1.1 – Brent posted a spread sheet called “Deferred Items” under Reference Material.

9. Old/New business –

a. Now that Macrovision has sold their software business, do we still have representation? Brent will try to find out.

b. COSMOS update: Jason is a committer. Eric Rose from IBM is nominated to be committer. IBM and SAS are both going through legal process to contribute code. Reviewing Change Analyzer code from IBM that parses and analyzes SDDs to identify what can be used. SAS has code that will handle a lot of the mechanics like processing artifacts, discovering versions, etc. The team is currently gathering requirements for the installation of the full COSMOS project deliverables. The goal is to use the SDD runtime being developed to install COSMOS. Also want to include registration of the deployed software with the COSMOS CMDB. Net, the SDD runtime is really “getting off the ground”. Brent notes that this is significant progress. Company participants in this work are SAS, IBM, CA and Compuware. Jason is working to grow that list. We discuss whether participation in this work constitutes use of the specification that qualifies for an OASIS statement of use. i.e. if we have 3 companies as open-source project contributors, would that qualify as the 3 statements of use?

c. Statement of use is a statement from the OASIS TC Process:

Statement of Use", with respect to a specification, is a written statement by an OASIS Organizational Member stating that it is successfully using or implementing that specification in accordance with the conformance clauses specified in Section 2.18, and stating whether its use included the interoperation of multiple independent implementations.

Also, from Brent’s notes from the TC Editor/Chair briefing given by Mary McRae at last year's OASIS Symposium:

§ Statements of use can be of many forms (interop/prototype/etc.; need not be products)

Brent would like us to have a discussion soon re: expected statements of use.

Minutes for OASIS SDD TC 03/20/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from March 6 meeting (Note: March 13 meeting was cancelled)

2. Administrative (Julia/Brent)

- Last week's meeting attendance

3. Public review comments review & disposition (no new PR comments received as of end of day March 18 -- Public Review is now complete!)

- next step: incorporate updates to specification and initiate approval of Committee Specification (ballot performed by OASIS TC Administrator)

4. Remaining work

A. Final Committee Draft for Primer -- Brent has incorporated all agreed-upon changes (Lazar's changes, Brent's responses to Julia's previous comments, updated "Conditions", "substitution value" and "weights" explanations to use the existing (updated by Randy) example). Updated version was posted for review; can consider a motion to open ballot for final approval.

B. Starter Profile Material -- Updates after approval ballot complete and approved; working on publication.

C. Example Updates: complete and posted (we should probably formally approve these as Committee Draft?)

D. Conformance Document -- Updates after ballot approval were posted; need to approve the updates and then incorporate the result into the specification.

E. Version 1.1: Initiate discussion of items to address and prioritize those items. Brent will post a mapping of known deferred items to supporting use cases.

5. Old/new business

** Adjourn 12:00 noon US Eastern Time

MINUTES

We have a quorum.

1. Minutes for our last meeting are approved without comment or objection.

2. Last week’s meeting was cancelled with short notice. It will not affect anyone’s voting rights.

3. Primer discussion

Brent notes a small number of changes that need to be made including:

a) The addition of a ResultingResource statement to the SimpleAppClient example.

b) A note from Lazaar that should have been addressed and removed.

c) Reword the text about the monolithic example to talk about the features rather than the support for multiple operating systems.

d) 3 minor editing issues that Julia found.

Motion to open ballot to approve the primer was made, seconded and passed.

4. Conformance chapter discussion

Three minor changes were made and have been reviewed. Motion to open ballot to approve conformance chapter was made, seconded and passed. Julia will merge in the conformance chapter to the specification, modify URL’s and post – today. Merri will review the merge and Brent will generate pdf and html files.

5. Example ballot

Motion to open ballot to approve the examples was made, seconded and passed.

6. OASIS Symposium

Brent, Randy and Julia submitted a presentation proposal and agreed to do a tutorial instead. Brent will post the slides for that tutorial so TC members can review. These will be submitted tomorrow so if you see anything that needs significant change please send comments immediately. (There will be some opportunity to modify this after tomorrow.)