- From: Larry Masinter <masinter@adobe.com>
- Date: Sat, 13 Oct 2012 12:55:45 -0700
- To: Robin Berjon <robin@w3.org>, "plh@w3.org" <plh@w3.org>, "Anne van Kesteren (annevk@opera.com)" <annevk@opera.com>, "Peter Saint-Andre (stpeter@stpeter.im)" <stpeter@stpeter.im>, "Pete Resnick (presnick@qualcomm.com)" <presnick@qualcomm.com>, Martin Dürst (duerst@it.aoyama.ac.jp) <duerst@it.aoyama.ac.jp>, "ted.ietf@gmail.com" <ted.ietf@gmail.com>
- CC: "www-archive@w3.org" <www-archive@w3.org>
I know there are a lot of private conversations about this, but I'd like to try, in the time frame of the next W3C TPAC and IETF meetings, to work out a solution to the issue of "forking" the URL specifications. Does everyone know what the issues are?
Is everyone willing to talk about solutions?
I think forking is harmful and unnecessary.
Bcc: "public-ietf-w3c@w3.org" IETF W3C Liaison
"public-webapps@w3.org" W3C Web Applications group chartered to work on something in W3C URL releated
"www-tag@w3.org" W3C Technical Architecture Group, since we discussed it
" public-iri@w3.org" mailing list of IETF IRI working group, responsible for IRI spec
Did I leave anyone out?
Larry
--
http://larry.masinter.net
Received on Saturday, 13 October 2012 19:56:58 UTC