- From: Larry Masinter <masinter@adobe.com>
- Date: Fri, 29 Jan 2010 10:03:44 -0800
- To: Arthur Barstow <Art.Barstow@nokia.com>
- CC: Robin Berjon <robin@berjon.com>, Doug Schepers <schepers@w3.org>, www-archive <www-archive@w3.org>, public-ietf-w3c <public-ietf-w3c@w3.org>, Graham Klyne <GK@ninebynine.org>
(moving to public w3c/ietf list, not administrative one) With regard to comments on the "widget:" URI scheme. > What does "clear utility" mean in this context and where is the > measurement criteria? > Where can we find an objective and measurable definition of "broad > Internet community"? In particular, where can I find a list of the > members of this community and is this "community" self-selected? These are great questions. I think the guidelines within the IETF (e.g., http://www.ietf.org/tao.html) use the word "community" without defining it precisely. I suppose the "community" is self-selected only in the sense that "anyone who posts on an IETF mailing list" should be given a voice. And of course "clear" and "utility" are subjective enough; I suppose when we wrote that in the URI guidelines we imagined that this wouldn't be hard actually be hard to do! I mean, it was my opinion that the registration document doesn't show why "widget://<garbage>/stuff" is more useful than "thismessage:/stuff" since <garbage> isn't defined in the document. If the document explained how it was useful (you know, like even gave a hint of a use case), then the utility would likely be clearer. If there are a lot of people who think something isn't "clear", clarifying the document will improve the chances that more people will think it is clear, enough to believe that the "community" generally thinks it is clear. I gave my opinion. I'm surprised you can't just try a little harder to clarify things, rather than try to formally ask for a precise definition of "clear utility". The "measurement criteria" aren't defined, but the process is. The process is "expert review"; and if the "expert" wants, the expert can call for "IETF review" and "IESG decision". Anyway, in this process, I'm not a gatekeeper; I *do* think the IETF process should be followed and the criteria for new URI schemes met, and I don't think you have to work so hard to do that. I mean, if you really can't easily come up with a use case where you can use widget: and you couldn't use thismessage:, and put that use case in the document, where's the "clear utility"? Larry
Received on Friday, 29 January 2010 18:04:29 UTC