[DDI-SRG] command type

Wendy Thomas wlt at pop.umn.edu
Mon Nov 12 14:44:51 EST 2007


In putting in the information on CommandType I came across a question for 
the group.

1) We have agreed to add a StructuredCommandType that is an empty abstract 
stub for extension where we can add a DDI sanctioned substitution for this 
stub or user can add something else.
Add the new StructuredCommand addition to Command in all parent structures

r:Command is a child of:

comparative element Difference
datacollection element GeneralInstruction
datacollection element DerivationInstruction (note name is being changed 
to GenerationInstruction)


NOW here is the question....

In renaming DerivationInstruction to GenerationInstruction we were going 
to add any missing parts from the current l:GenerationInstruction to the 
renamed DerivationInstruction. this includes a CommandFile Element as 
follows:

             <xs:element ref="CommandFile">
                <xs:annotation>
                   <xs:documentation>An external file containing commands 
for creating the generation.</xs:documentation>
                </xs:annotation>
             </xs:element>

    <xs:complexType name="CommandFileType">
       <xs:annotation>
          <xs:documentation>References a file which contains 
commands.</xs:documentation>
       </xs:annotation>
       <xs:sequence>
          <xs:element name="Location" type="xs:string" minOccurs="0" 
maxOccurs="unbounded">
             <xs:annotation>
                <xs:documentation>Documents the location of the command 
file as human-readable text.</xs:documentation>
             </xs:annotation>
          </xs:element>
          <xs:element name="Path" type="xs:string" minOccurs="0" 
maxOccurs="unbounded">
             <xs:annotation>
                <xs:documentation>Provides a machine-readable path 
expression for the command file's location (eg Java).</xs:documentation>
             </xs:annotation>
          </xs:element>
          <xs:element name="URI" type="xs:anyURI" minOccurs="0" 
maxOccurs="unbounded">
             <xs:annotation>
                <xs:documentation>URI for the command 
file.</xs:documentation>
             </xs:annotation>
          </xs:element>
       </xs:sequence>
       <xs:attribute name="formalLanguage" type="xs:string" use="optional">
          <xs:annotation>
             <xs:documentation>Indicates the formal language of the command 
file.</xs:documentation>
          </xs:annotation>
       </xs:attribute>
    </xs:complexType>


MY QUESTION IS....Shouldn't this be added in addition to 
StructuredCommandType in the three places we were adding that type?

Wendy

Wendy L. Thomas                          Phone: +1 612.624.4389
Data Access Core Director		 Fax:   +1 612.626.8375
Minnesota Population Center              Email: wlt at pop.umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455


More information about the DDI-SRG mailing list