- From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
- Date: Thu, 7 Sep 2000 10:38:45 -0700
- To: "Simon St.Laurent" <simonstl@simonstl.com>, <XML-uri@w3.org>
> That's not an answer, just an astoundingly weak debating > point. Sorry! See below. > Something more concrete would be appreciated, as it's pretty > obvious that > there are multiple conflicting interpretations. > > >Just as well as "New York" identifies the city identified by > the name "New > >York" > > Yes, and New York is an incorporated body - several, > actually, with fixed > geographic and political boundaries. There's a there there, > whatever the > context may be. There's no there there for > http://www.w3.org/1999/xhtml, > which is pretty poor practice for a tool we expect people to > use day in and > day out. You probably was told this definition of New York by some school teacher a long time ago or reading it in a book. Both are mechanisms for "resolving" a name and getting a definition for what the name means. On the Web, we do a GET on a URI and get back a description of what that resource is. In other words, the resource will tell you what kind of resource it is. Furthermore, it is possible for resources to describe other resources which also might be used to describe what kind a resource is. This is a perfectly consistent and decentralized world view. > >For "elements of the common syntax", the equality operation > is defined by > >RFC 2396. For everything else, you use case-sensitive matching. > > That's not specified anywhere I've seen, except in the > Namespaces in XML > Rec that got us into these problems in the first place. No, the XML-NS doesn't make it clear that the first part of the sentence is true. RFC 2396 specifies the equality rules for each common syntax element. Henrik
Received on Thursday, 7 September 2000 13:38:01 UTC