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

pays@faugeres.inria.fr
12 Jul 94 08:19:10+0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: John A. Kunze: "IRL opaqueness requirement to be loosened"
- Previous message: John Curran: "Re: questions on URL draft"

    Date: 12 Jul 94 08:19:10+0200

    From: pays@faugeres.inria.fr

    To: ccoprmm@oit.gatech.edu, masinter@parc.xerox.com

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

    Message-Id: <773993950.2372.0-faugeres.inria.fr*@MHS>

>
> While I think we can manage to avoid the character set issue in URNs
> and URLs, I don't think it is avoidable in URCs. In particular,
> attributes such as 'title' and 'author' will ultimately HAVE to face
> that there needs to be a character set for writing them in whatever
> human language they are actually written.
>

Fully agreed.

What might be acceptable for non US-ASCII strings (title, authors aso)
would be to have multiple values
. one in the natural Character-set (with MIME identification)
. an additional one (transcription is US-ASCII)
with preferably some tag to indicate which of the multiple values
is the "official" one

In fact as we experienced in X.500 it is advisable to have as many
alternate values that people (outsiders, foreigners) will
possibly search for...

-- PAP
>

- Next message: John A. Kunze: "IRL opaqueness requirement to be loosened"
- Previous message: John Curran: "Re: questions on URL draft"