AW: Review on the DITA 1.2 Machine Industry DTDs and XSDs

Eric

 

 

At the meetings on August 26th and 
September 2nd we posted the decision of the SC to rename machine industry 
task to machinerytask and to support the proposal of Michael Priestly to rename 
the machineIndustryDomain to taskRequirementsDomain.

http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/200808/msg00045.html

http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/200809/msg00001.html

 

At the meeting on the 23rd of September we made the 
final DITA 1.2 decission on the packaging question.

http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/200809/msg00025.html

There we decided not to have a machine industry package 
in DITA 1.2. All domains, mod's and constrains files became part of the 
technical package. (hazardstatement, taskrequirements and 
machinerytask)

 

there might be the possibility that we will have a 
machinery package with DITA 1.3 but I guess the domains hazardstatement and 
taskrequirements will remain on the technical package level due to their wider 
use.

 

So I would recommend the following 
urn's:

<system systemId=urn:oasis:names:tc:dita:xsd:hazardstatementDomain.xsd:1.2 uri="hazardstatementDomain.xsd"/> (as it already 
is)

<system systemId=urn:oasis:names:tc:dita:xsd:taskRequirementsDomain.xsd:1.2 uri="taskRequirementsDomain.xsd"/> (based on the new proposed 
naming)

<system 
systemId=urn:oasis:names:tc:dita:machinery:xsd:machineryTask.xsd:1.2 uri="machinerytask.xsd"/> (based on the new proposed 
naming)

<system systemId=urn:oasis:names:tc:dita:machinery:xsd:machineryTaskbodyConstraintMod.xsd:1.2 
uri="machineryTaskbodyConstraintMod.xsd"/> (based on the new 
proposed naming)

 

If someone from the Machine Industry SC would like to 
have the urn's differently, please reply.

 

Best regards

 

Chris

 

 

SeicoDyne 
GmbH

Eichenstrasse 
16

CH-6015 
Reussbühl

Switzerland

Tel: +41 
41 534 66 97

Mob: +41 
78 790 66 97

Skype: seicodyne

 

www.seicodyne.com



 

Member of 
the DITA Technical Committee

Chairman 
of the DITA Machine Industry 
Subcommittee

 

Von: Eric Sirois [mailto:] 

Gesendet: Donnerstag, 16. Oktober 2008 15:07
An: Christian 
Kravogel
Cc: ; 'Robert D 
Anderson'
Betreff: Re: Review on the DITA 1.2 Machine Industry DTDs 
and XSDs

Hi Chris, 

Thanks for the taking the time to review the Machine 
Industry DTD and XSDs. I will update the XSDs soon and post the a XSD package at 
OASIS. 

I have a  quick question 
for you and your SC.  For the XSD I created a URN as unique identifier. 
 As part of the design pattern URN I need a name for the specialization. 
 I use "machine" as the specialization identifier.  Does that work for 
you and the SC or is there a better token that you would prefer. 

Kind regards, 
Eric 

<system 
systemId="urn:oasis:names:tc:dita:spec:machine:xsd:machineIndustry.xsd:1.2"
     uri="machineIndustry.xsd"/>

Eric A. Sirois
Staff Software Developer 
DB2 
Universal Database - Information Development
DITA Migration and Tools 
Development
IBM Canada Ltd. - Toronto Software Lab
Email: 
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public 
information and government 
transactions avoid depending on technologies that 
imply or impose a specific product or 
platform on businesses or citizens" - 
EU on XML-based office document formats. 

  
  

    From: 
    "Christian Kravogel" 
      <> 
  

    To: 
    "'Robert D Anderson'" 
      <>, Eric Sirois/Toronto/IBM@IBMCA 
  

    Cc: 
    <> 
  

    Date: 
    10/14/2008 01:51 PM 
  

    Subject: 
    Review on the DITA 1.2  Machine 
      Industry DTDs and XSDs

Robert, Eric 
  
at the DITA Machine Industry TC 
meeting today we reviewed the DTDs and XSDs and we found some ";)?" who should 
not be there. Guess I made this mistake when I prepared the DTD file. 

  
Attached the 
corrected files. 
  
These are the modifications we made: 
  
Line 294 
old: 
<!ENTITY % supplies.content 
"((%nosupply;)? | 
(%supplyli;)?)" 
new: 
<!ENTITY % supplies.content 
"((%nosupply;) | 
(%supplyli;))" 
  

line 356: 
old: 
<!ENTITY % 
spares.content 
"((%nospares;)? 
| 
(%sparesli;)?)" 

  
new: 
<!ENTITY % 
spares.content 
"((%nospares;) 
| 
(%sparesli;))" 

  
line 418: 

old 
<!ENTITY % safety.content 
"((%nosafety;)? | 
(%safecond;)?)"> 
  
new 
<!ENTITY % safety.content 
"((%nosafety;) | 
(%safecond;))"> 

In the mitaskdomain.xsd schema it is the same 
correction: 

line 519: 
old: 
<xs:complexType name="supplies.content"> 

 <xs:choice> 
  
<xs:group ref="nosupply" minOccurs="0"/> 
  <xs:group ref="supplyli" minOccurs="0"/> 
 </xs:choice> 
</xs:complexType> 

  
new: 
<xs:complexType name="supplies.content"> 

 <xs:choice> 
  
<xs:group ref="nosupply"/> 
  
<xs:group ref="supplyli"/> 
 </xs:choice> 
</xs:complexType> 

  
line 616: 
old: 
<xs:complexType name="spares.content"> 

 <xs:choice> 
  
<xs:group ref="nospares" minOccurs="0"/> 
  <xs:group ref="sparesli" minOccurs="0"/> 
 </xs:choice> 
</xs:complexType> 

  
new: 
<xs:complexType name="spares.content"> 

 <xs:choice> 
  
<xs:group ref="nospares"/> 
  
<xs:group ref="sparesli"/> 
 </xs:choice> 
</xs:complexType> 

  
line 713: 

old: 
<xs:complexType name="safety.content"> 

 <xs:choice> 
  
<xs:group ref="nosafety" minOccurs="0"/> 
  <xs:group ref="safecond" minOccurs="0"/> 
 </xs:choice> 
</xs:complexType> 

  
new: 
<xs:complexType name="safety.content"> 

 <xs:choice> 
  
<xs:group ref="nosafety"/> 
  
<xs:group ref="safecond"/> 
 </xs:choice> 
</xs:complexType> 

  
SeicoDyne GmbH 
Eichenstrasse 
16 
CH-6015 Reussbühl 
Switzerland 
Tel: +41 41 534 
66 97 
Mob: +41 78 790 66 97 
Skype: seicodyne 
  
www.seicodyne.com 
 
  
Member of the 
DITA Technical Committee 
Chairman of 
the DITA Machine Industry Subcommittee 
 [attachment "mitaskDomain.mod" deleted by Eric Sirois/Toronto/IBM] 
[attachment "mitaskDomain.xsd" deleted by Eric Sirois/Toronto/IBM]