- From: John Stracke <francis@ecal.com>
- Date: 1999年9月21日 09:35:23 -0400
- To: dav <w3c-dist-auth@w3.org>
- Message-ID: <37E7899B.EE02D2DE@ecal.com>
Greg Stein wrote: > John Stracke wrote: > > > Mmm...yes, OK, that makes sense. Do you think <DAV:namespace> should contain the URI directly, or > > contain <DAV:href>? The former reduces bandwidth & complexity by a tiny amount; the latter leverages the > > existing definitions better. > > The namespace is a URI. I believe an href is typically a URL (certainly > "href" connotes this meaning). <dig, dig>...the DAV spec says "URI". > So... I would recommend that it just directly contains the URI rather > than yet-another-element. This was the way I was leaning, too. The main question that made me wonder was, suppose someone wants to define a type of namespace that's defined by something other than a URI? (In such a case, it might be best to be able to swap out the <href> element for something else.) However, I think the answer is that they should just define a new URI scheme. -- /=================================================================\ |John Stracke | http://www.ecal.com |My opinions are my own. | |Chief Scientist |================================================| |eCal Corp. |When rats leave a sinking ship, where exactly do| |francis@ecal.com|they think they're going? | \=================================================================/
Received on Tuesday, 21 September 1999 09:35:51 UTC