# Re: Re URC func spec

Mitra (mitra@pandora.sf.ca.us)
Wed, 23 Mar 1994 03:41:40 GMT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mark P. McCahill: "the one comment I got about nntp section..."
- Previous message: Mitra: "Re: Re URC func spec"
- Maybe in reply to: Terry Allen: "Re URC func spec"
- Next in thread: Michael Mealling: "Re: Re URC func spec"
- Reply: Michael Mealling: "Re: Re URC func spec"
- Reply: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"
- Reply: Michael Mealling: "Re: Re URC func spec"
- Reply: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"

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

    Subject: Re: Re URC func spec

    Date: Wed, 23 Mar 1994 03:41:40 GMT

    Message-Id: <Cn3M9H.2tn@pandora.sf.ca.us>

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.

- Mitra

- Next message: Mark P. McCahill: "the one comment I got about nntp section..."
- Previous message: Mitra: "Re: Re URC func spec"
- Maybe in reply to: Terry Allen: "Re URC func spec"
- Next in thread: Michael Mealling: "Re: Re URC func spec"
- Reply: Michael Mealling: "Re: Re URC func spec"
- Reply: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"
- Reply: Michael Mealling: "Re: Re URC func spec"
- Reply: Daniel W. Connolly: "LISP for Complex URC Sytax [WAS: Re URC func spec ]"