Next in thread → Next in month →

Re: [tm-pubsubj] [Fwd: NISO-Sponsored INFO URI SchemePublished]

From
"Rtringer-Iye, Ruellen"
Date
2004-01-16T15:41:28+00:00
ID
3098218.1074246668@LITSTRING_07_02
Thread
Re: [tm-pubsubj] [Fwd: NISO-Sponsored INFO URI SchemePublished]
The people working on this proposal are very tied in with digital 
libraries and publishing. I think it will be very influential 
whatever its merits or flaws.

--On Friday, January 16, 2004 7:47 AM -0500 Patrick Durusau 
<> wrote:

> Bernard,
>
> Actually responding to Peter's post below:
>
> Bernard Vatant wrote:
>> Peter
>>
> <snip>
>
>> -----Message d'origine-----
>> De : Peter Brown [mailto:]
>> Envoyé : vendredi 16 janvier 2004 11:16
>> À : tm-pubsubj
>> Objet : Re: [tm-pubsubj] [Fwd: NISO-Sponsored INFO URI Scheme
>> Published]
>>
>>
>> I read through a first draft in November (discussed with a few
>> people at the UK XML Topic Maps conference), but frankly there
>> was not much interest, as the proposal does not seem to offer
>> anything more than, say, Handle-based systems: Further it does
>> not seem to qualify as a specific scheme given that it fails the
>> test of being able to "deliver" (in a service sense not a
>> network or transmission one) anything that the http scheme does
>> not already manage.
>
> Can you say a bit more about how:
>
>> it fails the test of being able to "deliver" (in a service sense
>> not a network or transmission one) anything that the http scheme
>> does not already manage.
> ?
>
> As it stands now, the http scheme implies that there is a
> resource that can be found by resolving the URI.
>
> For example, I could write: http://www.loc.gov/lccn/2002022641,
> but most users would expect that to resolve to something. (I just
> checked and it does not.)
>
> So, without constructing any such URIs, the Library of Congress
> can simply say, here is the format to using Library of Congress
> Control Numbers as identifiers.
>
> That seems like a significant advantage to me, at least from the
> standpoint of using legacy identifiers, of which there are quite
> a few.
>
> If your argument is that one "could" use the http scheme to the
> same effect, I suppose that is true, but is contrary to the
> expectation of users.
>
> Note further the limitation of the character set that can be used
> under the http scheme and one starts to see real limitations in
> terms of using   it instead of this most recent proposal.
>
> Hope you are having a great day!
>
> Patrick
>
>
>> BTW, this was the same issue that put the proposed DOI: scheme
>> in the dock
>>
>> Peter
>>
>>
>>
>> To unsubscribe from this mailing list (and be removed from the
>> roster of the OASIS TC), go to
>> http://www.oasis-open.org/apps/org/workgroup/tm-pubsubj/members/
>> leave_workgroup.php.
>>
>>
>
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> 
> Chair, V1 - Text Processing: Office and Publishing Systems
> Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model
>
> Topic Maps: Human, not artificial, intelligence at work!
>
>
>
> To unsubscribe from this mailing list (and be removed from the
> roster of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/tm-pubsubj/members/l
> eave_workgroup.php.
>

---------------------------------------
Stringer-Hye, Suellen
Vanderbilt University
Email: 
Next in thread → Next in month →