Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 123 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 129 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 136 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 170 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 200 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 206 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 231 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 242 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 254 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 293 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 351 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 352 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 353 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 354 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 355 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 571 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 197 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 202 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_connect_db.inc.php on line 27 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/sessions/_session.class.php on line 222 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/generic/_genericelement.class.php on line 112 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 428 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 437 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/collections/_category.funcs.php on line 390 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 549 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 563 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist.class.php on line 602 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_item.class.php on line 2952 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 306 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 120 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 796 Deprecated: Function ereg() is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 413 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/skins/_skin.funcs.php on line 71
Thanks to the Sorin Velescu, the following articles have been translated into Romanian.
Data si Ora (Dates and Time)
Formate pentru data (Date formats)
Capacitati de afisare (Display capabilities)
[search keys: article-o-time qa-date-format qa-display-capabilities]
We have just published a Working Group Note called A Method for Writing Testable Conformance Requirements. This document presents a method for writing, marking-up, and analyzing conformance requirements in technical specifications that can help other Working Groups develop better specifications more quickly.
We derived this methodology from our collaboration with the Web Applications Working Group on the development of the test suite for the Widgets Packaging & Configuration specification.
Feedback on the document is more than welcome!
The W3C SPARQL Working Group has published a First Public Working Draft of SPARQL 1.1 Property Paths, which defines a more succinct way to write parts of basic graph patterns and also extend matching of triple pattern to arbitrary length paths. The group also published six updates, namely:
Thanks to the Spanish Translation Team, Spanish Translation US, the following articles have been translated into Spanish.
Consejos rápidos sobre internacionalización para la Web (Internationalization Quick Tips for the Web)
Introducción a las codificaciones y a los sets de caracteres (Introducing Character Sets and Encodings)
[search keys: gs-characters article-quicktips
Thanks to Dénes Kohn, Metaphraser Translation Company, the following articles have been translated into Hungarian.
Karakterkódolás ellenőrzése a validatorral (Checking the character encoding using the validator)
HTTP Fejlécek Ellenőrzése (Checking HTTP Headers)
Karakterkészletre vonatkozó beállítás a .htaccess fájlban (Setting charset information in .htaccess)
[search keys: qa-validator-charset-check qa-headers-charset qa-htaccess-charset]
The CSSWG has just published a Last Call Working Draft of the CSS Styling Attributes Leve 1 specification. Nothing new and exciting—style attributes have been here since the beginning—but now there's a CSS spec that actually defines their syntax and interpretation. Please send any comments to www-style with "[css-style-attr] …summary of comment…" as the subject line. The deadline for comments is 9 February 2010.
W3C is organizing a Workshop on the Next Steps for RDF around June 2010; we will announce the exact dates and location as soon as possible.
Since its publication in 2004, the Resource Description Framework (RDF) has become the core architectural block of the Semantic Web. The standard is now widely deployed in terms of tools and applications. Due to this wide deployment, additional R&D activities, and the publication of newer standards (e.g., SPARQL, OWL, POWDER, and SKOS), a number of issues regarding RDF have come to the fore. Workshop articipants will discuss these issues and help determine whether it is time for a new version of RDF. W3C Membership is not required to participate in the Workshop, but each participant must be associated with an accepted position paper. The deadline for position papers is 29 March 2010; see the Call for Participation for more information.
Updates (including the exact date and location of the Workshop) will be added to the Call for Participation and will be announced on the Semantic Web Activity News Blog.
The HCLS IG had a good year in 2009, with lots of interaction, demonstration, and outreach. HCLS was involved in: C-SHALS Tutorial, Shared Names, Bio-IT World (in Boston and Hannover), Concept Web Alliance (CWA), PRISM Forum SIG, AMIA conferences, 7th Annual Pharma Technology IT Summit, the Data Integration for the Life Sciences (DILS) Workshop, and SWAT4LS.
We held two Face2Face meetings (Boston,MA and Santa Clara,CA), organized the Workshop on Scientific Discourse at ISWC2009, and helped organize the Semantic Web Applications and Tools for the Life Sciences (SWAT4LS) in Amsterdam - all well-received. HCLS produced some deliverables such as a Translational Medicine Ontology, articles in journals and proceedings, lots of Linked Open Drug Data, three W3C Interest Group notes, an approach to query federation, and presented a new version of the Clinical Observations Interoperability demo. We also helped initiate Shared Names, participated in the development of the Concept Web Alliance demo, and won the Triplification Challenge of 2009. In 2009, several of our members have joined together to write grant proposals in both Europe and the U.S. which could provide more support for some HCLS activities. BTW, another way to support those activities is to join us (see top of page for instructions)!
A development that I am excited about is the collaborative effort involving HCLS and CWA and the Swiss Institute of Bioinformatics (SIB) to create a SPARQL endpoint for Uniprot. Such an endpoint could make it possible to perform essential bioinformatics information retrieval without ever leaving the comfort of your SPARQL query interface.
I'm writing to you from Stanford, California where I am visiting the Musen Lab, home of the National Center for Biomedical Computing (NCBO), and the creators of BioPortal and Protégé. NCBO just put in for a renewal grant so keep your fingers crossed! In HCLS, we hope to see continued support for the very valuable knowledge resources that have been made available to biomedical researchers by NCBO. HCLS is looking at how to incorporate BioPortal services into our demonstrations.
There is a lot of buzz these around augmented reality in general, and mobile specifically (just search for "augmented reality" on twitter - there is a new tweet every minute or so).
How can these new interaction paradigms be integrated into the platform of the Web and evolve to be as open and inclusive as the Web?
To understand this and related questions, Dan Applequist of Vodafone, Rittwik Jana of AT&T Labs Research, Christine Perey of PEREY Research & Consulting and myself are co-chairing the WWW2010 workshop "MobEA-2010: Augmented Reality and Virtual Interactivity".
The Call for papers includes a long list of topics - of particular interest to the mobile community could be:
If you have worked on these or related topics, and in particular if you have demos:
Paper submission is open until February 21 - check out the Call for papers for details.
The MW4D IG held its 31st teleconference on December 21 2009.
The approved minutes are available at http://www.w3.org/2009/12/21-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
Thanks to the Sorin Velescu, the following articles have been translated into Romanian.
Localizare vs. Internationalizare (Localization vs. Internationalization)
Site-uri Web monolinguale vs. multilinguale (Monolingual vs. multilingual Web sites)
Site-uri internationale si multilinguale (International & multilingual web sites)
[search keys: qa-i18n qa-mono-multilingual qa-international-multilingual]
SVG is growing in popularity by leaps and bounds. The SVG Working Group wants to make sure that SVG expands to meet the needs of the designer and developer community.
To that end, we have put a lot of effort into opening up our process: we've changed from a member-only group to a public group; we hold all our technical discussions in public; we post all our meeting agendas and minutes to the read-write www-svg list, and take agenda requests from the public; we started an open SVG Interest Group, which everyone is welcome to join; we've reached out to the open-source community to invite participation by an Inkscape contributor (more on that later); and we're actively seeking out the opinions of community leaders and people from the trenches in a variety of ways.
But sometimes too much is not enough. It's hard for busy people to sift through the technical details and standards process to find the SVG gold dust that helps them in their everyday jobs. Thus, this blog. We will try to keep you updated on the most relevant details of SVG implementations, publication of specifications, links to cool uses of SVG, and other news in the SVG world.
Readers who want to play an active role in the development of the SVG language are invited to post to the www-svg mailing list, as usual, but we hope this blog (and its Atom newsfeed) will help you stay aware of what you need to know about SVG's progress.
A new public wiki site has been set up at W3C, nicknamed “Semantic Web Standards Wiki” or SWSWiki. It is not the goal of this wiki to supersede other community wikis like Semanticweb.org or OWLED Wiki; instead it is to provide a “first stop” for more information on Semantic Web technologies, in particular on Semantic Web Standards published by the W3C. Communities around such standards are also welcome to use the Wiki for their purpose; as an example, and thanks to Antoine Isaac, the SKOS community has already begun creating its own specific pages. Essentially, the role of this Wiki is to be an alternative (and, at some point in the future, maybe a replacement) to the ESW Wiki at W3C, but concentrating on Semantic Web only and using Semantic Media Wiki as an underlying technology.
Some pages from the ESW wiki have already been copied to ESWWiki. For example, the old book list has been copied to SWSWiki Book page. The old ESW list of tools, as well as some related pages like the Commercial Product have also been copied; however, and in contrast to the book list, this was not simply a copy of the pages but a new structure was also created, making use of the possibilities of Semantic Media Wiki. As a result, each tool has its own, separate page (produced by a template) and different types of searches can be performed on the tool list to find the ones usable from, say, Python and relevant to OWL development. See the new tools‘ list for further details and the contributors‘ page if you also want to contribute. (No major change on the content of the tool descriptions have been made during this copy, although, in some cases, different texts referring to the same tool have been merged. Apologies if some mistakes have been made along the line.) Each tool also gained an automatic RDF description, thanks again to the possibilities offered by the Semantic Media Wiki.
This is an evolving Wiki. Evolving, meaning that new pages and new features will be added as time goes by; and Wiki, meaning that it relies on community contributions. Anybody having a W3C account (member or public) can and is welcome to contribute to the pages. General comments are also welcome (best is to send them to the Semantic Web Activity Lead, Ivan Herman, or discuss it on the SW IG).
Thanks to the Spanish Translation Team, Spanish Translation US, the following articles have been translated into Spanish.
HTML, XHTML, XML y códigos de control (HTML, XHTML, XML and Control Codes)
¿Quién utiliza Unicode? (Who uses Unicode?)
Migración a Unicode (Migrating to Unicode)
[search keys: qa-controls qa-who-uses-unicode article-unicode-migration]
Version 1.3.0 of the online W3C mobileOK Checker service is out. On top of the usual bug fixes and clarifications of messages, here are a couple of features which I hope will be useful.
Many thanks to users of the W3C mobileOK Checker who provided feedback and helped identify bugs!
Users rightly complained that the W3C mobileOK Checker only worked on content that was already available on the Web. Web authors usually start with local content and publish it once they are happy with the result. The mobileOK Checker comes after the battle here... There existed good reasons to restrict checks to published Web content as some of the mobileOK tests apply to the HTTP headers sent along with the content and thus cannot be run when the content is not available using HTTP.
Anyway, you can now check content for mobile-friendliness using file upload and direct input.

As already mentioned, some mobileOK tests only apply partially or do not apply at all when these input methods are used. For instance, the total size of the page is not accurate if stylesheets and images cannot be retrieved by the W3C mobileOK Checker. In short, the report is incomplete and the content cannot claim to be mobileOK™ as long as the remaining tests have not been enforced.
The Checker retrieves as many resources as possible and ignores those that cannot be retrieved when file upload or direct input is used. If the HTML content references a CSS stylesheet using an absolute HTTP URI, the Checker will retrieve and run tests on that stylesheet. Similarly, the base HTML element may be used to set the base HTTP URI against which the Checker will resolve relative links, as illustrated in the following example:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<base href="http://www.w3.org/Mobile/" />
<title>W3C test page</title>
</head>
<body>
<p><img src="W3C.gif" width="85" height="43" alt="W3C" /></p>
</body>
</html>
The Checker can retrieve the W3C.gif image in the above example even if the content is provided as direct input because its address can be resolved against the base element, leading to the http://www.w3.org/Mobile/W3C.gif absolute HTTP address.
Obviously, this does not work if the base element is a relative URI itself, or if the rest of the content is not available.
The W3C mobileOK Checker sometimes returns failures that do not seem to originate from the content under test. That is, the incriminated code does not reveal itself when one right clicks and selects View source on one's favorite desktop browser.
Most of the time, the reason for that apparent disconnection is that the server uses content adaptation and sends different content to the browser and to the W3C mobileOK Checker. The W3C mobileOK Checker uses specific HTTP headers to retrieve resources as if it were a mobile device. To avoid losing precious time to realize that the tests were simply run on the mobile version of the content, the report now includes the listing of the source that was received by the mobileOK Checker for reference.

W3C has published a set of URI-s to uniquely identify OWL 2 Profiles. These URI-s are needed for the upcoming SPARQL specification, but their usage can be more general and not bound to specific technologies.
The URI-s for the OWL 2 Profiles are:
http://www.w3.org/ns/owl-profile/DLhttp://www.w3.org/ns/owl-profile/ELhttp://www.w3.org/ns/owl-profile/QLhttp://www.w3.org/ns/owl-profile/RLEach of these URI-s can return, depending on content negotiations, XHTML+RDFa, RDF/XML, or Turtle content; the URI-s above with html, rdf, or ttl suffixes, respectively, can also be used to get to those versions directly.
W3C has published a set of URI-s to uniquely identify Semantic Web entailment regimes. These URI-s are needed for the upcoming SPARQL and RIF specifications, but their usage can be more general and not bound to specific technologies.
The URI-s for the various entailment regimes are:
http://www.w3.org/ns/entailment/Simplehttp://www.w3.org/ns/entailment/RDFhttp://www.w3.org/ns/entailment/RDFShttp://www.w3.org/ns/entailment/Dhttp://www.w3.org/ns/entailment/OWL-Directhttp://www.w3.org/ns/entailment/OWL-RDF-Basedhttp://www.w3.org/ns/entailment/RIFEach of these URI-s can return, depending on content negotiations, XHTML+RDFa, RDF/XML, or Turtle content; the URI-s above with html, rdf, or ttl suffixes, respectively, can also be used to get to those versions directly.