Re: PaceLinkDelicious, PaceLinkConstruct: @rel values

[Antone Roundy]

On Monday, November 15, 2004, at 08:21  PM, Tim Bray wrote:
On Nov 15, 2004, at 11:09 AM, Antone Roundy wrote:
The risk is the opposite of naming collision--multiple names for 
the same thing.
This is a problem for any format that's extensible in a 
decentralized manner. There's nothing we can do about it.

There is something we can do about it--we can build a few more values 
into the initial registry which are likely to get created
Agreed.  Propose a few and see if you can get consensus.  Write a Pace 
that assumes FieldingLinks.  You might want to wait to see if 
FieldingLinks gets accepted. -Tim

Will do.  At this point, I think we'll have more fruitful discussion if 
we first nail down the shape of the link element, and then work on the 
list of values.

BTW, in case I hadn't said so, +1 on PaceFieldingLinks and in favor of 
closing any competing Paces assuming text gets added saying that URIs 
in @rel are to be compared character-by-character, case sensitively.