DITA Machine Industry SC: Meeting Minutes 2007/09/18

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

Agenda:
1) Roll call 

We do have quorum.

2) Approve minutes from September 4th business meeting: 
*
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200709/msg00003.html

Motion to accept minutes made by: Chris Kravogel
Seconded by: Gerald Goetz

3) Business: 

- MI 03 MItask,
Evaluate mitask DTD
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200709/msg00002.html

- The group reviewd the DTD prototype for mitask developed
  by Chris Kravogel. This prototype is available in the
  documents section of the Machine Industry subcommittee:

 
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/downl
oad.php/25188/mitask_domain_dtd_1-2-0.zip

- In this prototype the software-, programming- and user-interface-
  domians have been removed. The hazardstatement- and mitask-domians
  have been added.

- Chris states that he used an element specialization technique that
  still has to be approved by the DITA TC (IssueConstraints12008).

 
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/25090/Iss
ueConstraints12008.html

- The mitask-specific elements in this DTD have been specialized
  from topic. The DTD itself is still based on the task DTD - it
  uses the element names and content models from task. This will
  change in future releases. The element names will have to change.
  
- A general design decision regarding the content model of mitask
  has to be made. Options are:
  
  - make mitask a domain specialization out of task.dtd
    (this implies limitations regarding the content model)
    
  - make an extension of task.dtd (as the mitaskDomian.mod
    already is)

  - create an additional different taks which is not bound to
    deriving it from topic at all (approval from DITA TC required)
  
- Discussion of content models for reqconds and reqpers.

  Conclusion:
  
  - There is still an uncertainty about the level of adoption of
    S1000D content models that the mitask should provide.
  
  - The design criteria behind S1000D elements and content models 
    need to be better understood. 
  
  - Chris will contact Scott Hudson regarding these questions. He
    has started a mailing list for DITA / S1000D interoperability.
    http://dita.xml.org/node/1483

4) Announcements/Opens 

 - Robin Sloan will not be able to join the proposed meeting at
   DITA Europe in November.