From: Clark C . E. <cc...@cl...> - 2002-07-23 16:28:01
|
On Mon, Jul 22, 2002 at 11:18:59PM +0300, Oren Ben-Kiki wrote: | - HTTP only? | | Isn't this a bit restrictive? There *are* other protocols one can use to | fetch web documents (e.g., ftp). And others might be added later on... | What's wrong with keeping our shortcut notation, and merely limiting the | URIs to URLs? | | - Optional end of rainbow => URI allowed? | | Clark mentioned making it optional (an obvious necessity for private types). | If it is optional, what is the problem with using URIs, exactly? If one | chooses to use an 'isbn:...' type family (Ugh), he's merely opted out of | ever supplying a pot of gold at the end of the rainbow, forever. Which he is | allowed to do anyway... First, I was talking with Steve about this one some; how about amending the spec to say: - All URIs must be from the HTTP scheme - The parser should support other scheme so that migration to a less restrictive mechanism is possible. And then we wait for use cases that would require something other than the http scheme. ... Second, I was thining about private types; they are in general rather useless since you can't even match on them; !!x in a query language isn't the same as !!x in a document. Thus, I'm questioning if we even need private types? ... Third, Steve says that _why has referred to "type family" as a domain; this actually sounds like a better word than type family. Thoughts? Best, Clark |