# Re: The URN: wrapper and URLs...

Simon E Spero (ses@tipper.oit.unc.edu)
Sun, 17 Oct 93 12:52:28 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Previous message: Simon E Spero: "Re: <'s for URLs"
- In reply to: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Next in thread: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Reply: Kevin Gamiel: "Re: The URN: wrapper and URLs..."

    Message-Id: <9310171652.AA12349@tipper.oit.unc.edu>

    To: Kevin Gamiel <kgamiel@vinca.cnidr.org>

    Subject: Re: The URN: wrapper and URLs...

    In-Reply-To: Your message of "Sun, 17 Oct 93 11:45:06 EDT."

                 <Pine.3.05.9310171105.A10689-c100000@vinca.cnidr.org>

    Date: Sun, 17 Oct 93 12:52:28 -0400

    From: Simon E Spero <ses@tipper.oit.unc.edu>

Kevin Gamiel <kgamiel@vinca.cnidr.org> writes:

>(insert cheesy, practical example of having to rewrite code here...)
>WAIS works fine as is, but because of evolving standards (Z39.50 v2), we
>(WAIS, Inc and CNIDR) are having to rewrite from the ground up. If you
>think having to strip the first 4 bytes from a URL to become compliant is bad,
>try having to add 3 full BER encoded APDUs, not to mention attribute
>sets, element sets, and other assorted horrors!
>

What's this we, white-man? :)

As another practical example, take X.400 '84 vs. X.400 '88.
They made the same mistake, and X.400 '88 just never happened.

If we're going to break existing code for no good reason then we might as
well bring along some jars to the meeting so at least we can get some cash
out of the experience.

Simon

- Next message: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Previous message: Simon E Spero: "Re: <'s for URLs"
- In reply to: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Next in thread: Kevin Gamiel: "Re: The URN: wrapper and URLs..."
- Reply: Kevin Gamiel: "Re: The URN: wrapper and URLs..."