Subject: Re: Incorrect mappings in RIM interfaces
The attributes mentioned are by design and not by accident. They do not map to ATTLIST in the DTD (they do not need to). Their purpose is describe relationship attributes for binding to the SQL scehma and future XQuery schema. Michael Joya wrote: > In a couple of places in the RIM spec, there's a mapping from certain getXXX values to attributes that don't exist. For an example of what I'm talking about, here's an excerpt from the table for RegistryEntry: > > RegistryEntry: > > [Method Summary] > Collection getAssociatedObjects() > Returns the collection of Objects associated with this > object. Maps to attribute named associatedObjects. > > Collection getAuditTrail() > Returns the complete audit trail of all requests that > effected a state change in this object as an ordered Collection > of AuditableEvent objects. Maps to attribute named > auditTrail. > > Collection getClassificationNodes() > Returns the collection of ClassificationNodes associated > with this object. Maps to attribute named > classificationNodes. > > In each case, I can't find an ATTLIST containing attributes named "associatedObjects", "auditTrail", or "classificationNodes", nor does it make any sense for there to be a single attribute value in the DTD. I think this part of the ebXML documentation has been brought directly out of someone's JavaDocs and some irrelevant information has been captured into the RIM by accident. > > -- > // Michael Joya > // XML Global Research and Development > // 1818 Cornwall Ave. Suite 9 > // Vancouver, Canada > // 604-717-1100x230 > > ------------------------------------------------------------------ > To unsubscribe from this elist send a message with the single word > "unsubscribe" in the body to: ebxml-regrep-request@lists.ebxml.org -- Regards, Farrukh
begin:vcard n:Najmi;Farrukh tel;work:781-442-0703 x-mozilla-html:TRUE adr:;;;;;; version:2.1 email;internet:najmi@east.sun.com fn:Farrukh Najmi end:vcard
Powered by
eList eXpress LLC