{excerpt:hidden=true}External data type representations{excerpt}
h4. OID
|| ASN.1 Notation | \{joint-iso-itu-t(2) uuid(25) opticks(100896646649726398451451927000444683547) data-types(0)\} ||
|| Dot Notation | 2.25.100896646649726398451451927000444683547.0 ||
|| IRI Notation | oid:/UUID/Opticks/0 ||
h4. Description
This arc contains descriptions of data types which can be used to share Opticks data with other applications. These data types may be used in network protocols, as file formats, or for interactive use in scripting plug-ins. All data type specifications should use a standardized representation such as DTD, XML Schema (XSD), or ASN.1. When an appropriate standardized representation is not available such as when describing the data set structure in an HDF5 file, a complete textual description may be used. Hierarchical definitions which reference other OID registrations may use the global OID or a local OID rooted at {{oid:/UUID/Opticks}}.
A data type may support multiple representations such as XML and defined free form strings. All supported representations should be defined. Different representations must be unambiguous and are usually assigned a representation context. A context might be a file extension, Opticks importer name, or {{StringUtilities}} target format.
Versioning of data types is only allowed if forward and backward compatibility can be guaranteed in an unambiguous manner. ASN.1, for example, allows extension points to be defined in version 1 of a definition. Versioning is discouraged for major changes to formats but may be used, for example, if a previously assumed attribute value of a data object needs to be explicitly overridden. If the assumed default will not adversely interfere with use in an old application, a new version may be created.
Instead of explicit versioning, a sub-arc can be created with leaf nodes defining subsequent versions of a data type. The original OID description should be updated to indicate it has been superseded.
h4. Information
Contact the registration authority if you would like to register an arc describing an Opticks external data type.
h4. Registration Authority
[The Opticks core development team|mailto:dev@opticks.ballforge.net]
h4. OID Tree
{pagetree:root=@parent|excerpt=true}
h4. OID
|| ASN.1 Notation | \{joint-iso-itu-t(2) uuid(25) opticks(100896646649726398451451927000444683547) data-types(0)\} ||
|| Dot Notation | 2.25.100896646649726398451451927000444683547.0 ||
|| IRI Notation | oid:/UUID/Opticks/0 ||
h4. Description
This arc contains descriptions of data types which can be used to share Opticks data with other applications. These data types may be used in network protocols, as file formats, or for interactive use in scripting plug-ins. All data type specifications should use a standardized representation such as DTD, XML Schema (XSD), or ASN.1. When an appropriate standardized representation is not available such as when describing the data set structure in an HDF5 file, a complete textual description may be used. Hierarchical definitions which reference other OID registrations may use the global OID or a local OID rooted at {{oid:/UUID/Opticks}}.
A data type may support multiple representations such as XML and defined free form strings. All supported representations should be defined. Different representations must be unambiguous and are usually assigned a representation context. A context might be a file extension, Opticks importer name, or {{StringUtilities}} target format.
Versioning of data types is only allowed if forward and backward compatibility can be guaranteed in an unambiguous manner. ASN.1, for example, allows extension points to be defined in version 1 of a definition. Versioning is discouraged for major changes to formats but may be used, for example, if a previously assumed attribute value of a data object needs to be explicitly overridden. If the assumed default will not adversely interfere with use in an old application, a new version may be created.
Instead of explicit versioning, a sub-arc can be created with leaf nodes defining subsequent versions of a data type. The original OID description should be updated to indicate it has been superseded.
h4. Information
Contact the registration authority if you would like to register an arc describing an Opticks external data type.
h4. Registration Authority
[The Opticks core development team|mailto:dev@opticks.ballforge.net]
h4. OID Tree
{pagetree:root=@parent|excerpt=true}