Minutes for OASIS SDD TC 01/31/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from January 24 meeting

2. Administrative (Julia/Brent)

- Primer approval ballot now open (closes Monday, Feb. 4)

3. Public review comments review & disposition [no new comments as of 01/30/20088:00 a.m.US eastern time]

4. Remaining work

A. Starter Profile Material -- Determine readiness for review & vote.

B. Example Update -- update examples to match Starter Profile and to use appropriate URIs; determine readiness and methodology for review & vote.

5. Old/new business

MINUTES

We have a quorum.

  1. Minutes for 1/24/2008 are approved without objection.
  1. Administrative
  2. Reminder that Primer ballot is open and closes next Monday. Lazar posted/e-mailed comments; we will add this to today's agenda for discussion if time permits
  3. No new public review comments received.
  1. Starter Profile and Primer discussion
  2. Jason will add examples to the doc before next week
  3. extending a profile
  4. defining a requirement on specific Windows version and service pack level
  5. Determine if the profile needs to be updated based on this example work (and make the updates if any are required).
  1. SDD Primer discussion
  2. Lazar would prefer to see the primer organized from the perspective of someone who is going to create an SDD rather than explaining an existing SDD. He will rework one section so we can all look at it and then decide if we want to rework the whole document.
  3. The current vote on the primer makes it a Committee Draft. That doesn’t prevent us reworking the doc for the next CD. Since there is discussion on the table for some serious changes, we can decide not to publish this first CD.

Minutes for OASIS SDD TC 01/24/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval: Meeting Minutes from January 17 meeting

2. Administrative (Julia/Brent)

- Public review submission status

- Primer approval ballot now open (closes Monday, Feb. 4)

- Updated standard adoption schedule posted

3. Remaining work

A. Starter Profile Material -- "schema" format in place; prose document to be updated (Jason) [see Jan. 10, Jan. 17 minutes]. Determine readiness for review & vote.

B. COSMOS SDD runtime effort overview & introduction -- including e-mail question about use cases (Jason) [10 minutes]

4. Public review comments review & disposition

5. Old/new business

** Adjourn 12:00noon US Eastern Time

MINUTES

We do not start with a quorum but achieve quorum by 10 after.

  1. Minutes for January 17, 2008 are approved without comment or objection.
  1. Administrative
  2. The public review began (finally!) on January 18th and will close on March 18th. There is one comment already – from a TC member on a minor error in the schema files. Also, Merri notes a difference between the CL1 schema and the CL2 schema. We want to change CL1 schema. Should this be posted as a comment? CL1 is non-normative so no public review comment is needed. Brent will clarify with a note on the public page – i.e. state that the CL1 schema is a subset of the CL2 schema provided for convenience and is non-normative. Brent will also find out more about where non-normative docs will be posted and see about having the CL1 schema moved.
  3. Primer ballot is open. Please review it (it isn’t very long) and vote. You can include comments in your vote. Note that Julia has made a lot of comments which can be seen in a marked-up version of the primer posted on the TC document page.
  4. The updated standard adoption schedule shows May 1st as the earliest likely adoption date.
  1. Starter Profile – Jason has posted new version of the primer and xsd files.
  2. Architecture check type was changed to CIM processor.
  3. Values of CIM operating system and processor have been reconciled – i.e. values in profile are now identical to names used in CIM.
  4. Jason requests help related to file system values. Randy will check and get back to Jason.
  5. TOC is wrong – Jason will update.
  6. Profile class definitions have been moved to an appendix.
  7. Attribute sections were created to consolidate attribute information and make the doc easier to follow.
  8. Section 2.1 has a statement about the SDD not governing profiles. Jason asks if we want to make recommendations.I.e. give some structure as to how you would work with profiles. e.g. Suggest that the first step is to look for existing profiles that meet your needs; If not find one to use as a starting point and extend it; Last choice is to create your own. If you extend or make your own, contribute back to the TC. Will also make recommendation that implementations provide extension points so that SDD authors can provide a means to deal with resource and artifact types they add to their profile that are not supported by the runtime.
  9. The SDD Primer assumes artifacts are defined in profiles. They aren’t there now. Should they be? We say yes and Jason will add. We decided on a simple enumeration.

