Issue 2904: profile ids & component ids (interop) Source: Real-Time Innovations (Mr. Dave Stringer, dstringer(at)rti.com) Nature: Uncategorized Issue Severity: Summary: Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS in the list of tagged component ids when they are tagged profile ids. Resolution: editorial change to CORBA 3.0 resolved Revised Text: Actions taken: September 28, 1999: received issue October 20, 1999: closed issue Discussion: End of Annotations:===== Date: Tue, 28 Sep 1999 18:38:59 +0100 From: "Dave Stringer" Organization: Nortel Networks X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: interop@omg.org Subject: profile ids & component ids Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: C?A!!iJ/!!@And9I)"e9 apologies if this is already subject of an issue ... Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS in the list of tagged component ids when they are tagged profile ids. Also, 13.6.2.2 claims "ORB services are assigned component identifiers in a namespace that is distinct from the the profile identifiers". What is the significance of this statement? Cheers, Dave Sender: jon@floorboard.com Message-ID: <37F12CB3.20CB468F@floorboard.com> Date: Tue, 28 Sep 1999 14:01:39 -0700 From: Jonathan Biggar X-Mailer: Mozilla 4.6 [en] (X11; U; SunOS 5.5.1 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Dave Stringer CC: interop@omg.org, issues@omg.org Subject: Re: profile ids & component ids References: <37F0FD33.ECA9998D@nortelnetworks.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: ALj!!eRSd9dgRd90X/e9 Dave Stringer wrote: > > apologies if this is already subject of an issue ... > > Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS > in the list of tagged component ids when they are tagged profile > ids. > > Also, 13.6.2.2 claims "ORB services are assigned component > identifiers > in a namespace that is distinct from the the profile identifiers". > What is the significance of this statement? 13.6.2.2 is correct, and 15.7.3 is wrong. 15.7.3 should be reworded to separate TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS from the rest of the list and identify them as profile ids that are required for conformance. -- Jon Biggar Floorboard Software jon@floorboard.com jon@biggar.org Sender: jis@fpk.hp.com Message-ID: <37F12EB4.3D50CDDE@fpk.hp.com> Date: Tue, 28 Sep 1999 17:10:12 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL X-Mailer: Mozilla 4.08 [en] (X11; U; HP-UX B.11.00 9000/889) MIME-Version: 1.0 To: Dave Stringer , Wayne Haughey , Henry Lowe , Andrew Watson , Tom Rutt CC: interop@omg.org Subject: Re: profile ids & component ids References: <37F0FD33.ECA9998D@nortelnetworks.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: G"@e9nn1e9BU:e9/Tid9 Dave Stringer wrote: > > apologies if this is already subject of an issue ... > > Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS > in the list of tagged component ids when they are tagged profile > ids. IMHO those are editorial errors and they should simply be editorially removed from that list in section 15.7.3. [Note: Wayne, Henry here's another one to fix for the PAS submission!] This list should be exactly the same as the one in 13.6.3 I think. > Also, 13.6.2.2 claims "ORB services are assigned component identifiers > in a namespace that is distinct from the the profile identifiers". > What is the significance of this statement? I don't know what's so special about "ORB services" - whatever they are. As far as I know component identifiers and profile identifiers are allocated from distinct namespaces. That is why it is OK for the ProfileId TAG_INTERNET_IOP and the ComponentId TAG_ORB_TYPE both to have the value 0. If the namespaces were not distinct this would be problematic since the Id 0 would be ambiguous. Jishnu. -- Jishnu Mukerji Systems Architect Email: jis@fpk.hp.com Hewlett-Packard EIAL, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA. X-Sender: hlowe@emerald.omg.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 29 Sep 1999 08:35:42 -0400 To: Jishnu Mukerji From: Henry Lowe Subject: Re: profile ids & component ids Cc: Dave Stringer , Wayne Haughey , Henry Lowe , Andrew Watson , Tom Rutt , interop@omg.org In-Reply-To: <37F12EB4.3D50CDDE@fpk.hp.com> References: <37F0FD33.ECA9998D@nortelnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-UIDL: HNL!!7SSd9O/O!!dE~!! Jishnu, Thanks. I'll look into when we can "sneak" these editorials in before the PAS for GIOP/IIOP is actually issued as a full standard. Henry ---------------------------------------------------- At 05:10 PM 09/28/1999 -0400, Jishnu Mukerji wrote: >Dave Stringer wrote: >> >> apologies if this is already subject of an issue ... >> >> Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS >> in the list of tagged component ids when they are tagged profile ids. > >IMHO those are editorial errors and they should simply be editorially removed >from that list in section 15.7.3. [Note: Wayne, Henry here's another one to fix >for the PAS submission!] This list should be exactly the same as the one in >13.6.3 I think. > >> Also, 13.6.2.2 claims "ORB services are assigned component identifiers >> in a namespace that is distinct from the the profile identifiers". >> What is the significance of this statement? > >I don't know what's so special about "ORB services" - whatever they are. As far >as I know component identifiers and profile identifiers are allocated from >distinct namespaces. That is why it is OK for the ProfileId TAG_INTERNET_IOP >and >the ComponentId TAG_ORB_TYPE both to have the value 0. If the namespaces were >not distinct this would be problematic since the Id 0 would be ambiguous. > >Jishnu. >-- >Jishnu Mukerji >Systems Architect > >Email: jis@fpk.hp.com Hewlett-Packard EIAL, >Tel: +1 973 443 7528 300 Campus Drive, 2E-62, >Fax: +1 973 443 7422 Florham Park, NJ 07932, USA. Sender: jis@fpk.hp.com Message-ID: <380E1D39.5A0B6F8B@fpk.hp.com> Date: Wed, 20 Oct 1999 15:51:22 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL X-Mailer: Mozilla 4.08 [en] (X11; U; HP-UX B.11.00 9000/889) MIME-Version: 1.0 To: Juergen Boldt CC: issues@emerald.omg.org, interop@emerald.omg.org Subject: Re: issue 2904 -- Interop issue References: <4.1.19991020144604.00ad16d0@emerald.omg.org> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: :G$!!d\^d9Dl#e9ZSLe9 Juergen Boldt wrote: > > This is issue # 2904 > > profile ids & component ids > > Section 15.7.3 includes TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS > in the list of tagged component ids when they are tagged profile > ids. > > Also, 13.6.2.2 claims "ORB services are assigned component > identifiers > in a namespace that is distinct from the the profile identifiers". > What is the significance of this statement? Please make these two separate issues and close the first one (the section 15.7.3 one) since this is being editorially fixed in the 3.0 Drafts. Retain the latter (13.6.2.2) as an issue. Jishnu. -- Jishnu Mukerji Systems Architect Email: jis@fpk.hp.com Hewlett-Packard EIAL, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA.