W3C starts two new technical committees

| by Mark Little Follow 15 Followers on Feb 28, 2007. Estimated reading time: 2 minutes |
The W3C has recently announced the formation of a new working group on internationalization (I18N). As their charter says, the aim of the group is:
to enable universal access to the World Wide Web by proposing and coordinating the adoption by the W3C of techniques, conventions, technologies, and designs that enable and enhance the use of W3C technology and the Web worldwide, with and between the various different languages, scripts, regions, and cultures.
It appears as though the group isn't going to define any new technologies for this effort, but rather will work with other efforts in W3C to ensure that they consider internationalization from an early stage. This is good news because the Web is a global resource and hence the technologies behind it should also be likewise global in nature. We can only hope that the work of this group is able to influence the various Web Services working groups within the W3C umbrella and is picked up by OASIS (where the majority of WS-* work is done), because internationalization is sorely lacking in this area. Although XML is the lingua franca of Web Services, it would be nice if various faults, policies (maybe even the specifications themselves) were suitably internationalized.

Another W3C working group also got started recently, with the acronym POWDER, standing for Protocol for Web Description Resources. This group is to specify a protocol for publishing descriptions of Web resources using RDF, such that the structured meta-data can be authenticated and applied to groups of Web resources. Furthermore, the descriptions of resources should be retrievable independently of the resources themselves.

The working group's efforts will be based on previous work in the incubator space and will try to resolve a number of unanswered questions posed by that effort. These include:

... how a description for a resource applies (or not) to elements included within that resource (for example, an image in an HTML page), the detail of how to link resources to descriptions, how to resolve any conflicts in the description's data, and several relating to the mechanism for grouping resources ("label scope"). This last area is a vital aspect of the POWDER model but has wider applicability, for example in the Evaluation and Report Language [EARL], P3P's Policy Reference File [P3P] and in the functionality offered by robots.txt.

RDF, OWL and the Semantic Web in general have been heavily pushed by the W3C over the past few years, but have failed to ignite the vendor space, often seen to be sidelined by the arrival of Web Services. Over recent years we've seen attempts by both sides in the debate to embrace the other, so it will be interesting to see whether or not POWDER remains purely in the domain of Semantic Web or has applicability to Web Services.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

RDF by Dan Diephouse

My limited exposure to RDF has kept me away from it. I like the idea, but the implementation seems bad IMHO. It was a bit too abstracted from reality and overly complex. I also think it was a big mistake not to support QNames instead of URIs in resources.

Re: RDF by Mark Little

A lot of the friction that has existed between Web Services and Semantic Web people has to do with when there's overlap in the problem domain and the different approaches that are taken. Both sides have often suffered from NIH syndrome and I believe there's a lot each side can learn from the other.

Re: RDF by Tomek Górski

Thanks for another very interesting article. Keep up the good work. Regards
Pozycjonowanie Tom

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

3 Discuss