Issue 2669: INS: compliance with RFC2396 (naming_ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: Given that the FTF is considering changes to the URL schemes proposed by the Interoperable Name Service proposal it may be worthwhile to raise the issue of compliance with RFC2396 again. RFC2396 defines Uniform Resource Locators. The INS RFC (orbos/97-12-20) required that submissions specify a relationship between CosNaming::Names and Uniform Resource Locators (URLs). I assume it was implied that proposals must comply with the current IETF specification for the Uniform Resource Locator (URL) generic syntax. RFC2396 uses the more general term Uniform Resource Identifier (URI). It makes a clear distinction between two orthogonal parts of a URI. The first part specifies how a remote resource can be located and retrieved. When describing the distinction between the two parts the RFC refers to this first part as the Uniform Resource Locator (URL) to stress the aspect of "locating" a remote resource. The second, optional component of a URI is the fragment identifier. This part of the URI contains information that is interpreted by the user agent AFTER the retrieval action has been successfully completed. The proposed iiopname (or corbaname) scheme also has two components, one part is used essentially as if it was a iioploc URL to LOCATE an object of type CosNaming::NamingContext. The second component is interpreted, by the ORB that uses the URL, AFTER the object was retrieved, to resolve a stringified CosNaming::Name relative to that context. Clearly, these two aspects of the bootstrapping mechanism: (1) locating the naming context, and (2) resolving the name, are better defined as orthogonal components. An ordinary URL, for example using the iioploc scheme, suffices for locating the naming context. A fragment identifier, separated from the URL by the "#" character, is the ideal place for the stringified name that is interpreted on the client-side. Resolution: A separator for corbaname is appropriate. This simplified the description of corbaname, into essent Revised Text: Original Section 4.6.2 (3.6.2) iioploc becomes corbaloc, 3.6.3 becomes corbaname with examples and corbaname text changes to reflect corbaname is a simple extension of corbaloc. See final submission edit document Section 3.6.2. (Change of name from iiop... to corba... covered in issue 2794) Actions taken: May 28, 1999: received issue May 4, 2000: closed issue Discussion: :Names and Uniform Resource Locators End of Annotations:===== Date: Fri, 28 May 1999 16:23:15 +1000 (EST) From: Michi Henning To: issues@omg.org Subject: Naming FTF: erroneous exception on resolve_str() Message-ID: Organization: Triodia Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: 1505b816f31c66cfa361666bb640d1fe Hi, CosNaming::NamingContextExt::resolve_str() has AlreadyBound in its raises expression. That's an editorial mistake: the AlreadyBound exception doesn't make sense for this operation and should be removed. Cheers, Michi. -- Michi Henning +61 7 3236 1633 Triodia Technologies +61 4 1118 2700 (mobile) PO Box 372 +61 7 3211 0047 (fax) Annerley 4103 michi@triodia.com AUSTRALIA http://www.triodia.com/staff/michi-henning.html