> Date: Wed, 16 Jun 2004 16:50:17 +0100
> From: Robert Sanderson <[log in to unmask]>
> > Hi Rob. Your profile document says:
> > > It is hoped that servers will support the use of proximity to
> > > search for combinations of set, index, attributeType and
> > > attributeValue, but it is recognised that this may not be
> > > possible in all implementations.
> > I think the further discussion, with examples, that's currently in
> > the context-set document belongs here in the profile.
> And not in the context-set? Or in both?
I meant just in the profile, but I could be wrong.
> > The context-set document says:
> > > oid The term is an OID in dotted notation. eg: 1.2.840.10003.3.1
> > What is the purpose of this? (I'm not arguing against it yet,
> > just wanting to understand the rationale.) In what circumstances
> > could a search-term not annotated with this modifier be
> > misinterpreted?
> zrx.set can be either a context set (cql.uri) or an attribute set
> (zrx.oid). The purpose is to not require the server to parse out
> the difference.
> zrx.set any/zrx.oid "1.2.840.10003.3.1 1.2.840.10003.3.2"
So don't we also need zrx.uri?
Also, don't these two relation modifiers (really structure attributes,
of course) belong in a more generic set than ZeeRex?
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ "Beak in beak, vestigal wing in vestigal wing, with a moonful
of spiracles, he's the Guaranteed Eternal Sanctuary Chicken"
-- Nemesis, "Rupper's Steady"
Listen to free demos of soundtrack music for film, TV and radio