> 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?


> The context-set document should give XML examples of what
> zrx.supports_* searches for.

Yup.

>
> 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"

If the server treated them as words, then it might normalise away the '.'s
Same reason that we have cql.number vs cql.string.

Rob

--
      ,'/:.          Dr Robert Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.
I L L U M I N A T I  L5R Shop: http://www.cardsnotwords.com/