Use the submission form to add a new talk (member only link)
Last year, we introduced server-side XForms as the most promising way of making XForms a short-term reality on the web.
In this year’s presentation, we discuss how this promise has materialized with hybrid Ajax-based open source implementations, and we demonstrate the most exciting capabilities of XForms running on today’s deployed web browsers.
We not only show how XForms fulfils its initial promise of becoming the next generation web forms, but also how it serves as a general-purpose dynamic user interface technology.
Finally, we show that hybrid XForms implementations effectively offer an abstraction layer over Ajax technologies, thereby greatly simplifying the implementation of common Ajax use-cases and giving XForms a place of choice in the “Web 2.0” ecosystem.
Il World Wide Web, l’ invenzione che più ha rivoluzionato la nostra vita negli ultimi anni, nasce dall’ intuizione di Tim Berners-Lee, che peraltro ha sempre affermato che il Web è il frutto di un lavoro collettivo, e da un’ incredibile serie di sviluppi di ricerca e tecnologici. I principi ispiratori della proposta iniziale sono ancora vivi e attuali, e il Semantic Web è la realizzazione di un sogno che appariva impossibile.
Nella nascita e successiva travolgente diffusione del Web hanno giocato un ruolo fondamentale un’ impostazione tecnica e umana che ha privilegiato e valorizzato il lavoro collettivo e il rispetto reciproco, e una forte attenzione ai valori umani.
As one of the important provider of IST Standards, in the area of Web technologies (XML, http, HTML, CSS, WAI, etc), the international World Wide Web Consortium (W3C) is well positionned to give its opinion on the matter of Open Standards definition.
W3C follows a process that promotes the development of high-quality standards. This process has evolved over a period of ten years, from a very rough consensus building approach of writing specifications, to a formal set of obligations that promote fairness, responsiveness, and progress: all facets of the W3C mission.
Using the W3C process as a model, we present the set of requirements that a provider of technical specification must follow to qualify for the adjective Open Standard.
The Ubiquitous Web aims to make it much easier to create distributed Web applications that work across a wide range of devices. It combines high level declarative application models and Web based approaches to accessing local and remote services and binding them as part of application sessions.
Considering that HTML is the world's most popular document format, it is seriously ill-fitted for information representation purposes.
After an enormous effort in the 90's to undo the damage caused by mixing content and presentation, it seems like that message is now coming through.
But there is still a long road to navigate. The tools you use for content delivery can greatly affect what you can achieve, and the amount of work you have to put in to achieve it.
Do we really want to re-author a site for each type of device that is likely to use it? What are the best ways to meet the challenges of multi-lingual environments and accessibility?
Work is ongoing at the World Wide Web Consortium W3C on producing markup languages that meet the needs of modern web content, and this talk describes the approach used, and in particular how XHTML2 and XForms meet the challenges of structured content, single authoring, accessibility, and device independence.
If you are a designer, developer or author working on a website that may be translated or adapted for users in other countries or languages, you need to ensure that you don't build in substantial barriers to localization. If you think that the translation vendor or localization team can take care of things for you when the time comes, you really need to hear this talk. We will use examples to examine some of the things that must be designed into the site, rather than treated as an afterthought, if it is to be successfully deployed in more than one language or country.
The Internationalization Tag Set (ITS) work at the W3C, led by Yves Savourel, defines a standard to support better internationalisation and localisation of schemas and XML documents (both existing and new ones). The standard proposes a set of data categories, for which it then defines implementations as a set of elements and attributes. It also provides examples of how ITS can be used with popular existing markup schemes such as DocBook and DITA, and in three schema languages, XML DTDs, XML Schema, and RELAX NG.
The first version of the standard is nearing completion. It addresses how to identify translatable vs. non-translatable content, localisation notes, terminology references, directionality of text, language markup, inline elements, and ruby annotation.
The aim is to ensure that XML formats support features needed for international use and for efficient localisation. It should also make the job of vendors easier by standardising the format and processing expectations of localisation-related markup items, and allowing translation tools to more effectively identify how content should be handled.
The talk will use examples to acquaint you better with ITS and its relevance to the localisation community.
The demand for automated or assisted Web service discovery and invocation prompted the development of the Web Services Policy framework (WS-Policy), a general purpose framework for expressing requirements, capabilities, and general characteristics for invoking a particular Web service, such as security or reliability requirements. The WS-Policy language is limited to AND and OR and functions named by QNames. Simple boolean logic allows one to discover equivalent policies and to test whether a particular connection conforms to a given policy.
While any language with AND, OR and named functions subsumes WS-Policy's expressiveness, the most interesting are those that are, intuitive, sound, and extensible. A variety of current schema (W3C XML Schema and OWL) and query languages (XQuery and SPARQL) meet these requirements to varying degrees. This paper will demonstrate and contrast expressions of Web service policies in these languages.
SPARQL and XQuery are query languages for two data different models. The current definition of WS-Policy does not presume any particular expression of service or library capabilities into any data model. All that's required is that some mechanism be able to recognize a policy and verify compliance of the available software modules. For example, this could be hard coded into an agent. Query languages like SPARQL and XQuery are designed to intuitively expression boolean logic. Using, for instance, SPARQL to express policies implies a mapping of agent capabilities into an RDF graph. Likewise, expressing agent capabilities in XML allows one to query them with XQuery.
We will describe the ways in which these languages all exceed this simple AND, OR, named function expressivity and discuss the applicability of this extra expressivity to describing Web service policies, or Web services in general. Importing this expertise from other domains informs us about potential policy expressivity. We will identify additional use cases met by adopting this additional expressivity.
233 entries. (Use the separate submission page to add a new talk; member only link.)
Please send feedback on this page to the W3C Communications Team (w3t-pr@w3.org).Copyright © 1994-2009 W3C ® (MIT , ERCIM , Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
