As per Relevance of the word represent, we have this rfc below:
Network Working Group V.
Request for Comments: 2714 R.
Category: Informational S.
Sun Microsystems, Inc
October 1999
Schema for Representing CORBA Object References in an LDAP
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
CORBA [CORBA] is the Common Object Request Broker
defined by the Object Management Group. This document defines
schema for representing CORBA object references in an LDAP
[LDAPv3].
1.
This document assumes that the reader has a general understanding
CORBA
Traditionally, LDAP directories have been used to store data.
and programmers think of the directory as a hierarchy of
entries, each containing a set of attributes. You look up an
from the directory and extract the attribute(s) of interest.
example, you can look up a person's telephone number from
directory. Alternatively, you can search the directory for
with a particular set of attributes. For example, you can search
all persons in the directory with the surname "Smith".
CORBA applications require access to CORBA objects. Traditionally
CORBA applications have used the COS Naming service for storage
retrieval of CORBA object references. When deployed in
with a directory, CORBA applications should be able to use
directory as a repository for CORBA object references. The
provides a centrally administered, and possibly replicated,
for use by CORBA applications distributed across the network
Ryan, et al. Informational [Page 1]
RFC 2714 Schema for CORBA Object References October 1999
For example, an application server may use the directory
"registering" CORBA objects representing the services that
manages, so that a client can later search the directory to
those services as it needs
The motivation for this document is to define a common way
applications to store and retrieve CORBA object references from
directory. Using this common schema, any CORBA application
needs to read or store CORBA object references in the directory
do so in an interoperable way
Note that this schema is defined for storing CORBA "
references," not CORBA objects in general. There might be other
to store CORBA objects in an LDAP directory but they are not
by this schema
2. Representation of CORBA Object
This document defines schema elements to represent a CORBA
reference in LDAP directory. Applications in possession of
reference to an object can invoke calls on that object. Such
reference is termed an "interoperable object reference," or IOR
Access to CORBA objects by using IORs is achieved transparently
the application, by means of the General Inter-ORB Protocol
A CORBA object reference is represented in the directory by
object class corbaObjectReference. corbaObjectReference is a
of the abstract corbaObject object class. corbaObjectReference is
auxiliary object class, which means that it needs to be mixed in
a structural object class
The object class corbaContainer is used in a directory entry
represents a CORBA object or object reference. It is a
object class, and when representing an object reference,
corbaObjectReference object class would also need to be present
the entry. corbaContainer is not required when a subclass
corbaObject (such as corbaObjectReference) is mixed in with
structural object class
The definitions for the object classes corbaObject
corbaObjectReference, and corbaContainer are presented in Section 4.
The corbaObject class has two optional attributes:
and description. corbaRepositoryId is a multivalued attribute
is used to store the repository ids of the interfaces implemented
a CORBA object. description is used to store a textual
of a CORBA object
Ryan, et al. Informational [Page 2]
RFC 2714 Schema for CORBA Object References October 1999
The corbaObjectReference class has one mandatory attribute: corbaIor
corbaIor is used to store the object's stringified IOR
corbaIor and corbaRepositoryId are defined in Section 3;
is defined in [v3Schema].
3. Attribute Type
The following attribute types are defined in this document
3.1
This attribute stores the string representation of the
object reference (IOR) for a CORBA object. An IOR is an opaque
for the object which contains the information necessary to locate
object, even if the object is in another ORB
This attribute's syntax is 'IA5 String' and its case
insignificant
( 1.3.6.1.4.1.42.2.27.4.1.14
NAME 'corbaIor
DESC 'Stringified interoperable object reference of a CORBA object
EQUALITY caseIgnoreIA5
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
SINGLE-
)
3.2
Each CORBA interface has a unique "repository id" (also called "
id") that identifies the interface. A CORBA object has one or
repository ids, one for each interface that it implements
The format of a repository id can be any string, but the
specifies four standard formats
a. IDL-
IDL:Prefix/ModuleName/InterfaceName:
Ryan, et al. Informational [Page 3]
RFC 2714 Schema for CORBA Object References October 1999
For example, the repository id for the "NamingContext" in OMG's
Naming module is: "IDL:omg.org/CosNaming/NamingContext:1.0".
b. RMI-
RMI:ClassName:HashCode[:SUID
This format is used by RMI-IIOP remote objects [RMI-IIOP].
"ClassName" is the fully qualified name of the class (for example
"java.lang.String"). "HashCode" is the object's hash code (that is
that obtained by invoking the "hashCode()" method). "SUID" is
"stream unique identifier", which is a 64-bit number that
identifies the serialization version of the class; SUID is
in the repository id
c. DCE-
DCE:
This format is used for DCE/CORBA interoperability [CORBA-DCE].
"UUID" represents a DCE UUID
d. "local
This format is defined by the local Object Request Broker (ORB).
The corbaRepositoryId attribute is a multivalued attribute;
value records a single repository id of an interface implemented
the CORBA object. This attribute need not contain a complete list
the interfaces implemented by the CORBA object
This attribute's syntax is 'Directory String' and its case
significant. The values of this attribute are encoded using UTF-8.
Some values may require translation from their native
in order to be correctly encoded using UTF-8.
( 1.3.6.1.4.1.42.2.27.4.1.15
NAME 'corbaRepositoryId
DESC 'Repository ids of interfaces implemented by a CORBA object
EQUALITY
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
Ryan, et al. Informational [Page 4]
RFC 2714 Schema for CORBA Object References October 1999
4. Object Class
The following object classes are defined in this document
4.1
This structural object class represents a container for a
object
( 1.3.6.1.4.1.42.2.27.4.2.10
NAME 'corbaContainer
DESC 'Container for a CORBA object
SUP
MUST ( cn )
)
4.2
This abstract object class is the root class for representing a
object
( 1.3.6.1.4.1.42.2.27.4.2.9
NAME 'corbaObject
DESC 'CORBA object representation
SUP
MAY ( corbaRepositoryId $ description )
)
4.3
This auxiliary object class represents a CORBA object reference.
must be mixed in with a structural object class
( 1.3.6.1.4.1.42.2.27.4.2.11
NAME 'corbaObjectReference
DESC 'CORBA interoperable object reference
SUP
MUST ( corbaIor )
)
Ryan, et al. Informational [Page 5]
RFC 2714 Schema for CORBA Object References October 1999
5. Security
Obtaining a reference to an object and storing it in the
may make a handle to the object available to a wider audience.
may have security implications
6.
We would like to thank Sanjeev Krishnan of Sun Microsystems,
Nash of IBM, and Jeffrey Spirn of Oracle for their comments
suggestions
7.
[CORBA] The Object Management Group, "Common Object
Broker Architecture Specification 2.2",
http://www.omg.
[CORBA-DCE] Distributed Systems Technology Center and
Equipment Corporation, "DCE/CORBA
Specification", May 1998.
http://www.omg.org/library/schedule
DCE_CORBA_Interworking_RFP.
[LDAPv3] Wahl, M., Howes, T. and S. Kille, "Lightweight
Access Protocol (v3)", RFC 2251, December 1997.
[RMI-IIOP] IBM and Java Software, Sun Microsystems, Inc., "RMI
IIOP", June 1999. http://java.sun.com/products/rmi
iiop/index.
[v3Schema] Wahl, M., "A Summary of the X.500(96) User Schema for
with LDAPv3", RFC 2256, December 1997.
Ryan, et al. Informational [Page 6]
RFC 2714 Schema for CORBA Object References October 1999
8. Authors'
Vincent
Sun Microsystems, Inc
Mail Stop EDUB03
901 San Antonio
Palo Alto, CA 94303
Phone: +353 1 819 9151
EMail: vincent.ryan@ireland.sun.
Rosanna
Sun Microsystems, Inc
Mail Stop UCUP02-206
901 San Antonio
Palo Alto, CA 94303
Phone: +1 408 863 3221
EMail: rosanna.lee@eng.sun.
Scott
Sun Microsystems, Inc
Mail Stop UCUP02-209
901 San Antonio
Palo Alto, CA 94303
Phone: +1 408 863 3222
EMail: scott.seligman@eng.sun.
Ryan, et al. Informational [Page 7]
RFC 2714 Schema for CORBA Object References October 1999
9. Appendix - LDAP
-- Attribute types --
( 1.3.6.1.4.1.42.2.27.4.1.14
NAME 'corbaIor
DESC 'Stringified interoperable object reference of a CORBA object
EQUALITY caseIgnoreIA5
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
SINGLE-
)
( 1.3.6.1.4.1.42.2.27.4.1.15
NAME 'corbaRepositoryId
DESC 'Repository ids of interfaces implemented by a CORBA object
EQUALITY
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
-- from RFC-2256 --
( 2.5.4.13
NAME 'description
EQUALITY
SUBSTR
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024}
)
-- Object classes --
( 1.3.6.1.4.1.42.2.27.4.2.9
NAME 'corbaObject
DESC 'CORBA object representation
SUP
MAY ( corbaRepositoryId $ description )
)
( 1.3.6.1.4.1.42.2.27.4.2.10
NAME 'corbaContainer
DESC 'Container for a CORBA object
SUP
MUST ( cn )
)
Ryan, et al. Informational [Page 8]
RFC 2714 Schema for CORBA Object References October 1999
( 1.3.6.1.4.1.42.2.27.4.2.11
NAME 'corbaObjectReference
DESC 'CORBA interoperable object reference
SUP
MUST ( corbaIor )
)
-- Matching rule from ISO X.520 --
( 2.5.13.5
NAME 'caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
Ryan, et al. Informational [Page 9]
RFC 2714 Schema for CORBA Object References October 1999
10. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Ryan, et al. Informational [Page 10]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
