Submit OID descriptions as XML files

The form below is used to submit an XML file containing OID descriptions conforming to the XML schema of the OID repository.

If the OID does not yet exist in the OID repository, it is added but the description will not be visible until it is validated by the OID repository administrator (a confirmation will be sent to you by email once this is done).
If the OID is already described in the OID repository, it is ignored.

Note 1: Daniel Marschall has developed an Application Programming Interface (API) in PHP which can help developers in creating such XML files.

Note 2: If you have a text file gathering objects in a MIB, a GDMO module or an LDAP specification, you can send it to the OID repository administrator who has a tool to automatically extract OIDs from such files. Please make sure that the top OID is defined in the file.

XML schema for OID descriptions

XML schema for the allowed subset of XHTML

The example below is an XML document that conforms to our XML schema and contains the description of one OID (namely, {joint-iso-itu-t(2) example(999) xml-submission(777)}).

There can be more than one <oid> block per <oid-database> but only one <oid-database> per XML file.
A father OID does not need to be described in the file prior to its child OIDs because the tool will sort the blocks before adding information to the OID repository.
The <submitter> part contains information about you. This information will not be displayed when people will query the OID repository. It is at that email address that you will receive the result of your XML submission. That email address will also be used to keep you informed if the OID descriptions you submitted are updated in the future.
Note that a subset of XHTML is allowed inside plain text for the <description>, <information> and <address> elements.
In HTML entity references (such as "é", "é"), the ampersand '&' has to be explictly encoded as "&" (e.g. "&eacute;", "&#233;").
More detail about what is allowed for each XML tag is given as <documentation> tags in the XML schema. Please have a look at it.

<oid-database> <submitter> <first-name>John</first-name> <last-name>Smith</last-name> <email>john.smith@myhost.com</email> </submitter> <oid> <asn1-notation>{joint-iso-itu-t(2) example(999) xml-submission(777)}</asn1-notation> <identifier>oid-repository</identifier> <description>Example of a description conforming to the <a href="https://oid-base.com/oid.xsd">XML Schema of the OID repository</a> </description> <information>More information can be found in <a href="https://itu.int/ITU-T/X.660">Rec. ITU-T X.660</a>. </information> <current-registrant> <first-name>John</first-name> <last-name>Doe</last-name> <email>john.doe@dummy.com</email> <address>Street Name Town Country </address> <modification-date>2002-05-25</modification-date> </current-registrant> </oid> </oid-database>

Once added to the OID repository, the above description will be displayed as shown on the display example.

Webmaster

	File (a single XML file containing all the OID descriptions, or a zipped archive of XML files): Your name

	`-test`	Check the validity of your file, and get the list of the OIDs that would be created or modified (without updating the OID repository and informing the OID repository administrator). It is recommended to keep this option checked until there is no remaining error in your XML document.

	`-ignoreNL`	Ignore all newline characters used in text descriptions between XML tags. By default, newline characters are turned into `<br>` elements when displayed in HTML. When this box is checked, newline characters are replaced with a whitespace.