On 07/20/2010 08:40 PM, Young,Jeff (OR) wrote:
I tried to keep the examples abstract in my earlier message, but
probably to the point of obscurity. If you think these URIs or something
like them would help, then convince someone at OCLC to implement them:
The Ohio State University Libraries seeks a dynamic and creative leader for
the administrative team.
The Assistant Director for Information Technology provides leadership,
vision, and strategic direction for a wide range of digital systems and
services of the Ohio State University Libraries.
Lars,
Just so we're clear, I'm arguing the citations should be separately
identifiable. Web service APIs and HTML mashups create barriers for
interoperability.
Even though libris.kb.se publishes Linked Data URIs, it's hard to guess
how they should choose to support multiple text/plain citation
Young,Jeff (OR) wrote:
http://example.org/manifestation/1/citation-apa.txt (text/plain)
The problem I have with the use of (text/plain) is that too many
platforms still assume / default to latin1 for text/plain. While this
appears to be reducing, with signwriting still coming through the
Stuart,
Sorry, I didn't mean to discount citation representations along other
content-negotiable dimensions. It seems likely that BCP-47
http://tools.ietf.org/html/rfc5646 will eventually be upgraded to recognize
signwriting. If so, my URI pattern suggestion could be extended to support
I suspect this discussion happened on code4lib before the thread got
cross-posting to LLD XG where I first saw it.
There are undoubtedly a ton of diverse use cases, but that doesn't mean
APIs are the best solution. Here are some spitball possibilities for
not just manifestations and we need page
Just to bring things back to where (I think) we started. I think
people
are
talking about three separate things here:
* URIs for bibliographic works (which, as Karen pointed out, are
missing
some crucial bits of info like page numbers)
URIs for bibliographic works: I assume you mean
