On Wed, May 30, 2007 at 10:43:12AM +0100, Graham Triggs wrote:
> On Tue, 2007-05-29 at 14:58 +0100, James Rutherford wrote:
> > Using UUIDs (as suggested earlier) would *work*, but would produce
> > horrid URLs.
>
> Note that I never suggested using UUIDs as part of a URL. What I said is
> that UU
On Tue, 2007-05-29 at 14:58 +0100, James Rutherford wrote:
> Using UUIDs (as suggested earlier) would *work*, but would produce
> horrid URLs.
Note that I never suggested using UUIDs as part of a URL. What I said is
that UUIDs would give you a robust scheme of internal unique identifiers
- and in
On May 29, 2007, at 9:58 AM, James Rutherford wrote:
> On Tue, May 29, 2007 at 08:21:47AM -0400, Mark Diggory wrote:
>> PI resolvers come in all shapes and sizes, What all your talking
>> about implementing is proxy/resolution. I would highly recommend NOT
>> conflating the PI resolution mechanis
On Tue, May 29, 2007 at 08:21:47AM -0400, Mark Diggory wrote:
> PI resolvers come in all shapes and sizes, What all your talking
> about implementing is proxy/resolution. I would highly recommend NOT
> conflating the PI resolution mechanism (and why do we even have to
> have one) with the url
On Tue, 2007-05-29 at 12:52 +0100, James Rutherford wrote:
> Well if we're going to be strict, we should escape the value of the
> handle 1234/56 as 1234%2F56. Since DSpace already breaks this rule, I
> didn't deem including a colon as such a great crime ;)
Fair point, and you are probably right.
Hey Folks,
PI resolvers come in all shapes and sizes, What all your talking
about implementing is proxy/resolution. I would highly recommend NOT
conflating the PI resolution mechanism (and why do we even have to
have one) with the url path with which a Community, Collection, Item
or Bitstr
On Tue, May 29, 2007 at 11:56:58AM +0100, Graham Triggs wrote:
> On Tue, 2007-05-29 at 11:43 +0100, James Rutherford wrote:
> > I don't see what's so unusual or undesirable about colons. The reasoning
> > behind doing it this way was so that the value after "/uri/" is the
> > canonical form of the
On Tue, 2007-05-29 at 11:43 +0100, James Rutherford wrote:
> I don't see what's so unusual or undesirable about colons. The reasoning
> behind doing it this way was so that the value after "/uri/" is the
> canonical form of the identifier.
The colon is a reserved character, and in this example wou
On Tue, May 29, 2007 at 11:12:13AM +0100, Graham Triggs wrote:
> On Tue, 2007-05-29 at 10:44 +0100, James Rutherford wrote:
> > > 3) Including special characters in the URL string doesn't seem like a
> > > good idea. While they are valid characters, it does take extra
> > > processing to encode/de
On Tue, 2007-05-29 at 10:44 +0100, James Rutherford wrote:
> > 3) Including special characters in the URL string doesn't seem like a
> > good idea. While they are valid characters, it does take extra
> > processing to encode/decode them from layer to layer.
>
> As I mention on the wiki, my curren
On May 25, 2007, at 6:35 PM, Graham Triggs wrote:
> Hi,
>
>> 1) Why would an institution use more than one PI
>> system? How do you determine which PI system generates a PId
>> (base it
>> on collection, community)?
>
> There are a lot of theoretical reasons why multiple PI schemes may
> be
Hi,
> 1) Why would an institution use more than one PI
> system? How do you determine which PI system generates a PId (base it
> on collection, community)?
There are a lot of theoretical reasons why multiple PI schemes may be in
use. Even if you have the simple case of an institute / repository
12 matches
Mail list logo
