Hi Harry,
I'm a little fuzzy here too. Let me say that Pete Zehler and I have
repeatedly researched
the XML keyref and idref elements and they just weren't intended for
declaring key element
relationships (they presume that XML _attributes_ and not _elements_ are
being referenced).
However, Pete and I also agreed on WIMS telecons long ago that using
containment was
a bad (fragile) idea. Therefore, all of the WIMS top level objects (Agent,
System, Service,
etc.) have elements that _reference_ related or subordinate objects (Jobs,
Resources, etc.),
using the XxxReference datatypes (which support URI, name, or local integer
ID references),
rather than actually _containing_ the subordinate objects (like IPP unwisely
did).
In particular the WIMS protocol operations now do NOT require absolute URIs
as Agent
references, per Bill Wagner's good comment some time back that absolute URIs
expose
the customer's network topology.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Tuesday, November 08, 2005 12:51 PM
To: imcdonald at sharplabs.com
Cc: wamwagner at comcast.net
Subject: WIMS - containment vs metadata ID REF
My Chicago notes are cryptic about
"containment vs metadata IDRef. Further investigation needed. Ira prefers
containment. Doesn't see how IDRef can be used in the Printing classes".
Is this a last call comment (that's not how I recorded it). Is this a WIMS
protocol comment?
Trying to get this into the minutes in a meaningful fashion.
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20051109/34fee064/attachment.html