Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-11 Thread Andrew Anderson
;> question >>>>>>> marks in this way (two question marks is probably feasible, but it >>>>> doesn't >>>>>>> appear that one is). I don't believe that the ARK spec and HTTP URIs >>>> are >>>>>

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-10 Thread John Kunze
er or > >>>>> content > >>>>> negotiation standards emerge. > >>>>> > >>>>> Ethan > >>>>> > >>>>> On Sat, Dec 6, 2014 at 10:23 AM, Phillips, Mark < > >> mark.phill...@unt.edu> > >>>>> wrote: > >&g

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-09 Thread Andrew Anderson
ctions of ? and ?? >>>>>> with >>>>>> our systems. >>>>>> >>>>>> I remember the single ? being a bit of a problem to implement in our >>>>>> system stack (Apache/mod_python/Django) and from what I can tell

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-09 Thread Ethan Gruber
n tell > isn't > > >>> possible with (Apache/mod_wsgi/Django) at all. > > >>> > > >>> The ?? inflection wasn't really a problem for us on either of the > > >>> systems. > > >>> > > >>> From co

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-08 Thread John Kunze
K, the issues > around > >>> supporting the ? and ?? inflections don't seem to be related to the > >>> frameworks issues as other issues like commitment to identifiers, the > >>> fact > >>> that ARKs are being used in a redirection

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-08 Thread Conal Tuohy
mmitment to identifiers, the >>> fact >>> that ARKs are being used in a redirection based system like Handles, or >>> the >>> challenges of accessing the item metadata for items elsewhere in their >>> system. >>> >>> I think having a standard

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-08 Thread John A. Kunze
item metadata for items elsewhere in their system. I think having a standard set of request parameters or other url conventions could be beneficial to the implementation of these features by others. Mark ____ From: Code for Libraries on behalf of todd.d.robb...@gmail.c

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-08 Thread Ethan Gruber
. > > Mark > > From: Code for Libraries on behalf of > todd.d.robb...@gmail.com > Sent: Saturday, December 6, 2014 8:23 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] Functional Archival Resource Keys > > This brief

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-06 Thread Phillips, Mark
ntation of these features by others. Mark From: Code for Libraries on behalf of todd.d.robb...@gmail.com Sent: Saturday, December 6, 2014 8:23 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Functional Archival Resource Keys This brief exchang

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-06 Thread todd.d.robb...@gmail.com
This brief exchange on Twitter seems relevant: https://twitter.com/abrennr/status/296948733147508737 On Fri, Dec 5, 2014 at 12:50 PM, Mark A. Matienzo wrote: > Hi Ethan, > > I'm hoping Mark Phillips or one of his colleagues from UNT will respond, > but they have implemented ARK inflections. For

Re: [CODE4LIB] Functional Archival Resource Keys

2014-12-05 Thread Mark A. Matienzo
Hi Ethan, I'm hoping Mark Phillips or one of his colleagues from UNT will respond, but they have implemented ARK inflections. For example, compare: http://texashistory.unt.edu/ark:/67531/metapth5828/ http://texashistory.unt.edu/ark:/67531/metapth5828/? http://texashistory.unt.edu/ark:/67531/metap

[CODE4LIB] Functional Archival Resource Keys

2014-12-05 Thread Ethan Gruber
I was recently reading the wikipedia article for Archival Resource Keys (ARKs, http://en.wikipedia.org/wiki/Archival_Resource_Key), and there was a bit of functionality that a resource is supposed to deliver that we don't in our system, nor do any other systems that I've seen that implement ARK URI