Subversion Repositories oidinfo_new_design

Rev

View as "text/xsd" | Blame | Last modification | View Log | RSS feed

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  3. <xsd:schema targetNamespace="http://oid-info.com"
  4.             xmlns="http://oid-info.com"
  5.             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  6.             xmlns:xhtml="http://oid-info.com/xhtml-light.xsd">
  7.  
  8.   <xsd:import namespace="http://oid-info.com/xhtml-light.xsd"
  9.               schemaLocation="http://oid-info.com/xhtml-light.xsd"/>
  10.  
  11.   <xsd:element name="oid-database">
  12.     <xsd:annotation>
  13.       <xsd:documentation>
  14.         This schema contains the XML format needed to create and describe
  15.         one or more object identifiers (OIDs) in the OID repository
  16.         located at http://oid-info.com.
  17.         N.B.: Each file can only contain one top-level <oid-database/> tag.
  18.         To submit your XML file, go to http://oid-info.com/submit.htm
  19.         Example of an "oid-database" XML file:
  20.  
  21.         <!--
  22.         <oid-database>
  23.                 <submitter>
  24.                         <first-name>John</first-name>
  25.                         <last-name>Smith</last-name>
  26.                         <email>john.smith@myhost.com</email>
  27.                 </submitter>
  28.        
  29.                 <oid>
  30.                         <value>{joint-iso-itu-t(2) example(999) xml-submission(777)}</value>
  31.                         <synonymous-identifier>oid-repository</synonymous-identifier>
  32.                         <description>Example of a description conforming to the
  33.                            <a href="http://oid-info.com/oid.xsd">XML Schema of
  34.                            the OID Repository</a>.</description>
  35.                         <information>More information can be found at
  36.                            <a href="http://oid-info.com/submit.htm">Submit OID
  37.                            descriptions as XML files</a>.</information>
  38.                         <current-registrant>
  39.                                 <first-name>John</first-name>
  40.                                 <last-name>Doe</last-name>
  41.                                 <email>john.doe@dummy.com</email>
  42.                                 <modification-date>2002-05-25</modification-date>
  43.                         </current-registrant>
  44.                         <first-registrant>
  45.                                 <first-name>Paul</first-name>
  46.                                 <last-name>Connor</last-name>
  47.                                 <email>paul.connor@myhost.com</email>
  48.                                 <creation-date>1999-12-31</creation-date>
  49.                         </first-registrant>
  50.                 </oid>
  51.         </oid-database>
  52.         -->
  53.  
  54.       </xsd:documentation>
  55.     </xsd:annotation>
  56.  
  57.     <xsd:complexType>
  58.       <xsd:sequence>
  59.         <xsd:element name="submitter" type="Submitter">
  60.           <xsd:annotation>
  61.             <xsd:documentation>
  62.                 The submitter is the person (probably you!) who creates the XML document
  63.                 conforming to this XML schema.
  64.             </xsd:documentation>
  65.           </xsd:annotation>
  66.         </xsd:element>
  67.        
  68.         <xsd:element name="oid" type="Oid" minOccurs="1" maxOccurs="unbounded">
  69.           <xsd:annotation>
  70.             <xsd:documentation>
  71.                 Fill one <oid/> element per OID to be added in the database.
  72.             </xsd:documentation>
  73.           </xsd:annotation>
  74.         </xsd:element>
  75.       </xsd:sequence>
  76.     </xsd:complexType>
  77.   </xsd:element>
  78.  
  79.          
  80. <!-- Here begins the description of an object identifier (OID). -->
  81.   <xsd:complexType name="Oid">
  82.     <xsd:sequence>
  83.       <xsd:element name="value">
  84.         <xsd:annotation>
  85.           <xsd:documentation>
  86.             This is the value (path) of the OID either in ASN.1 notation
  87.             (with or without curly brackets) or in dot notation.
  88.           </xsd:documentation>
  89.         </xsd:annotation>
  90.         <xsd:simpleType>
  91.           <xsd:restriction base="xsd:string">
  92.             <xsd:pattern value="\{?\s*(((([a-z][a-zA-Z0-9\-]*\s*((\s*(0|[1-9][0-9]*)\s*\))?|(0|[1-9][0-9]*))){2,}\s*)|((0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))*))\s*\}?"/>
  93.           </xsd:restriction>
  94.         </xsd:simpleType>
  95.       </xsd:element>
  96.  
  97.       <xsd:element name="synonymous-identifier" minOccurs="0" maxOccurs="unbounded">
  98.           <xsd:annotation>
  99.             <xsd:documentation>
  100.               The <synonymous-identifier/> element is used to associate
  101.               other identifiers (words beginning with a lowercase letter)
  102.               to the last arc of the OID being defined.
  103.               For example "ccitt" is a synonymous id for "itu-t".
  104.               It is recommended to use this element when the dot-notation is
  105.               used to identify the OID in tag <value/>, because in that case
  106.               no identifier is associated with the last arc.
  107.               Note that you should not use this element to add the same
  108.               identifier as the one already associated with the last arc when
  109.               the ASN.1 notation is used to identify the OID in tag <value/>.
  110.               If present, the identifier associated with the last arc in
  111.               tag <value/> is retained as the main identifier to designate the
  112.               arc being defined. Otherwise the first <synonymous-identifier/>
  113.               is used.
  114.             </xsd:documentation>
  115.           </xsd:annotation>
  116.         <xsd:simpleType>
  117.           <xsd:restriction base="xsd:string">
  118.             <xsd:pattern value="[a-z][a-zA-Z0-9\-]*"/>
  119.           </xsd:restriction>
  120.         </xsd:simpleType>
  121.       </xsd:element>
  122.  
  123.       <xsd:element name="description" type="xhtml:xhtml-light">  
  124.         <xsd:annotation>
  125.           <xsd:documentation>
  126.             The <description/> element usually contains a short piece of
  127.             text which describes the purpose of the OID. A subset of XHTML
  128.             (in particular, <a href="..."/> in lowercase letters) can be used.
  129.             Note that non ASCII characters should be coded in a form such as
  130.             &#233; (instead of a latin small letter e with acute). Note also
  131.             that newline characters will be replaced by the HTML tag <br/>
  132.             except if you select the -ignoreNL option at
  133.             http://oid-info.com/submit.htm when
  134.           </xsd:documentation>
  135.         </xsd:annotation>
  136.       </xsd:element>
  137.  
  138.       <xsd:element name="information" type="xhtml:xhtml-light" minOccurs="0" maxOccurs="1">
  139.         <xsd:annotation>
  140.           <xsd:documentation>
  141.             The <information/> element gives more information about the
  142.             OID. URLs, references to documents and standards, and rules on how
  143.             to create subarcs are expected. A subset of XHTML (in particular,
  144.             <a href="..."/> in lowercase letters) can be used.
  145.             Note that non ASCII characters should be coded in a form such as
  146.             &#233; (instead of a letter e with acute accent). Note also that
  147.             newline characters will be replaced by the HTML tag <br/> except
  148.             if you select the -ignoreNL option at http://oid-info.com/submit.htm
  149.           </xsd:documentation>
  150.         </xsd:annotation>
  151.       </xsd:element>
  152.  
  153.       <xsd:element name="current-registrant" minOccurs="0" maxOccurs="1">
  154.           <xsd:annotation>
  155.             <xsd:documentation>
  156.               The <current-registrant/> element is used to indicate the
  157.               person or company (different from the first RA) who is
  158.               currently in charge of the OID, allocating subarcs and
  159.               registering information on these subarcs (see
  160.               http://oid-info.com/faq.htm#registration-authorities). If the
  161.               current RA is known, it is recommended to fill this element
  162.               because the identified contact will be automatically notified by
  163.               email each time someone creates a child OID, or submits
  164.               modifications on the current OID or on any child OID. If this
  165.               OID was recently allocated, the current RA is probably still the
  166.               first RA, so please fill the boxes in the <first-registrant/>
  167.               element below.
  168.             </xsd:documentation>
  169.           </xsd:annotation>
  170.         <xsd:complexType>
  171.           <xsd:complexContent>
  172.             <xsd:extension base="Registrant">
  173.               <xsd:sequence>
  174.                 <xsd:element name="modification-date" minOccurs="0" maxOccurs="1">
  175.                   <xsd:annotation>
  176.                     <xsd:documentation>
  177.                         The <modification-date/> element is used to describe
  178.                         when the current-registrant was nominated (if known).
  179.                         The date format is CCYY-MM-DD or CCYY/MM/DD or CCYY-MM or
  180.                                            CCYY/MM or CCYY.
  181.                     </xsd:documentation>
  182.                   </xsd:annotation>
  183.                   <xsd:simpleType>
  184.                     <xsd:restriction base="xsd:string">
  185.                        <xsd:pattern value="[0-9]{4}([/-](0?[1-9]|1[1-2])([-/](0?[1-9]|[1-2][0-9]|3[0-1]))?)?"/>
  186.                     </xsd:restriction>
  187.                   </xsd:simpleType>
  188.                 </xsd:element>
  189.               </xsd:sequence>
  190.             </xsd:extension>
  191.           </xsd:complexContent>
  192.         </xsd:complexType>
  193.       </xsd:element>
  194.  
  195.       <xsd:element name="first-registrant" minOccurs="0" maxOccurs="1">
  196.         <xsd:annotation>
  197.           <xsd:documentation>
  198.                 The <first-registrant/> element is used to indicate the very
  199.                 first person (if known) responsible for managing this OID
  200.                 (see http://oid-info.com/faq.htm#registration-authorities).
  201.                 If the first RA is known, it is recommended to fill this
  202.                 element because the identified contact will be automatically
  203.                 notified by email each time someone creates a child OID, or
  204.                 submits modifications on the current OID or on any child OID.
  205.                 When the responsabilities are transfered to someone else, the
  206.                 <current-registrant/> element above is filled and the data in
  207.                 this element are kept for historic purposes.
  208.           </xsd:documentation>
  209.         </xsd:annotation>
  210.         <xsd:complexType>
  211.           <xsd:complexContent>
  212.             <xsd:extension base="Registrant">
  213.               <xsd:sequence>
  214.                 <xsd:element name="creation-date" type="xsd:date" minOccurs="0" maxOccurs="1">
  215.                   <xsd:annotation>
  216.                     <xsd:documentation>
  217.                         The <creation-date/> element is used to describe when
  218.                         the OID was first registered (if known). It is not the
  219.                         date when the OID description is submitted to the OID
  220.                         repository.
  221.                         The date format is CCYY-MM-DD or CCYY/MM/DD or CCYY-MM or
  222.                                            CCYY/MM or CCYY.
  223.                     </xsd:documentation>
  224.                   </xsd:annotation>
  225.                 </xsd:element>
  226.               </xsd:sequence>
  227.             </xsd:extension>
  228.           </xsd:complexContent>
  229.         </xsd:complexType>
  230.       </xsd:element>
  231.     </xsd:sequence>
  232.   </xsd:complexType>
  233.  
  234.  
  235.   <xsd:complexType name="Submitter">
  236.     <xsd:sequence>
  237.       <xsd:element name="first-name" type="xsd:string" minOccurs="0" maxOccurs="1"/>
  238.       <xsd:element name="last-name" type="xsd:string"/>
  239.       <xsd:element name="email" type="Email">
  240.         <xsd:annotation>
  241.           <xsd:documentation>
  242.                 This email address is for internal use, to keep you informed
  243.                 that the submission went smoothly. It will not be displayed
  244.                 on the web.
  245.           </xsd:documentation>
  246.         </xsd:annotation>
  247.       </xsd:element>
  248.     </xsd:sequence>
  249.   </xsd:complexType>
  250.  
  251.  
  252.  
  253.   <xsd:complexType name="Registrant">
  254.     <xsd:sequence>
  255.         <xsd:annotation>
  256.           <xsd:documentation>
  257.                  At least one of the following elements is required.
  258.           </xsd:documentation>
  259.         </xsd:annotation>
  260.       <xsd:element name="first-name" type="xsd:string" minOccurs="0" maxOccurs="1"/>
  261.       <xsd:element name="last-name" type="xsd:string" minOccurs="0"
  262.       maxOccurs="1">
  263.         <xsd:annotation>
  264.           <xsd:documentation>
  265.              If the registrant is a company or an organization, use the
  266.              <last-name/> element to give its name.
  267.           </xsd:documentation>
  268.         </xsd:annotation>
  269.       </xsd:element>
  270.  
  271.       <xsd:element name="email" type="Email" minOccurs="0" maxOccurs="1">
  272.         <xsd:annotation>
  273.           <xsd:documentation>
  274.              An antispam modifier will be applied to this email address
  275.              when displayed on the web.
  276.           </xsd:documentation>
  277.         </xsd:annotation>
  278.       </xsd:element>
  279.       <xsd:element name="address" type="xsd:string" minOccurs="0" maxOccurs="1"/>
  280.       <xsd:element name="phone" type="xsd:string" minOccurs="0" maxOccurs="1"/>
  281.       <xsd:element name="fax" type="xsd:string" minOccurs="0" maxOccurs="1"/>
  282.     </xsd:sequence>
  283.   </xsd:complexType>
  284.  
  285.   <xsd:simpleType name="Email">
  286.     <xsd:restriction base="xsd:string">
  287.       <xsd:pattern value="[a-zA-Z0-9_\-\.]+@(\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.|([a-zA-Z0-9\-]+\.))+([a-zA-Z]{2,4}|[0-9]{1,3})\]?"/>
  288.     </xsd:restriction>
  289.   </xsd:simpleType>  
  290. </xsd:schema>
  291.