ViaThinkSoft OIDplus 2.0
ViaThinkSoft Registration Authority
System icon System
oid icon Object Identifier (OID)
     oid: -- ViaThinkSoft
          oid: -- Specifications
               oid: -- Other specifications
               oid: -- File formats
               oid: -- Algorithms
               oid: -- Interfaces
               oid: -- Individual script languages and notations
               oid: -- Communication interfaces
               oid: -- Individual protocols
guid icon Globally Unique Identifier (GUID)
ipv4 icon IPv4 Network Blocks
ipv6 icon IPv6 Network Blocks
oidplus:com.viathinksoft.freeoid icon Register a free OID
oidplus:search icon Search
oidplus:documents$doc/$d0f09d32320cc71896809b62c177ccb5d53b770954450db312d05a039883bb5c60fa1728910f3812934c0f0407e554b640197ab5b95b538fb0730c5eb5029dd9 icon Documents
oidplus:links$links/$245eda5be9dc372e2ba78bc98a2262a917a6c4f4b7c0a5e7b23b8a49dfd593ba4d3c99742b04c0687c22f764c4a391a7f3376492627718799ca7c2af67536f22 icon External resources
oidplus:contact icon Contact sysadmin

Specifications Specifications

Technical information

Dot notation:
ASN.1 notation: { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 37476 specification(3) }
OID-IRI notation: /ISO/Identified-Organization/6/1/4/1/37476/Specification
SHA1 namebased UUID: f7cc2b7a-5a71-503a-9ed8-dbce7bb1b70e
MD5 namebased UUID: 5dcd415f-60fd-301a-10cc-3a630f6b5366



Definition in the Assignment Advisory:

Objects, file formats etc. which are not necessarily product specific - especially objects which can be used for data exchange. The child arcs are defined as follows:

misc(0): Everything that does not fit into the other categories.

fileformat(1): Definition of generic (non product specific) data structures which are encoded into files.

algorithm(2): Generic algorithm definitions (not product or programming language specific).

interface(3): Definition of generic interfaces, e.g. COM+ interfaces.

script(4): Script languages.

communication(5): Definitions how systems and applications should communicate. For example, a JSON data structure embedded in another file or transferred inside a foreign protocol. If you want to define a data structure which is saved entirely in a file, then use the arc fileformat(1) instead. If you want to define a data structure which is sent entirely over a TCP/UDP connection, use the arg protocol(2) intead.

protocol(6): Definitions of data structures sent entirely via network, without usage of other protocols (e.g. HTTP).

Registration Authority

Daniel Marschall

Subsequent objects

ID ASN.1 IDs (comma sep.) IRI IDs (comma sep.) RA Created Updated
0 misc Misc ViaThinkSoft 2011-03-14 2016-12-15
1 fileformat FileFormat ViaThinkSoft 2011-03-14 2016-12-15
2 algorithm Algorithm ViaThinkSoft 2011-03-14 2016-12-15
3 interface Interface ViaThinkSoft 2011-03-14 2016-12-15
4 script Script ViaThinkSoft 2011-03-14 2016-12-15
5 communication Communication ViaThinkSoft 2011-03-14 2016-12-15
6 protocol Protocol ViaThinkSoft 2011-03-14 2016-12-15


Share Static link to this page