Archives for: October 2009
2009-10-30
Minutes and Resolutions 2009-10-28
- Resolved:
exdefinition to be changed to use the parent's element font size if set onfont-size(just likeem) Rationale: Avoid infinite loops in the spec. :) - Resolved: Preserve CSS2.1's
0.5emfallback in CSS3 Values for when ex height cannot be found. - The CSSWG has no objections in principle to Selectors API 2 introducing a new pseudo-class for its scoping element.
- display: run-in clarifications and drop-shadow proposal (see also targetting filter effects) added to TPAC agenda.
- As of 2003 the CSSValue interface is deprecated+obsolete and other specs should not rely on it. In response to Sylvain's message the CSSWG will update the DOM-L2-Style spec to include this note inline.
- Discussed TPAC agenda, schedules, and presenting at Thursday's Developer Gathering.
2009-10-29
Minutes of October 5 teleconference published
The MW4D IG held its 27th teleconference on October 5 2009.
The approved minutes are available at http://www.w3.org/2009/10/05-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
Guidelines for Web Content Transformation Proxies open for review
More than a year ago, we, the Mobile Web Best Practices Working Group, published a Last Call of a document then called Content Transformation Guidelines, and invited the community to review the document. The document provides guidance to Content Transformation proxies as to whether and how to transform Web content.
Many comments were received. They triggered extensive discussions within the group. Finding the right balance between allowing proxies to alter content that would otherwise not display successfully on mobile devices and reducing side-effects such proxies may have on Web applications already designed for mobile devices is no easy task! Significant changes were brought to the document as a result and another Last Call was published a couple of weeks ago under the title Guidelines for Web Content Transformation Proxies 1.0.
We think we have addressed and replied to all the comments, providing rationale when we have not incorporated the suggested changes. We deeply thank last year's commenters, and apologize for the time it took to address the comments!
Once again, we would like to invite the community at large (and in particular mobile Web authors who are impacted by the deployment of such transcoding proxies) to review and comment the document. The Status of This Document section contains a list of the changes made in response to user feedback.
The Last Call review period ends on 6 November 2009. Comments should be sent to the public-bpwg-comments@w3.org public mailing-list (with public archives).
2009-10-27
HCLS F2F
OWL 2 is a W3C Recommmendation
Today W3C announces a new version of a standard for representing knowledge on the Web. OWL 2, part of W3C's Semantic Web toolkit, allows people to capture their knowledge about a particular domain (say, energy or medicine) and then use tools to manage information, search through it, and learn more from it. As an open standard based on Web technology, OWL 2 lowers the cost of merging knowledge from multiple domains. More than a dozen implementations of OWL 2 are already available. The standard consists of 13 documents, of which 4 are instructional.
2009-10-24
Minutes and Resolutions 2009-10-21
- Reviewed last call comments on Selectors Level 3 from the Protocols and Formats Working Group. Resolved: that their first request is out-of-scope for Selectors. fantasai to respond and answer their other questions.
- Resolved: Remove "Namespaces and down-level clients" (Chapter 11) from Selectors.
- The CSSWG plans to review the state of Selectors implementation reports at TPAC: if we have enough implementation reports, we can move to PR directly.
- Resolved: Yves' comments on the Media Queries and CSS2.1 grammars result in no change.
- Briefly discussed problem with targetting filter effects. As this is a large problem, further discussion is deferred to TPAC and beyond.
2009-10-23
17:52:22, by Richard Ishida 
, 281 words, 74343 views 
Categories: Miscellaneous, Highlight, w3cWebDesign, w3cWebUserAgents
Unicode Collation Algorithm Version 5.2 Released
Version 5.2 of the Unicode Collation Algorithm has been released. This version resynchronizes the Unicode Collation Algorithm with all of the updates for the Unicode Standard, Version 5.2.
The rest of this post is taken from the Unicode Consortium's release notification and details changes and issues for implementations.
- The text of UTS #10 has been updated. Among other changes, the revised text for UTS #10 makes it clear that the BASE for implicit generation of weights for Han characters does not include unassigned code points.
- There are small changes in Gujarati, Telugu, Malayalam (including weighting for chillus), Tamil, and Sinhala. While these changes move in the direction of expected behavior, good results will only come from tailoring for particular languages, such as with CLDR.
- There have been significant changes to the ordering of many combining marks. Many combining marks that are not in customary use in modern languages now have the same secondary weight, and will only be distinguished on a fourth level, by code point ordering. This can be seen by looking at the Unicode Collation Charts (http://unicode.org/charts/collation/). In 5.2, many characters now have a white background, indicating that they sort exactly the same as the previous character, unless a 4th (codepoint) level is used.
- Implementations of UCA should take note that the increased number of characters may cause overflows if the implementing code makes certain assumptions or optimizations. This can result either from the new character additions (which increase the number of distinct weights in the table) or because of changes in the way the weights, particularly for secondary weight values, are assigned in the table. The latter change may result in unexpected numbers of characters having the same weight.
Publication of Three Scientific Discourse Notes
The Semantic Web Health Care and Life Sciences Interest Group is pleased to announce the publishing of three Interest Group notes by the Scientific Discourse Task Force:
- Semantic Web Applications in Neuromedicine (SWAN) Ontology
- SIOC, SIOC Types and Health Care and Life Sciences
- SWAN/SIOC: Alignment Between the SWAN and SIOC Ontologies
These notes describe how one can use the Semantic Web to express and integrate scientific data from different domains and from heterogeneous services. It is hoped that they will inspire further contributions to the ongoing work of the Health Care and Life Sciences Interest Group and its Scientific Discourse Task Force, as well as inspire those in other domains to exploit the Semantic Web. On a related topic, the Interest Group holds a Workshop on Scientific Discourse next monday ISWC 2009
W3C has published three HCLS related Intrerest Group Notes
The W3C Semantic Web in Health Care and Life Sciences Interest Group (HCLS) is pleased to announce the publishing of three Interest Group notes by the Scientific Discourse Task Force:
- SWAN/SIOC: Alignment Between the SWAN and SIOC Ontologies
- Semantic Web Applications in Neuromedicine (SWAN) Ontology
- SIOC, SIOC Types and Health Care and Life Sciences
These notes describe how one can use the Semantic Web to express and integrate scientific data from different domains and from heterogeneous services. It is hoped that they will inspire further contributions to the ongoing work of the Health Care and Life Sciences Interest Group and its Scientific Discourse Task Force, as well as inspire those in other domains to exploit the Semantic Web.
First drafts for SPARQL 1.1 published
The W3C SPARQL Working Group published the First Public Working Draft of six SPARQL 1.1 specifications. SPARQL is the query language of the Semantic Web, and SPARQL 1.1 enhances the SPARQL landscape with:
- SPARQL 1.1 Query - Adds support for aggregates, subqueries, projected expressions, and negation to the SPARQL query language.
- SPARQL 1.1 Update - Defines an update language for RDF graphs.
- SPARQL 1.1 Protocol - Defines an abstract interface and HTTP bindings for a protocol to issue SPARQL Query and SPARQL Update statements against a SPARQL endpoint.
- SPARQL 1.1 Service Description - Defines a vocabulary and discovery mechanism for describing the capabilities of a SPARQL endpoint.
- SPARQL 1.1 Uniform HTTP Protocol for Managing RDF Graphs - Describes the use of the HTTP protocol for managing named RDF graphs on an HTTP server.
- SPARQL 1.1 Entailment Regimes - Defines conditions under which SPARQL queries can be used with entailment regimes such as RDF, RDF Schema, OWL, or RIF.
2009-10-16
CSS3 Backgrounds and Borders Last Call for Comments
The CSS Working Group just published a Last Call for Comments Working Draft of CSS Backgrounds and Borders Level 3. Please review the draft and send your feedback. We'll be accepting comments through 17 November 2009. (Note that feature requests are likely to be deferred to CSS4.) The best place for feedback is the CSSWG's official mailing list www-style@w3.org, but we'll also look at any comments posted (or linked to) from the cross-post on CSS3.info.
There are a couple issues we're specifically looking for feedback on:
Rounding vs. Scaling Down
The round option for background-repeat
and border-image-repeat resizes images to fit the nearest
whole number of tiles, rather than always scaling up or always scaling
down. Rounding keeps closer to the intended size and, in the case
where one dimension is fixed (e.g. in ‘border-image’), keeps the image
closer to the intended aspect ratio. This is almost certainly the best
solution for vector images and high-resolution raster images. However,
if the given image is a low-resolution raster image, it will require
interpolating pixels, which can look bad. See "Rounding Extremes" for
illustrations.
The workaround is to specify a higher-resolution image (e.g. by shrinking from the original with background-size or border-image-width). Possible spec solutions include introducing a separate keyword that always scales down, and changing the algorithm so that we force scaling down whenever interpolation would be required for scaling up. So the options here are
- Leave the spec as-is (always round to nearest): the workaround is good enough for me.
- Trigger forced downscaling when interpolation is needed: avoiding interpolation is important to me and I don't mind that the exact number of tiles is unpredictable and the resulting aspect ratio might skewed a little extra.
- Default to rounding for
round, but I want an extra keyword to force downscaling in all cases (including vector images) because [...]. - Something else?
Please comment on what you prefer and why. (The more specific you can be "for example, this image that I would want to use [...]", the easier it will be for us to understand your point.)
box-break naming
The previous
draft included two properties for controlling behavior at box
breaks (line breaks / column breaks / page breaks):
border-break for controlling whether the border is drawn
at the break, and background-break for controlling
whether the background is drawn for each box individually or for the
whole element as if it were broken after painting.
Hyatt suggested merging the two, so the current draft has a single
box-break property instead. The two values mean,
basically, "render backgrounds and borders for this box, and then
slice it up" and "break the box and then render backgrounds and
borders for each box individually". The value names aren't
particularly clear, however, so we were wondering if anyone has better
ideas.
Conclusion
So take a look at the new draft and send us your comments! This is your last chance to give feedback on this module: if all goes well, we'll be publishing the Candidate Recommendation in time for Christmas, and given the state of experimental implementations right now, I expect things to move rapidly from there.
Device APIs on the way
Back in June, I noted that a new group that would work on Javascript APIs to access device features (such as a camera, an addressbook, a calendar, etc.) had been proposed for review to W3C Members.
Since then, not only was the group approved and started, but we even got our first publication out: a Working Group note describing the expected requirements for these device APIs.
Of course, that document may seem a bit abstract at a first glance: you'll see no API defined in there, nothing with which to play.
But if you think Device APIs are a great opportunity for the Web platform (on mobile and elsewhere), I strongly encourage you to take a look at that document and check if the requirements highlighted there match what you know you'll need from these APIs - and if they don't, please let the Working Group know!
HTML+RDFa First Draft Published
2009-10-14
Minutes and Resolutions 2009-10-14
- Call for agenda items for TPAC F2F meeting
- Reviewed status of CSS Multi-column Layout Last Call comments, specifically:
- Name needs to be changed to match convention.
- Discussed relation of this module's
column-rule-colorto CSS3 Color vs CSS2.1. - Discussed where column rules are drawn: whether they are drawn for empty columns, or empty parts of columns, or always for the entire column box.
- Discussed text-overflow: shrink proposal. A note will be added to the CSS3 Text Editor's Draft about adding a new keyword value to the
text-justifyproperty; the issue is deferred to the next active editor.
2009-10-09
18:14:59, by Richard Ishida , 39 words, 115182 views Categories: Highlight, For review, w3cSemanticWeb, w3cWebDesign, w3cWebArchitecture, w3cWebOfDevices, w3cWebServices, w3cXMLCore, w3cWebUserAgents
Article for wide review: Choosing a language tag
Comments are being sought on this article prior to final release. Please send any comments to www-international@w3.org (subscribe). We expect to publish a final version in one to two weeks. [search keys: qa-choosing-language-tags]
18:10:18, by Richard Ishida , 59 words, 108787 views Categories: Highlight, Update, Articles, w3cSemanticWeb, w3cWebDesign, w3cWebArchitecture, w3cWebOfDevices, w3cWebServices, w3cXMLCore, w3cWebUserAgents
Updated article: Language tags in HTML and XML
This tutorial was updated to incorporate changes made to BCP 47 by the recent publication of RFC 5646. Changes to BCP 47 include the introduction of extended language subtags, and the addition of ISO 639-3 language subtags, bringing the total number of subtags in the registry to almost 8,000.
Translators should consider retranslating the whole tutorial. [search keys: article-language-tags]
Product Modelling using Semantic Web Technologies
...definition, storage, exchange and sharing of product data. Product data is information about the structure and behaviour of things that are realized in industrial processes. So principally product data is about things that are manmade, but it can also be about things in the natural world that interact with those industrial processes and/or its resulting products. Typical products would include automobiles, airplanes, buildings, infrastructures, ships and other manmade complex products.
This report describes the role and scope of product data, and initial work in two technical areas:
- Quantities, Units & Scales; and
- Product Structure - the decomposition of wholes in parts and the interconnection relationships between these parts.
2009-10-07
Minutes and Resolutions 2009-10-07
- Resolved:
roundkeyword forbackground-repeatandborder-image-repeatscales to the nearest whole number of tiles. This will be marked as an issue for feedback in case people prefer different behavior or would like additional controls (e.g.round-uporround-down) keywords). - Resolved: Add percentages to
border-radius. They refer to a percentage of the corresponding dimension of the box (soborder-radius: 50%gives an oval). - Resolved: Publish CSS Backgrounds and Borders Level 3 as Last Call Working Draft
- Last Call period has ended for css3-multicol; Håkon will be compiling comments (not many received).
- fantasai was asked to present on CSS at TPAC's Developer Meeting, and welcomes any suggestions for topics to cover.
13:46:01, by Richard Ishida , 94 words, 64105 views Categories: Miscellaneous, Highlight, w3cSemanticWeb, w3cWebDesign, w3cWebArchitecture, w3cWebOfDevices, w3cWebServices, w3cXMLCore, w3cWebUserAgents
Unicode 5.2.0 Released
On 1st October, Unicode 5.2 was released! The data files, code charts, and Unicode Standard Annexes for this version are final and are posted on the Unicode site.
For Unicode 5.2, the core specification is no longer just a delta document applied to the book; instead, the entire core specification,with all textual changes integrated, will be available on the Unicode site. As of this announcement, the first five chapters are available; the other chapters will follow soon
For full details about what is new or changed in this release, see the version documentation for Unicode 5.2.
2009-10-06
Last Call of Guidelines for Web Content Transformation Proxies published
The Mobile Web Best Practices Working Group published a Last Call Working Draft of Guidelines for Web Content Transformation Proxies. The document provides guidance to implementers of Content Transformation proxies as to whether and how to transform Web content.
The document has already been published as a Last Call a year ago under the title "Content Transformation Guidelines", and has been updated based on feedback from reviewers. The Working Group invites the mobile developer community to review the draft once more and send feedback by 6 November 2009, sending comments to the public-bpwg-comments@w3.org mailing-list (archive).
Last Call of Mobile Web Application Best Practices published
The Mobile Web Best Practices Working Group published a Last Call Working Draft of Mobile Web Application Best Practices. This document specifies Best Practices for the development and delivery of Web applications on mobile devices. The recommendations expand upon statements made in the Mobile Web Best Practices 1.0, especially concerning statements that relate to the exploitation of device capabilities and awareness of the delivery context.
The Working Group invites the mobile developer community to review the draft and send feedback by 6 November 2009, sending comments to the public-bpwg-comments@w3.org mailing-list (archive).
2009-10-05
Minutes of September 28 teleconference published
The MW4D IG held its 26th teleconference on September 28 2009.
The approved minutes are available at http://www.w3.org/2009/09/28-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
Mobile Web Online Training Course Starts Next Week
As we noted recently it's uncertain whether it will be possible to run the successful online training course An Introduction to W3C Mobile Web Best Practices next year. We've received a great deal of positive feedback from previous students so if you want to make sure you don't miss the opportunity of taking this course with W3C, sign up today!
The course begins on Monday 12th October and will run through to Friday 11th December, during which time you will:>
- learn about the specific promises and challenges of the mobile platform;
- learn how to use W3C's Mobile Web Best Practices to design mobile-friendly Web content and to adapt existing content for mobile;
- discover the relevant W3C resources for mobile Web design.
You work at times to suit you with no specific time when you need to be online so you can take the course no matter what time zone you're in. The sign-up system uses PayPal which takes care of most world currencies without any difficulty.
For more details of the course content and who will benefit most from it, please see the dedicated page.
2009-10-02
RIF is a W3C Candidate Recommendation
Three of the drafts define XML formats with formal semantics for storing and transmitting rules:
- The RIF Production Rule Dialect (PRD) is designed for the kinds of rules used in modern Business Rule Management systems.
- The RIF Basic Logic Dialect (BLD) is a foundation for Logic Programming, classical logic, and related formalisms.
- The RIF Core Dialect is the common subset of PRD and BLD, useful when having a ubiquitous platform is paramount.
The other drafts:
- RIF Datatypes and Builtins (DTB) specifies the datatypes and standard operations (modeled on XPath Functions) available in all RIF dialects
- RIF RDF and OWL Compatibility specifies how RIF works with RDF, RDFS, OWL 1, and OWL 2.
- RIF Framework for Logic Dialects (FLD) provides a mechanism for specifying extended dialects, beyond BLD, when more expressive power is required.
The group has also published a new version of RIF Test Cases, and three new First Public Working Drafts: RIF Overview, RIF Combination with XML data, and OWL 2 RL in RIF. The Working Group asks all developers to send implementation reports, and other comments, to public-rif-comments@w3.org by 29 October 2009.
2009-10-01
New Working Group Note: Requirements for String Identity Matching and String Indexing
On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note.
This document is being published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication.
The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing.
Editor: Martin Dürst. [search keys: tr-charreq]
Minutes and Resolutions 2009-09-30
- Resolved: Add Tab's gradient syntax proposal to CSS Image Values Level 3. (Also: Tab will add SVG equivalents for all the examples.)
- Resolved: Drop
box-shadowfrom CSS Backgrounds and Borders Level 3: work onbox-shadowoutside the module for the time being, possibly re-merge with draft later. Rationale: drop-shadows seem to need a lot more discussion, but the rest of the draft is ready to move on. - Resolved:
border-imageresizes to fit small boxes the same way asborder-radius(proportional in both dimensions) - Discussed Doug Schepers' message about extensions to DOM mouse events and whether they belong in the CSSOM View Module or in DOM3 Events
Search
Categories
Mobile Web Test Suites Working Group blog
- Announcements (11)
- Opinions (1)
- Testing tools (2)
- Web Compatibility Test (7)
- Widgets testing (3)
Archives
- September 2011 (7)
- August 2011 (23)
- July 2011 (17)
- June 2011 (13)
- May 2011 (18)
- April 2011 (14)
- March 2011 (24)
- February 2011 (15)
- January 2011 (11)
- December 2010 (12)
- November 2010 (19)
- October 2010 (18)
- More...
Misc
XML Feeds
What is RSS?
Who's Online?
- Guest Users: 15