Please review the profile primer now. Get comments to Jason by Tuesday the 29th. Jason will get updates to Randy by Wednesday and Randy will update example to match. Then we will go over everything next Thursday.

  1. COSMOS runtime project overview and update (from Jason). Use case formulation is in progress. Work can be seen on the COSMOS wiki. These are high level use cases for tools and runtime. Next step will be to open “Enhancement Requests” for enhancements to COSMOS for specific use cases. Detailed designs are done under the ERs.
  1. Merri is working on an appendix that explains more about CL1 and CL2. She would like to post it as a separate document now. It cannot be added to the spec until 1.1. We would like to include it with the other expository documents, like the primer – after the TC has reviewed and approved.
  1. Question about potential F2F meetings – so people can plan travel. Are we going to wait until we instantiate 1.1 and then schedule a meeting? Do we want a F2F to kick-off 1.1? Noted that we had a F2F to kick-off 1.0 – and it happened after 1.0 use cases and requirements were done and when there were submissions to review. Noted that 1.1 could be used as an opportunity to update the charter. Changing the charter requires a re-chartering process which would also be a way to invite others to join. Noted that we have a list of items deferred to 1.1. We can pull that out in the near future and use it to create use cases for 1.1. Brent will make sure that list is posted and notes that it is a partial list.
  1. Randy has posted updates to the CL1 and CL2 schema with the minor link problem fixed.
  1. John notes that an SDD presentation is on the agenda for EclipseCon with question marks next to it. Is someone thinking of presenting. Jason will check this out. Brent, Randy and Julia have submitted a proposal to the OASIS symposium and have been asked to do a tutorial instead of a presentation. We will know by the end of the month if this is accepted. The content of this tutorial might be re-used at EclipseCon. But EclipseCon is March 17-20, more than a month before the OASIS conference (April 28 – 5/1). Jason has a conflict and is not a candidate for presenting an EclipseCon.

Minutes for OASIS SDD TC 01/17/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval Meeting Minutes from January 10 meeting

2. Administrative (Julia/Brent)

- Public review submission status

3. Remaining work

A. Starter Profile Material -- "schema" format in place; prose document to be updated (Jason) [see Jan. 10 minutes]. Determine readiness for review & vote.

B. Primer -- accept John's updates and a few additional updates (Brent) see Jan. 10 minutes]. Determine readiness for review & vote.

C. COSMOS SDD runtime effort overview & introduction -- including e-mail question about use cases(Jason) [10 minutes]

D. OASIS Symposium -- opportunity for tutorial

4. Old/new business

** Adjourn 12:00noon US Eastern Time

MINUTES

We do not start with a quorum but achieve quorum by 10 after.

  1. Minutes for 1/10/2008 are approved as posted.
  1. Public review has still not begun. We are at the top of Mary MacRae’s list but she is apparently having connection difficulties and is not able to get our documents put in the correct location.
  1. Brent posted a primer that is probably ready for review. John completed the composite application description. Brent embedded example snippets and did some light editing. He also placed snippets in other locations. Brent also completed chapter 5 in the document.

Brent asks if we think the scope of the content is now about right? No comments. Please share thoughts on this via email if you think of something. Brent suggest we put this up for review now using an electronic ballot and allow comments. We can decide that abstain means agreement. Use of the electronic ballot is a way to make it easy to everyone’s comments in one place – it is not required for this non-normative document.

The intent is to post this primer with a link on the front page of our public TC site. It would not be subject to formal comments.

Moved, seconded and passed – open an electronic ballot as described.

  1. OASIS symposium is coming up at end of April. Call for papers went out a while ago. Randy, Julia and Brent submitted an abstract for an overview paper. The symposium committee has asked us to turn that into a tutorial. Has anyone else submitted something for the symposium? No response. Does the TC have an opinion on delivering a tutorial at the symposium – and is there someone willing to assist with that? (Symposium is the week of April 28thin Santa Clara, CA. The tutorial would be on the 28th.) Howard is in that area and will possibly attend. Randy asks if discussion of the COSMOS work in the tutorial is appropriate and useful. Yes, it is appropriate.
  1. COSMOS runtime effort – Jason wanted to give us an overview, but cannot be here today. Merri fills in. The runtime group met for several hours at IBM on Monday and came up with two sets of use cases – one for tooling and one for deployment. Tools are a build time generator and a packaging tool. For deployment, the hope is to take the use cases created by the SDD TC and adopt those for the runtime. Does anyone have a problem with this? The use cases do have company names included – i.e. the company that submitted the use case. Note that the use cases are already publicly available on our TC site and it is a TC-approved document. It appears that the OASIS copyright allows re-publishing and derivitative works from the published documents – which means that there would not be a problem. Brent will double check with OASIS. Merri will check on the Eclipse side to make sure there is no problem importing this information into COSMOS – which is an Eclipse project.
  1. Old/New Business – none. We adjourn early.

