- From: Karl Scheibelhofer <Karl.Scheibelhofer@iaik.at>
- Date: Tue, 28 Nov 2000 08:30:39 +0100
- To: "Tom Gindin" <tgindin@us.ibm.com>
- Cc: "Olivier Dubuisson" <Olivier.Dubuisson@francetelecom.fr>, "XMLSigWG" <w3c-ietf-xmldsig@w3.org>, <SEC_ESI@LIST.ETSI.FR>
> -----Original Message----- > From: w3c-ietf-xmldsig-request@w3.org > [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Tom Gindin > Sent: Monday, November 27, 2000 6:02 PM > To: Karl Scheibelhofer > Cc: Olivier Dubuisson; XMLSigWG; SEC_ESI@LIST.ETSI.FR > Subject: RE: Representation of OIDs as URIs > > > > Why, exactly, are we including the organization specification of the > OID in a URI as a subordinate of the domain name? Both > "etsi.org" and "OID > 0.4.0" refer to the same organization, after all. A meaningful > URI for the > example below is more like: > http://www.etsi.org/oid/1733.1.4.1 or > http://www.etsi.org/oid/electronic-signature-standard/1.4.1 > > The one real advantage of using URI's over OID's to a programmer is > that the programmer can find the assigning authority, and then have a > reasonable chance of finding the definition. i think that this scheme is very hard to handle. you do not get easily from one presentation to the other, at least not in an automated way. additionally, you cannot always assume that the domain name is the same as the top-level part of the OID. regards Karl Scheibelhofer -- Karl Scheibelhofer, <mailto:Karl.Scheibelhofer@iaik.at> Institute for Applied Information Processing and Communications (IAIK) at Technical University of Graz, Austria, http://www.iaik.at Phone: (+43) (316) 873-5540
Received on Tuesday, 28 November 2000 02:32:20 UTC