Dashboard > The DataPortability Project > ... > Steering > Relationship to W3C
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Relationship to W3C
Added by Harry Halpin , last edited by Harry Halpin on Apr 14, 2008
Labels: 
(None)

 How does DataPortability.org relate to existing standards bodies?

 One way is through an http://www.w3.org/2005/Incubator/

 Through the Social Web XG, the W3C will have an official conduit for keeping track of DataPortability.org. Also, since an XG (Incubator Group) is not chartered to make standards, but can recommend standardization work.

Advantages:

  • Possibility of linking into the W3C process, a way of staying in touch
  • May help get the W3C to commit resources to social network portability if needed in future.
  • Would be useful to doublecheck anything out of DataPortability.org and draw it to W3C attention
  • Also, perhaps a way to make sure things stay royalty-free.
  • Can help network DataPortability.org output with other W3C Working Groups to check for compatibility.
  • May help give weight to DataPortability.org efforts.

Disadvantages:

  •  W3C is viewed semi-closed, i.e lots of people may not have membership. But can be addressed through Invited Expert status.
  • W3C is viewed as slow and cumbersome, but the Incubator Process is viewed as more agile.

Examples of previous Incubator Groups: The Emotion Markup Language Group to add standardized markup to areas like speech synthesis: http://www.w3.org/2005/Incubator/emotion/

Draft Charter of Social Web Incubator Group on ESW Wiki: http://esw.w3.org/topic/SocialWebXGCharter

Please comment!  

I'd suggest the IETF - as a more open process than W3C, and one with a commitment to "rough consensus and running code." 

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators