From: "Karen Coyle" <[log in to unmask]>
> I looked at that, but I still don't see the actual "list" of elements,
> just info on the structure of the identifiers.
Go to http://www.loc.gov/z3950/agency/zing/srw/infoURI.html to the first
table, a list of object types. The first object type listed is
"cql-context-set". It points to the list:
http://www.loc.gov/cql/context-sets.html go to that page and at the bottom
is a table of "known context sets" which lists their identifiers. Note that
some of the identifiers are 'info' and some aren't (they're 'http') -- SRW
requires that context sets have identifiers, and it offers 'info' as one way
to do it, but it doesn't require that the identifier be an 'info' URI, just
that it be a URI.
>And I'm still confused
> about how "organizations register objects" -- is there a registry for
> the individual objects?
Do you mean "objects" or "object types"?
For object types, in the SRW case, there is a single list,
http://www.loc.gov/z3950/agency/zing/srw/infoURI.html currently listing five
types. New types are added by consensus; organizations may not register
private types. For the actual objects, there should be a separate registry
for each authority.(So at
http://www.loc.gov/z3950/agency/zing/srw/infoURI.html, under "authorities"
we should add a link for each authority.)
> So with a URI like:
> "xv" is the namespace, and that corresponds to a Namespace Authority,
> which appears to be LoC, since LoC has registered the namespace "xv". So
> what you are calling "subauthorities" are not Namespace Authorities in
> the info definition of that. They are really organizations that LoC
> allows to create xv values (presumably as long as they follow certain
> rules). In essence, info could care less about what happens after "xv"
> since LoC is the authority in control of that. How the "xv" namespace is
> used is entirely up to LoC to define,
Right. (Except I would say "entirely up to the xv community to define," LC
acting on behalf of that community.)
> This means that I would still like for us to address the problem set,
> which I sent out before as:
> 1) We have a large number of independent lists that have to be
We have an additional proposal, not quite ready to post yet, that we think
is complementary to the xv proposal. (In fact, the xv proposal could be
integrated into the new proposal.) That is, we think this additional
namespace, tentatively 'cv' for "controlled value", along with 'xv', neatly
partition the problem space of controlled values. We don't suggest that the
xv proposal be approved (or submitted `for 'info' approval) until we can get
this additional proposal out for discussion, which we hope will be soon,
however we do feel that the xv proposal is a separate problem and can be
discussed separately for now.
> > the difference is in the first case, a huge burden is placed on the info
> > registry who probably doesn't want it; in the second case the burden is
> > an organization who has agreed to take it on.
> So you are saying that the registry agency might prefer to have fewer
> namespaces registered.
Yes, is that not a reasonable assumption?
> I guess that will be a question for the permanent
> agency when one is set up. But I think that since we don't know one way
> or the other we should think about what is best for our community, and
> hope that the agency will be able to handle that.
Ok then, what's best for our community?
> > "info:xv/lc/mods/resourceType/oclc/cartoon
> > so LC has (hypothetically) allocated a subspace to OCLC who registers
> > "cartoon" within the subspace.
> That still doesn't tell me where the individual values are registered.
> They are not registered in the info registry. Do you really mean
> "registered" or do you mean that OCLC has an authoritative list that has
> "cartoon" as one value in it?
Both. OCLC has an authoritative list (and, presumably, rules for how objects
are added, which may, but need not, include rules for delegation of
subauthorities), which to me fulfills the definition of "registered".
> And if so, how does one make the
> connection between the URI and actual list?
Each authority provides a list of subauthorites that it has assigned, and
for each, a url.