1335,23 → 1335,36 |
if (!$objParent) return ''; |
$parentNS = $objParent::ns(); |
|
// http://oid-info.com/cgi-bin/display?a=list-by-category&category=Not%20allocating%20identifiers |
// http://oid-info.com/cgi-bin/display?a=list-by-category&category=Not%20allocating%20identifiers (15 Nov 2023) |
$no_asn1 = array( |
'oid:0.2.228', |
'oid:1.3.6.1.4.1', |
'oid:1.3.6.1.4.1.37476.9000', |
'oid:1.3.6.1.4.1.37553.8.8', |
'oid:2.16.276.1', |
'oid:2.16.756', |
'oid:2.16.756.1', |
'oid:2.16.756.5' |
//'oid:2.25', // according to Olivier, it is OK that UUID owners define their own ASN.1 ID, since the ASN.1 ID is not required to be unique |
//'oid:1.2.840.113556.1.8000.2554' // Adhoc (GUID/UUID-based) customer use. It is probably the same case as the UUID OIDs, after all, these are UUIDs, too. |
//'oid:1.2.840.113556.1.8000.2554', // Adhoc (GUID/UUID-based) customer use. It is probably the same case as the UUID OIDs, after all, these are UUIDs, too. |
//'oid:1.3.6.1.4.1.54392.1', // Another UUID-to-OID method |
//'oid:1.3.6.1.4.1.54392.2', // Another UUID-to-OID method |
//'oid:1.3.6.1.4.1.54392.3', // Another UUID-to-OID method |
); |
|
// http://oid-info.com/cgi-bin/display?a=list-by-category&category=Not%20allocating%20Unicode%20labels |
// http://oid-info.com/cgi-bin/display?a=list-by-category&category=Not%20allocating%20Unicode%20labels (15 Nov 2023) |
$no_iri = array( |
'oid:0.2.228', |
'oid:1.2.36', |
'oid:1.2.250.1', |
'oid:1.3', |
'oid:1.3.6.1.4.1', |
'oid:1.3.6.1.4.1.37476.9000', |
'oid:1.3.6.1.4.1.37553.8.8', |
'oid:2.16.276.1', |
'oid:2.16.756', |
'oid:2.16.756.1', |
'oid:2.16.756.5', |
'oid:2.25' |
); |
|