OK - I was coming up with all this terrifically long ways of having a unique OID for DAS created LDAP metadata.
Then a light bulb turned on (And this very rarely happens). The EPackages that contain SDO Metadata (The metadata for an SDO model) are already namespaced. It's the same concept used to namespace elements in an xml document, and SDO uses this because it has to be able to serialize model instances to XML. For instance Maven POM elements live in the namespace: http://maven.apache.org/POM/4.0.0 Is http://maven.apache.org/POM/4.0.0 a legal OID value? If not we could just generate a checksum of it, or strip out the illegal characters, and use that as the globally unique OID. Then we just use a simple convention like checksum + 1 for the Syntax OID branch checksum + 2 for the AttributeType OID branch etc etc etc Sound OK? Thanks, - Ole
