On Thu, Nov 12, 2009 at 10:17 AM, Karen Coyle <lists_at_kcoyle.net> wrote:
> Aha! So under what circumstances is that information presented and usable?
> What makes me "know" that I will find that in source? Is this a standard
> practice? Is it a response to a machine query?
These questions are probably better for the id.loc.gov list, since I
can't vouch for this particular decision. For the record, on
lcsubjects.org (or, at least the revision that is currently remodeling
itself on my machine), throws these into a different URI space:
http://lcsubjects.org/schemes/{scheme}#scheme
If I was to take a stab at the motivation for why they chose to
obscure it from the public view is that they probably figured the only
things that cared were rdf-aware agents and the humans who love them.
So when you look at http://id.loc.gov/authorities/ through an RDF
parser, it sees:
http://www.w3.org/2007/08/pyRdfa/extract?uri=http%3A//id.loc.gov/authorities/
I am not sure the value of providing the information in the HTML view
or if the answer is more like what I'm giving you now. It's somewhat
analogous to having a MARC view in an OPAC to a non-librarian without
textual labels for the fields/subfields.
-Ross.
Received on Thu Nov 12 2009 - 10:32:29 EST