# Re: New URC Specification is ready....

Larry Masinter (masinter@parc.xerox.com)
Tue, 12 Jul 1994 18:23:06 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Ronald E. Daniel: "HTML archives reorganized"
- Previous message: Michael Mealling: "Re: New URC Specification is ready...."
- Next in thread: Michael Mealling: "Re: New URC Specification is ready...."
- Reply: Michael Mealling: "Re: New URC Specification is ready...."

    To: ccoprmm@oit.gatech.edu

    In-Reply-To: ccoprmm@oit.gatech.edu's message of Tue, 12 Jul 1994 10:18:11 -0700 <94Jul12.101818pdt.2760@golden.parc.xerox.com>

    Subject: Re: New URC Specification is ready....

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <94Jul12.182312pdt.2760@golden.parc.xerox.com>

    Date: 	Tue, 12 Jul 1994 18:23:06 PDT

> You got any suggestions?

I think there are two choices (someone correct me if there are more):

1) the URC is a document, and, as such, is encoded in a character set.

Content-type: text/urc; charset=US_ASCII

Author: Masinter, Larry

2) each attribute value is (possibly) a document, and needs a way to
encode it within the URC.

I don't actually understand how to accomplish 2 if URCs are also
expected to be `transport friendly', i.e., themselves included in
text/plain; charset=US_ASCII messages.

- Next message: Ronald E. Daniel: "HTML archives reorganized"
- Previous message: Michael Mealling: "Re: New URC Specification is ready...."
- Next in thread: Michael Mealling: "Re: New URC Specification is ready...."
- Reply: Michael Mealling: "Re: New URC Specification is ready...."