Re: More Web-developed Open Protocols

I think another aspect to what is going on isn't a rejection of the W3C 
(or any other standards group), but just a lack of familiarity on the part 
of many developers with the standards process.  At the same time, they're 
very familiar with Wikis and open source development and on-line forges, 
so it's an easier step to saying, "hey, let's put a protocol together" 
than it is to figure out how to do the same thing through a standards 
organization when maybe none of them have ever participated in that 
process.

In this type of situation, the answer is to try to show what the 
differences are between the two processes by way of quality control, more 
rapid and broader uptake due to reputation, promotional infrastructure and 
consensus building expertise, and IPR management.

In short, it's still a marketing issue, but in many cases perhaps a 
somewhat different marketing issue than supposed.

Andy.

"Harry Halpin" <hhalpin@w3.org> wrote on 06/13/2010 10:55:53 AM:

> Most of these are being brought together under the "OStatus" banner [1]
> (actual spec here [2]) and implemented by status.net, and rapidly other
> open source social networking projects like Elgg and the media-hit
> Diaspora.
> 
> So, it's pretty clear standardization in the social web world is going 
on
> outside the W3C. I think one discussion to have, which we've had at the
> Social Web XG and have been interviewing folks on [3], is precisely why
> this is the case. It seems to me the main issue is the closed membership
> model, and the second issue is the perceived slow-moving process. It 
might
> be interesting on having a thorough discussion of this.
> 
> Also, what areas outside the Social Web is standardization happening
> outside the W3C that conceivably seems to be a core part of the Web, 
more
> focussed on formats that protocols? Cloud computing? Security/Privacy?
> 
> [1] http://ostatus.org/
> [2]
> 
http://ostatus.org/sites/default/files/ostatus-1.0-draft1-specification.html

> [3] http://www.w3.org/2010/04/21-swxg-minutes.html
> 
> > http://oauth.net/
> >
> > http://diso-project.org/
> >
> > http://www.salmon-protocol.org/
> >
> > http://code.google.com/p/webfinger/
> >
> > http://code.google.com/p/pubsubhubbub/
> >
> >
> >
> >
> >
> > Karl Dubost <karl+w3c@la-grange.net>
> > Sent by: public-vision-newstd-request@w3.org
> > 06/12/2010 01:18 PM
> >
> > To
> > public-vision-newstd@w3.org
> > cc
> >
> > Subject
> > OExchange Technical Specification
> >
> >
> >
> >
> >
> >
> > Another example of a recent specification starting.
> >
> >
> > On Sat, 12 Jun 2010 17:16:42 GMT
> > In OExchange Technical Specification
> > At http://www.oexchange.org/spec/
> >
> > This document describes OExchange, a simple
> > specification for URL-based content sharing on the
> > web. OExchange codifies an existing model in wide
> > use today, adds a dynamic discovery capability,
> > and creates a foundation for additional verbs.
> >
> > This is the technical specification. The Quick
> > Start Guide provides a short introduction to the
> > protocol and its practical implementation.
> >
> >
> > --
> > Karl Dubost
> > Montréal, QC, Canada
> > http://www.la-grange.net/karl/
> >
> > See the new Gesmer.com http://www.gesmer.com
> >
> > _____________________________________________________________
> > Any tax information or written tax advice contained herein
> >    (including any attachments) is not intended to be and
> >    cannot be used by any taxpayer for the purpose of avoiding
> >    tax penalties that may be imposed on the taxpayer. (The
> >    foregoing legend has been affixed pursuant to U.S.
> >    Treasury Regulations governing tax practice.)<br><br>
> >
> >    Electronic mail from Gesmer Updegrove LLP, 40 Broad
> >    Street, Boston, MA 02109. Voice: (617) 350-6800, Fax:
> >    (617) 350-6878. This communication is intended only for
> >    the use of the individual or entity named as the
> >    addressee. It may contain information which is privileged
> >    and/or confidential under applicable law. If you are not
> >    the intended recipient or such recipient's employee or
> >    agent, you are hereby notified that any dissemination,
> >    copy or disclosure of this communication is strictly
> >    prohibited. If you have received this communication in
> >    error, please immediately notify Christopher O'Sullivan at
> >    (617) 350-6800 and notify the sender by electronic mail.
> >    Please expunge this communication without making any
> >    copies. Thank you for your cooperation.
> 
>