On Fri, 18 Jun 2004, Mike Taylor wrote:
> > 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
> > > 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.
Hrm. I'll at least make the note in the profile more extensive, but as
it's really the only way to do a search using index and set, it could be
used in other profiles, so I think it belongs at least in the context set
documentation as well.
> > > The context-set document says:
> > > > oid The term is an OID in dotted notation. eg: 1.2.840.10003.3.1
> So don't we also need zrx.uri?
Nope, as cql has a uri relation modifier already.
Of course that should probably be noted as useful in the profile.
> Also, don't these two relation modifiers (really structure attributes,
> of course) belong in a more generic set than ZeeRex?
URI definitely belongs where it is, but where would OID go?
I guess that it could go into the Network set. Or we could rename ZeeRex
to something more schema neutral. But I don't think it's of broad enough
applicability to go into CQL. Apart from Z39.50, where are oids used
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. 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/