Please review the primer, post comments and vote.

Minutes for OASIS SDD TC 01/10/2008 Meeting

AGENDA

11:05 AM ET Roll Call

1. Minutes approval Meeting Minutes from December 13 meeting

2. Administrative (Julia/Brent)

- Public review submission status

3. Remaining work

A. Starter Profile Material -- "schema" format in place, need to update with values submitted by TC members; prose document to be updated (Jason) [see Dec. 13 minutes]

B. Primer -- initial content posted (Brent); updates posted (John); need review and a few additional updates to complete

4. Old/new business

** Adjourn 12:00noon US Eastern Time

MINUTES

We have a quorum.

  1. Meeting Minutes from December 13 meeting are approved without comment.
  1. Administrative
  2. Public Review status – We submitted everything required from the TC for the public review to the OASIS staff on December 13th. The staff has still not started the public review. This puts us behind on our schedule by a month. There isn’t anything we can do to change this – the public review must be a full 60 days. What we can do is try to address comments quickly. Typically comments come in at the end of the review period. Minor things can just be done by the editors. Substantive issues must be brought up in a TC meeting. All comments must be acknowledged – Brent will handle this. All comments must be addressed – Brent will send out information as appropriate.
  3. Action items – there are several old action items. We have not been using action items. Two are done, others are out-of-date or deferred. We vote to close them all.
  1. Remaining work
  2. Starter Profile – Jason updated the docs earlier today based on our agreements made at our last meeting and has incorporated additional classes suggested by individual companies.

Jason would like some help determining how to wrap up the document. It ends abruptly now after the classes are described. Additional information could include instructions or examples on how to use profiles. Pointers to examples would be good.Also include a discussion, plus examples, of how the values in the profiles are used in SDDs. Also include information on how to extend profiles.

Comment – data type and valid value definitions should be separate.

Comment – there are some valid values that do not match the ones defined in CIM. If we are using the same, or a subset of CIM, we should use the same values. Jason will stick to using the family types from CIM and put a note in the document about the correspondence with CIM values.

Comment – CIM models objects, not just resources. It makes for a bit of a mismatch. Randy and Jason will talk more about this off-line.

Comment – Refer to the SDD primer.

Please get any additional suggestions for additional classes to Jason ASAP.

Once Jason tells us this is ready for review, the review process will be similar to what we’ve done for the specification. Even though this is not normative, it is informative and public and we’ll take a vote on it after the review.

  1. SDD Primer – John posted an update that included his action item to provide text explaining the composite example. (Noted: “quite good”).

John notes that some examples will need to change to match the final starter profile.

Do we want to embed example files (attach) or inline them? We have both in the doc. Noted that it is easier to maintain if they are linked, but much easier to read and understand if they are inline. Another option is to put them in an appendix. Also, snippets could be inlined instead of full examples. Snippets could be combined with appendix or attachment or pointer to example files in appendix. Specification uses inline snippets combined with an appendix containing a link. We like this last suggestion best.

Brent will take the pen now for the primer and change the examples and fill in content for chapter 5.

Everyone – please review John’s changes (THIS WEEK) – or the whole thing if you haven’t reviewed yet.

Is there more work after Brent makes changes? Brent might call on individuals for help with chapter 5. We should be ready for a review in one or two more rounds of editing.

  1. New/old business:
  2. New work item. Examples need to be updated. Randy says he’ll do it once we finalize the starter profile.

Also, Randy asks that people review the examples (THIS WEEK) and look for things that are maybe not quite how we would like to do things and suggest updates.

  1. John suggests that Jason walk us through the COSMOS work on our next call. Jason notes that subscribing to cosmos-dev can be useful. Also, there is a recurring call on Tuesdays at 9am. Progress can be monitored by attending the meeting or following the work on the wiki. Now is the time to start participating if you intend to participate at all.