Re: [widgets] dir and span elements
On 12/03/10 7:27 PM, Richard Ishida wrote: I agree with Felix. Note also for example that the HTML 4.01 spec also says This attribute specifies the base direction of directionally neutral text ... in an element's content *and attribute values*. (my emphasis). Ok, I've rewritten the following algorithms to make sure a direction is always associated with a string (as well as the language): http://dev.w3.org/2006/waf/widgets/#rule-for-determining-directionality http://dev.w3.org/2006/waf/widgets/#rule-for-getting-a-single-attribute-valu http://dev.w3.org/2006/waf/widgets/#rule-for-getting-text-content-with-norma There are, of course, some problems with applying directionality to attributes where their base direction is different than that of the element content or they contain text which needs to have embeddings applied to just a part of the text. These are some of the reasons that we and the ITS spec always advise against using user readable text in attributes - use elements for that stuff. Yeah, we kinda stuffed up in a few places then: version attribute of the widget element, the short attribute of the widget name, and possibly the email attribute of the author element. If we find that they start to cause problems in the wild, we might deprecate them in the future in favor of element-based equivalents. Kind regards, Marcos -- Marcos Caceres Opera Software
Request for Comments: Media Resource specs
Hi All, The Media Annotations WG is preparing the following two specs for LC and is seeking comments from the WebApps community: 1. Ontology for Media Resource 1.0 [Version 09 March 2010] http://www.w3.org/TR/2010/WD-mediaont-10-20100309/ 2. API for Media Resource 1.0 [Version 09 March 2010] http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100309/ If you have any comments, please send them to public-media- annotat...@w3.org (archived at [1]). Regarding the deadline for comments, Daniel reports we will start LC in April, thus due is by April. -Art Barstow [1] http://lists.w3.org/Archives/Public/public-media-annotation/ Begin forwarded message: From: ext Soohong Daniel Park soohong.p...@samsung.com Date: March 16, 2010 12:15:48 AM EDT Subject: [W3C Media Annotation WG] Request for Expert Review [1] Ontology for Media Resource 1.0 [Version 09 March 2010] http://www.w3.org/TR/2010/WD-mediaont-10-20100309/ Abstract: This document defines the Ontology for Media Resource 1.0, a core vocabulary to describe media resources on the Web. It is defined based on a core set of properties which covers basic metadata to describe media resources. Further it defines syntactic and semantic level mappings between elements from existing formats. The ontology is supposed to foster the interoperability among various kinds of metadata formats currently used to describe media resources on the Web. [2] API for Media Resource 1.0 [Version 09 March 2010] http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100309/ Abstract: This specification defines a client-side API to access metadata information related to media resources on the Web. The overall purpose of the API is to provide developers with a convenient access to metadata information stored in different metadata formats. The API will be introduced in an abstract manner using the interface definition language Web IDL. Thereby, the Media Ontology Core Properties will be used as a pivot vocabulary in the API.
[widgets] dir and span tests
Hi, I've created a bunch of tests for dir and span and would really appreciate if someone could review them for completeness. They test the most relevant elements affected by dir (span, widget, name, license, description): http://dev.w3.org/2006/waf/widgets/test-suite/i18n-tests.xml The tests are based on the HTML+CSS Internationalization Tests [1]. Please note that there is no reference graphics in the test suite; I intend to use the ones from [1] and a few that I will have to create by hand. The tests are also not documented at this point, but I will get to that too. Eventually, each of the tests will be put into a separate widget file. To make life easier for testers, in some cases, I've combined elements together into a single test. Kind regards, Marcos [1] http://www.w3.org/International/tests/list-html-css#direction -- Marcos Caceres Opera Software
Re: CSS WG comments on View Modes Media Feature spec
On Thu, Mar 11, 2010 at 9:36 AM, Daniel Glazman daniel.glaz...@disruptive-innovations.com wrote: Hi WebApps Working Group. 4. all these queries could/should have an event-based counterpart so the changes are detectable by code. We understand this is outside of the scope of this spec but that's still an important comment. I think CSSOM should cover this (but I don't know if it does). -- Marcos Caceres http://datadriven.com.au
Re: CSS WG comments on View Modes Media Feature spec
On Tue, 16 Mar 2010 20:04:37 +0100, Marcos Caceres marc...@opera.com wrote: On Thu, Mar 11, 2010 at 9:36 AM, Daniel Glazman daniel.glaz...@disruptive-innovations.com wrote: Hi WebApps Working Group. 4. all these queries could/should have an event-based counterpart so the changes are detectable by code. We understand this is outside of the scope of this spec but that's still an important comment. I think CSSOM should cover this (but I don't know if it does). It doesn't and I'm not really convinced it should. At least not as some kind of generic mechanism. That wouldn't work well for some media features and most of the time is really not warranted. -- Anne van Kesteren http://annevankesteren.nl/
Re: [widgets] Span example
Hi Richard, Added the example at: http://dev.w3.org/2006/waf/widgets/#span Please see also the examples for the dir attribute: http://dev.w3.org/2006/waf/widgets/#dir Thanks again for all your time and help! On Tue, Mar 16, 2010 at 7:58 PM, Richard Ishida ish...@w3.org wrote: [This is a continuation of one part of the http://lists.w3.org/Archives/Public/public-i18n-core/2010JanMar/0043.html thread.] It addresses the comment: [[ 7.16. The span Element http://dev.w3.org/2006/waf/widgets/#the-span-element-and-its-attributes [2] I think the example could be improved by having something inside the span with punctuation (eg. exclamation mark) or such, and maybe the description should be in English - otherwise you'd probably want to put the dir on the widget tag and have English in the span. Should I try to find another example ? ]] at http://www.w3.org/International/reviews/0907-widgets-pc/ Here's my proposed example (thanks to Aharon Lanin for helping with the Hebrew). I made up something that might appear in a Hebrew widget, rather than an English one, since it's a little more realistic. widget xmlns=http://www.w3.org/ns/widgets; xml:lang=he dir=rtl name xml:lang=enGPS Weather!/name description יישומון ה-span dir=rtl xml:lang=enGPS Weather!/span מאפשר לך לבדוק את מזג האוויר בכל נקודת GPS ברחבי העולם. /description /widget Here's a version ready to drop into HTML (I suggest you copy it as a unit, to avoid problems with the bidirectional text.) lt;widget xmlns=quot;http://www.w3.org/ns/widgetsquot; xml:lang=quot;hequot; dir=quot;rtlquot;gt; lt;name xml:lang=quot;enquot;gt;GPS Weather!lt;/namegt; lt;description יישומון ה-lt;span dir=quot;rtlquot; xml:lang=quot;enquot;gt;GPS Weather!lt;/spangt; מאפשר לך לבדוק את מזג האוויר בכל נקודת GPS ברחבי העולם. lt;/descriptiongt; lt;/widgetgt; -- Marcos Caceres http://datadriven.com.au
Re: CSS WG comments on View Modes Media Feature spec
On 16/03/10 8:14 PM, Anne van Kesteren wrote: On Tue, 16 Mar 2010 20:04:37 +0100, Marcos Caceres marc...@opera.com wrote: On Thu, Mar 11, 2010 at 9:36 AM, Daniel Glazman daniel.glaz...@disruptive-innovations.com wrote: Hi WebApps Working Group. 4. all these queries could/should have an event-based counterpart so the changes are detectable by code. We understand this is outside of the scope of this spec but that's still an important comment. I think CSSOM should cover this (but I don't know if it does). It doesn't and I'm not really convinced it should. At least not as some kind of generic mechanism. That wouldn't work well for some media features and most of the time is really not warranted. Ok, fair enough - CSSOM might not be the place. Is there a generic CSS mechanism/API to detect query changes? -- Marcos Caceres Opera Software
RE: [widgets] Span example
Argh. Sorry Marcos. The span dir=rtl should of course read span dir=ltr RI Richard Ishida Internationalization Lead W3C (World Wide Web Consortium) http://www.w3.org/International/ http://rishida.net/ -Original Message- From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of Marcos Caceres Sent: 16 March 2010 19:15 To: Richard Ishida Cc: public-webapps; public-i18n-c...@w3.org Subject: Re: [widgets] Span example Hi Richard, Added the example at: http://dev.w3.org/2006/waf/widgets/#span Please see also the examples for the dir attribute: http://dev.w3.org/2006/waf/widgets/#dir Thanks again for all your time and help! On Tue, Mar 16, 2010 at 7:58 PM, Richard Ishida ish...@w3.org wrote: [This is a continuation of one part of the http://lists.w3.org/Archives/Public/public-i18n-core/2010JanMar/0043.html thread.] It addresses the comment: [[ 7.16. The span Element http://dev.w3.org/2006/waf/widgets/#the- span-element-and-its-attributes [2] I think the example could be improved by having something inside the span with punctuation (eg. exclamation mark) or such, and maybe the description should be in English - otherwise you'd probably want to put the dir on the widget tag and have English in the span. Should I try to find another example ? ]] at http://www.w3.org/International/reviews/0907-widgets-pc/ Here's my proposed example (thanks to Aharon Lanin for helping with the Hebrew). I made up something that might appear in a Hebrew widget, rather than an English one, since it's a little more realistic. widget xmlns=http://www.w3.org/ns/widgets; xml:lang=he dir=rtl name xml:lang=enGPS Weather!/name description יישומון ה-span dir=rtl xml:lang=enGPS Weather!/span מאפשר לך לבדוק את מזג האוויר בכל נקודת GPS ברחבי העולם. /description /widget Here's a version ready to drop into HTML (I suggest you copy it as a unit, to avoid problems with the bidirectional text.) lt;widget xmlns=quot;http://www.w3.org/ns/widgetsquot; xml:lang=quot;hequot; dir=quot;rtlquot;gt; lt;name xml:lang=quot;enquot;gt;GPS Weather!lt;/namegt; lt;description יישומון ה-lt;span dir=quot;rtlquot; xml:lang=quot;enquot;gt;GPS Weather!lt;/spangt; מאפשר לך לבדוק את מזג האוויר בכל נקודת GPS ברחבי העולם. lt;/descriptiongt; lt;/widgetgt; -- Marcos Caceres http://datadriven.com.au No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2745 - Release Date: 03/15/10 19:33:00
[IndexedDB] IDBRequest Interface Questions
Hey all, I'm starting to work on a prototype of the IndexedDB spec to get a better understanding of it. While working with the IDBRequest I think I understand why nobody likes the current event-based model. I'm also seeing that as it is currently specified, it doesn't meet the requirements of the web developers we had talked to were looking for in an event based API (per the latest editors draft on March 16). Essentially, what they wanted was a way to add more than one listener for success or error, and it doesn't look like that is currently possible unless you roll your own callback that manages this (which they wanted to avoid doing). As they described it, they wanted to be able to use something like addEventListener with the option of also just setting onsuccess and onerror (much like how XHR works). I also can't seem to figure out what the success event is supposed to be for just about anything. Am I just missing something, or is this not yet specified? Cheers, Shawn smime.p7s Description: S/MIME Cryptographic Signature
Re: [WebSQLDatabase] Adding a vacuum() call
shane, i was hoping you could clarify a few things about AUTO_VACUUM: However, the B-Tree balancing algorithm used by SQLite will attempt to merge pages with neighbors when there space utilization drops below certain thresholds. Minimum average fill for intkey leaves is 50%. For other pages I think it's 66%. according to http://www.sqlite.org/pragma.html#pragma_auto_vacuum: Auto-vacuum does not defragment the database nor repack individual database pages the way that the VACUUM command does. so the way i understand these statements is: 1. sqlite always attempts to merge mostly-empty pages. the (auto-)vacuum settings have no effect on that. 2. AUTO_VACUUM only moves pages around and deletes the empty ones. it does not try to repack individual pages. however, because of #1, page repacking happens anyway (to some extent), when AUTO_VACUUM is on. am i right? and one more question: Auto-vacuuming is only possible if the database stores some additional information that allows each database page to be traced backwards to its referer. Therefore, auto-vacuuming must be turned on before any tables are created. It is not possible to enable or disable auto-vacuum after a table has been created. what happens if we create a database without AUTO_VACUUM on, insert some data, save it to a file, then turn on AUTO_VACUUM and try to open that database again? will sqlite add the missing information? will AUTO_VACUUM be silently turned off for that database? will we get an error when we try to open/read from/write to that database? anything else that we need to be aware of in this case? thanks, dumi
Re: [WebSQLDatabase] Adding a vacuum() call
On Wed, 17 Mar 2010 01:50:00 +0100, Dumitru Daniliuc d...@chromium.org wrote: shane, i was hoping you could clarify a few things about AUTO_VACUUM: Perhaps this is a bit out of scope of this mailing list ?
