AW: [dita-machine-industry] DITA Machine Industry SC: Meeting Minutes 2007/10/16

["SeicoDyne DITA" <dita@seicodyne.ch>]

Short info about the reply from Michael:

****************
Von: Michael Priestley [mailto:mpriestl@ca.ibm.com] 
Gesendet: Dienstag, 16. Oktober 2007 16:18
An: Christian Kravogel
Betreff: Re: AW: Machine Industry Issues



I think adding elements like supplies and spares to the prereq model for all
task authors is probably overkill (think of how the machine industry people
reacted to the software elements there - and they were in a domain!) 

If the rest of the content model is what you need, then I think probably a
domain is the way to go - you will need to be using 1.2 domain capabilities,
since in 1.1 it is not valid to specialize domains from prereq (or any other
structural specialization). 

***************

Best regards

Chris

-----Ursprüngliche Nachricht-----
Von: Gerald Goetz [mailto:goetz@noxum.com] 
Gesendet: Dienstag, 16. Oktober 2007 17:38
An: dita-machine-industry@lists.oasis-open.org
Cc: scott.hudson@flatironssolutions.com
Betreff: [dita-machine-industry] DITA Machine Industry SC: Meeting Minutes
2007/10/16


Agenda:
1) Roll call 

We have quorum.

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

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

3) Business: 

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


 - Discussion about the content model of element prelreqs with Scott Hudson.

   The content model shall be the "open DITA content model" as implemented
   in the mitask DTD prototype.

   Proposal made by: Chris Kravogel
   Seconded by: Sissy Closs

 - Discussion about the general design decision regarding the content model
   of mitask with Scott Hudson.
  
   - Option 1: Make mitask a domain specialization out of task.dtd
     (this implies limitations regarding the content model)
     - This would raise the questions what happens to the existing
       element prereq
     - This option can be ruled out due to the restrictions made by
       the task content model
     
   - Option 2: Derive mitask from topic
     - There are also specialization limitations 
    
   - Option 3: Create an additional different task which is not bound to
     deriving it from topic at all (approval from DITA TC required)
    
   Chris will try to move this discussion to the DITA TC.   

4) Announcements/Opens 

- The next meeting on October 30 will be one hour earlier (3 pm CET) for the
  european participants (different DST rules).
  
- The face to face meeting is scheduled for Friday November 9 from 4 pm to 6
pm
  at the TEKOM conference in Wiesbaden, Germany.

- Feedback regarding the hazardstatement specialization from the DITA
TC:
  The hazardstatement content model seems to be acceptable but the attribute
  specialization might not be a valid DITA 1.1 specialization. There might
be
  some modifications to the main element hazardstatement necessary in order
  to be consistent with the standard.