PROJ - ODP2 - Meeting 19.04.2007 - Minutes

Agenda

Meeting Results

Agree on agenda

Due to the fact that more contributions are expected with regards to requirements, we should rather focus on the structuring of the working draft. Therefore we will focus the agenda on this and the next meeting.

Select note taker

Øyvind Aassve

Review Open Action Items

Review of formulations in existing requirement draft

Postponed til after requirements contribution deadline.

Implementing requirements proposal from Dublin into draft

Postponed til after requirements contribution deadline.

Status with regard to additional requirements contributions

There are still IPR-issues to deal with. There is still hope that these issues will be resolved within the requirements deadline in about two weeks.

Other business

Structuring of the working draft document

Structuring of the document was made the main topic of the meeting.

Use of Confluence

Question: Could we use Confluence in the specification development process? How suitable is Confluence for big documents?.
Advantage: All information available in a central easy, always accesible spot, always up to date, handles change tracking, enables separate versioning for the different pages.
Disadvantage: No page numbers?

Proposal: We will try to use Confluence and if necessary we split it into several pages. At given stages we can put them togheter into a single PDF. It will be interesting to test out how Confluence is for developing documents.
There is however raised an issue in fmg that says all development in un/cefact should be done in ODF.

   Decision: Use Confluence until other decision from fmg.

  Action Point: Mark sends generic spec template to Tony.

  Action Point: Tony implements the Confluence-pages for this template.  

Document structure

The main outline of the spec is proposed to be: 

Introduction

How context drivers works and their purpose (non-normative).

Metamodel (normative)

Methodology - rules and logic (normative)

• Consider assembly approach
• Governance and harmonizaton
• Extension and maintenace
• Design time and run-time

Context categorization (normative)

References to related standards

• How to handle relation to SBDH

Appendix:

• Migration Path for current context drivers
  
  

Next meeting

Next meeting: May 3.

Agenda: Handle contributions/ submissions if any has  been received.
Continue working on outline of working draft.

Final deadline for requirements contributions will be set on this meeting.

Next Meetings

Action item list of the Steering Committee is available, now. You'll find the first lists of action items for the TMG StC group at the following link:

http://75.43.29.149:8080/display/public/TMG+-+Steering+Committee+%28StC%29

Every specific action item list is a so called "News Page" that is based on News Page and should be prepared immediately after each meeting. The action item will be display at this webpage by the filtering mechanism. This will match the specified labels "tmg_stc" and "action_items"

I assigned each action item to one responsible persons, therefore is the action item list a little bit longer. But this is more helpful in order to see, if the action item will be really solved.

Please click on the right icon: , if you feel that you solved your action items in were you're responsible for it.

The green icon shows , that the specific action item is checked.

Please do not click on "Edit" at left navigation pane, if you're at the news page directly. Otherwise, we will loss all the "checked" actions.