WEID/WEIX - Kennziffern, ID Alphanumerics, Shortened Graph Notation (WEIX) and commercial signs, named sequences

The WEID Repository will allow the registration of WEID and UUID, OID, PEN as WEID or WEIUUID...and provide a method for registration and subregistration... .

What is WEID?

Read the docu article about: WEID

WEID basics...

• OID basics...
• Alphanumeric OID representation
• "-" is the seperator
• A WeLuhn Checknumber is added to every WEID
• The prefix "weid:" directly points to further nodes of the arc (it replaces as prefix): 1.3.6.1.4.1.37553.8 which is thedesignated arc to register any WEID»«OID subsequences for any own purposes out of the responsibillity of FRDLWEB.This feature is in development and any added OIDs maybe will not be activated yet. The registration of WEID Alphanumeric OIDs beneath this arc is managedby Webfan.de in order of FRDLWEB. A registration of those kind of WEID means that you are responsible for any numbers benath your WEID.
• A WEID strictly differs from an WEIX. While WEIX allows the "tree-dimensinal" shortened graph notation,the WEID tree is strictly hierarchically ordered like the OID system excepts (remember it is alphanumeric notated, bar seperated and checksummed).We emphasize that WEID has now an higher priority for us now then the WEIX ideas!
• An UUID Version 5 sha1 namebased from OID namespace 6ba7b812-9dad-11d1-80b4-00c04fd430c8 is generated for each entry.
• Internally (if some one matters), sub-OIDs are (also) associated by its parents UUID.
• A collision of UUIDs will prohibit a new entry - we stay tuned... ...and maybe refrain from the UUID system.
• WEID ordered alphanumerics only allow UPPERCASE characters (I also like to write UUIDs in UPPERCASE).
• Every entry is associated with an UNIQUE identifier (unique within our system) which can be chosen by the one who registers a WEID.The identifier has to be written in lowercase letters, -bars are allowed, no dots, up to 255 characters are allowed.The identifier is also used for the ASN1 Notation of the entry. We just allow ONE identifier for ONE UNIQUE node entry for now.
• Named sequences are a speciall feature of the WEID registry™. They are nested between two Typed Noise™ characters, for the first timethose charachters will be "*" and "@" and written in lowercase and can be up to 36 characters long. A Named Sequence™ can appear anywhere within the WEIDand replace any sequence (NOT a complete!) of a WEID. A WEID parser should replace the name by the sequence it was registered for, this canmake WEIDs look shorter, e.g. weid:12-3A-BC*webfan*45-67 instead of weid:12-3A-BC-ANY7346-OTHER-474H-SEQ45-67. This feature will come within the next weeks,a central named sequence look up register will be established, but for the first time we have a lower priority on this feature.
• We maybe suggest a Wexml microformats like response on a "look-up page" which provides informations about the object type or links to look further or... .
• To every entry one "look-up url" and one "rooting url" can be added.

Further thoughts...

• Regard that there are two types of WEID entries: leaf and node.
• There are exceptions of WEIDs pointing to an object instance (e.g. the subweids of the companies and individuals arc).In most cases a WEID SHOULD point to an objecttype (-description), and not to an instance. To "point" aWEID to a specific instance of an object (like e.g. a specific Rechnung of the object "rechnungen" (http://look-up.webfan.de/weid:1-8-3-3-3-5),your application COULD use notations like the following examples, where "id" or "ID" assigns the objects instance:
  weid:1-8-3-3-3-5,ID:123
  weid:1-8-3-3-3-5;ID:123
  weid:1-8-3-3-3-5|ID:123
  {weid:1-8-3-3-3-5}{ID:123}
  etc...
  just chose your applications notaion adequately.
  {weid:1-8-3-3-3-5}{ID:123}{weid:1-2-3-3-4-0} could be handled as an "ordered weid/oid fractal", for example....
  

Webfan.de Internet Drafts...