{ "11": "Proprietary" }
Parent node: weid-spec-changes (1.3.6.1.4.1.37553.8.1.8.1.6.1)
Dot notation: | 1.3.6.1.4.1.37553.8.1.8.1.6.1.11 |
ASN.1 notation: | { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) frdlweb(37553) weid(8) org(1) webfan(8) technical-specifications(1) weid-spec(6) weid-spec-changes(1) weid-spec-change-2023-08-07-custom-namespace(11) } |
OID-IRI notation: | /ISO/Identified-Organization/6/1/4/1/Frdlweb/weid/Organization/Webfan/1/6/1/11 |
WEID notation: | weid:1-8-1-6-1-B-7 |
DER encoding: | 06:0F:2B:06:01:04:01:82:A5:31:08:01:08:01:06:01:0B |
Changes with Spec Change 11: Proprietary Namespaces:
Spec Change 11 (07 August 2023) allows custom / vendor-specific WEID sub-namespaces.
Such namespaces must begin with x-
, for example: weid:x-contoso:ABC-DEF-?
could be a WEID defined by Contoso Ltd.
As usual for WEID, the namespace is case insensitive.
To avoid confusion with Spec Change 10 Domain-WEID, the sub-namespace must not contain a dot (.
).
The vendor has complete control over the namespace and can define the behavior. However, it is recommended to make use of Base36 and the weLuhn check digit.
Since the vendor specifies the namespace, it is up to the vendor if they allow the mapping of their WEID-Namespace to the OID-Tree. In comparison to class A/B/C/D WEID which are 100% OID compatible, custom WEID might not be OID-compatible at all.
Currently, the following custom namespaces are known:
weid:x-frdl:[Base36_NS]-[SubNS]:[Base36_ID]-[CheckDigit]
to be defined/implemented by Frdlweb (base idea here).ID | Base36 | ASN.1 IDs (comma sep.) | IRI IDs (comma sep.) | RA | Comment | Created | Updated |
---|---|---|---|---|---|---|---|
No items available |