W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

IOR Questions

From: David Orchard <dorchard@bea.com>
Date: Mon, 8 Nov 2004 09:27:39 -0800
Message-ID: <32D5845A745BFB429CBDBADA57CD41AF0B8D77A0@ussjex01.amer.bea.com>
To: <public-ws-addressing@w3.org>
To all the IOR experts,


I've been reading through the IOP/IOR stuff, and I had some questions.
Hopefully you can answer..


My understanding of IORs is that an IOR consists of a type value +
sequence of profiles.  Profile consists of a tag + profile specific
data.  The profile specific data contains version, host and port
information.  The optional profile data consists of a buncha components.
These components are roughly policy information (security, transaction)
and address/identifier information (alternative IIOP Address, object
key, endpoint id position).  


1. Why is it called a tagged profile?  Is the XML analogy a "typed"
profile?  Why not just call it a profile?

2. Is the multicomponent profile simply a way of saying that there's a
bunch of components/properties in the profile, ie multi-component
profile roughly equals EPR scope as it stands today?

3. Why does the IOR spec say so much about how intermediaries deal with
the profile transmission?  It seems like there are 2 sets of data in an
IOR, the "standard" which must always be forwarded and then the
extensions which might not be forwarded.  And would you expect that this
IOR material would go away, that it would be best to forward all the IOR

4. What is the relationship between corbaloc URIs and IORs?  I think
that the corbaloc URI schema is a subset of the IOR in that it doesn't
serialize the profile data but provides a URI form for the
version/host/port info.  But it could be a full serialization of the IOR
into string format using the IOR->CDR->String rules in 13.6.9...  help?

5. what else am I missing in my cluelessness?








Received on Monday, 8 November 2004 17:28:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:21 UTC