OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-machine-industry message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: DITA Machine Industry SC: Meeting Minutes 2007/08/07


Agenda:

1) Roll call 
We do have quorum.

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

Motion to accept minutes made by: Chris Kravogel
Seconded by: Robin Sloan

Approve minutes from July 24th business meeting:
*
http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email
/archives/200707/msg00005.html

Motion to accept minutes made by: Chris Kravogel
Seconded by: Robin Sloan

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 

General Design Decision:

The group agrees that more feedback from implementors
is needed to finally decide on the general design questions. 

A List of important questions and the background of the current
decisions shall be included in the text of the DITA proposed feature.

Decisions so far:

- The described Elements shall be made optional in their
  container elements. Occurence: Zero or one (?)

  Elements:
   - spares
   - supplies
   - reqconds
   - supequip
   - safety
   
  Decision criteria: A madatory element would restrict the
  content model to far. Specializations can alwas make
  optional elements required but not the other way around.

- "The no-elements" shall remain in the content model. 

  Decision criteria:
  There are industry use-cases, where it actually is
  relevant to explicitly state that there are no
  such items needed.
  
- The content model itself shall not be changed. The
  or-constructs shall remain unchanged.

  The question raised was whether an occurence of one
  to many would be usefull for certain elements. The
  content models would then differ from S1000D.
  
DTD / Schema Implementation:

Chris Kravogel will implement the proposed content models
in a DTD.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]