| Previous | Table of Contents | Next |
TaggedComponents contained in TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS profiles are identified by unique numeric tags
using a namespace distinct form that is used for profile tags. Component tags are assigned by the OMG.
Specifications of components must include the following information:
• Component ID: The compound tag that is obtained from OMG.
• Structure and encoding: The syntax of the component data and the encoding rules. If the component value is encoded as a CDR encapsulation, the IDL type that is encapsulated and the GIOP version which is used for encoding the value, if different than GIOP 1.0, must be specified as part of the component definition.
• Semantics: How the component data is intended to be used.
• Protocols: The protocol for which the component is defined, and whether it is intended that the component be usable by other protocols.
• At most once: whether more than one instance of this component can be included in a profile.
Specifications of protocols must describe how the components affect the protocol. In addition, a protocol definition must
specify, for each TaggedComponent, whether inclusion of the component in profiles supporting the protocol is required (MANDATORY
PRESENCE) or not required (OPTIONAL PRESENCE). An ORB claiming to support Full-IOR conformance shall not drop optional components,
once they have been added to a profile.