# Re: Re URC func spec

Michael Mealling (ccoprmm@oit.gatech.edu)
Wed, 23 Mar 94 11:55:00 EST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"
- Previous message: Tim Berners-Lee: "URLs: Change History"
- In reply to: Mitra: "Re: Re URC func spec"
- Next in thread: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"

    From: ccoprmm@oit.gatech.edu (Michael Mealling)

    Message-Id: <199403231655.AA07643@oit.gatech.edu>

    Subject: Re: Re URC func spec

    To: mitra@pandora.sf.ca.us (Mitra)

    Date: Wed, 23 Mar 94 11:55:00 EST

    In-Reply-To: <Cn3M9H.2tn@pandora.sf.ca.us>; from "Mitra" at Mar 23, 94 3:41 am

Mitra said this:
>I would say that a URC can only contain a URN or a URC as the data field - i.e.
>as associated with some meta-info. Since any character can be in the
>data field, it makes sense that a suitably escaped URN could be there.
>
>
> For example a URC might be
>
> URN: path.net/mitra/1234
> Author: Mitra <mitra@path.net>
> OldVersion: URN:path.net/mitra/1233
> RelatedDoc: URC:URN: path.net/mitra/1232 Author: Fred
>
> I'm not sure how we do the escaping etc and syntax, but think this is a
> reasonable example of the content being conveyed.

Correct. My objection would against encoding the URN as a field since you
can accomplish the same thing by allowing a URC to contain more than
one URN. (If this is objectionable then just consider it as two or more
URCs that have been stuck together with some rules for what that means).
Then you can come up with some very flexible fields for what
relationship that element has to it's previous equal (in the precedence
sense). One example that Terry brought up offline was something like this:

URN:bla
TITLE:Mody Dick
URL:http://bla/bla
Cost: US$39.95
URN:bla
Relationship_Type: Version
Title: Moby Dick- The Abridged Version
URL:gopher://bla
Cost: US$2.00

This allows for two URNs for similiar resources that are not
considered equal but instead are just similar. It does the same thing as your
example but is much more parsable. Comments?

-MM

    --
    ------------------------------------------------------------------------------
    Michael Mealling                     ! Hypermedia WWW, WAIS, and gopher will be
    Georgia Institute of Technology      ! here soon via MIME. Your view of the
    Michael.Mealling@oit.gatech.edu      ! internet is about to change completely!

- Next message: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"
- Previous message: Tim Berners-Lee: "URLs: Change History"
- In reply to: Mitra: "Re: Re URC func spec"
- Next in thread: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"