- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sun, 05 Sep 2010 11:06:29 -0400
- To: RDFa WG <public-rdfa-wg@w3.org>
If there are no objections to this proposal in 7 days, we will close ISSUE-42: DOMString vs. string. http://www.w3.org/2010/02/rdfa/track/issues/42 Mark was right, DOMString is a UTF-16 encoded string and has nothing to do with the DOM - it's just badly named. DOMString maps to whatever language-native type that supports it in the implementing language. There are even instructions on how to map it to unicode: http://dev.w3.org/2006/webapi/WebIDL/#idl-DOMString There is no 'string' type in the latest WebIDL spec, so this issue is fairly straightforward - leave DOMString as-is. I propose that we keep the RDFa API's use of DOMString as-is and close ISSUE-42. Please comment in 7 days from this post if you object to this proposal. If there are no objections within 7 days, ISSUE-42 will be closed. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: WebID - Universal Login for the Web http://blog.digitalbazaar.com/2010/08/07/webid/2/
Received on Sunday, 5 September 2010 15:06:58 UTC