DITA Machine Industry SC: Meeting Minutes 2007/06/26

["Gerald Goetz" <goetz@noxum.com>]

Agenda:
1) Roll call 
We have quorum.

2) Approve minutes from May 29th business meeting: 
*
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200706/msg00000.html 

Minutes accepted by: Chris Kravogel
Seconded by: Gerald Goetz

Note: The business meeting from June 12 is not considered as an
      official meeting (no quorum) and does not require meeting
      minutes.

3) Business: 

- MI 03 MItask, Evaluate S1000D element list
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200706/msg00001.html 

The group reviewed the S1000D element list based on

 - the Excel document "S1000DprocedureElements-v1-1.xls"
   provided by Chris Kravogel

 - the S1000D Element Description (proced.zip)  
   Chris uploaded the S1000D documentation provided by Robin Sloan
 
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200706/msg00004.html
 
General Procedure:

- Review the list of elements and their content models
- Decide which elements and content models should be
  adopted by the MITask data model
- Specify a preference regarding the occurence  
- Decide on a element name and exact MITask content model
  later, in a second step

General Design Decisions:

The group will only adopt elements and content models when
a use case can be identified - especially without prior knowledge
of S1000D applications, use cases and data models.

Conformance with S1000D is not mandatory. Element names
and content models can differ. Interoperability with S1000D
is not a primary goal of the MITask design process. However
the group trys to keep the MITask somehow close to S1000D.

Elements not adopted by the MITask data model are marked
unnecessary (Unn).

Element List Evaluation:

Element "proced" (Procedural Information):
  - The element "proced" has a similarity to DITA "taskbody".
  - The future name of this element can not be "taskbody".
  - Occurence: Optional (General DITA content model)
 
Content Model of "proced":
  - Element "prelreqs" (Preliminary Requirements) has a
    similarity to DITA "prereq".
  - Element "closereqs" Close up requirements) has a
    similarity to DITA "postreq".

Element "prelreqs" (Preliminary Requirements):
  - Occurence: Optional

Element "pmd" (Production Management Data):
  - Unneccessary 

Element "reqconds" (Required Conditions):
  - Occurence: TBD

Content Model of "reqconds":
  - S1000D content model: ( noconds|( reqcond| reqcondm| reqcontp)+)

  - The content model allows a nesting of "reqcond" and
    includes an element noconds (No Required Conditions).
    The element "noconds" could be spared if "reqconds"
    was optional. The value of the required occurence in
    combination with a no-element in the content model has
    to be discussed.

Element "reqcond" (Required Condition):
  - The group would favour a DITA block content model but
    intends to include a combined block / phrase content model
    in order to conform with the general DITA specialization
    approach. The S1000D content model is considered to elaborate.

  - The element applic (Applicability) in the S1000D content model
    is regarded to be covered by the DITA select attributes. Chris
    described the process of attribute specialization in DITA 1.1.

Element "reqcondm" (Required Condition Data Modules):
  - Unneccessary 

Element "reqcontp" (Required Condition Technical Publications):
  - Use case: Provide a list of related bulletins / related
    instruction sheets etc.
  - Combined block / phrase content model.

4) Announcements/Opens 

Chris suggests a group meeting this fall at one of the following
events:

 - tekom Annual Conference November 2007, Wiesbaden, Germany 
 - DITA Europe, November 2007, Brussels, Belgium