OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (Second) Last Call for XPointer 1.0

Umm... Only if it tells you that before you click and in this 
case, I still don't think they can make it stick.
It would also have to cover any reuse of the reference if 
entry to the site does not present the warning.  A 
contract cannot be made ex post facto (my guess).  
It would be entrapment otherwise.  It is a weird turn 
but one predicted on the use of the Name to infer 
rights (eg, is a URN like a trademark).

Definitely an RDF application.


Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: John Cowan [mailto:jcowan@reutershealth.com]
Sent: Thursday, January 11, 2001 3:27 PM
To: Jonathan Borden; xml-dev@xml.org
Subject: Re: (Second) Last Call for XPointer 1.0

Jonathan Borden wrote:

> It is entirely another thing to impose conditions on the mere reading of
> XPointer specification which by the way is simply silly language that
> who has ever been involved in the drafting of a software contract ought
> is silly.

Unfortunately it is not simply silly:  it is a command backed
by a threat to sue.  The structure is "If you read this,
and play by our rules, we will not sue you for your
(necessary) infringement; but if you break our rules, we
MIGHT sue you!"