W3C

Web Architecture

Web Architecture focuses on the foundation technologies and principles which sustain the Web, including URIs and HTTP.

Architecture Principles Header link

Web Architecture principles help to design technologies by providing guidance and articulating the issues around some specific choices.

Identifiers Header link

We share things by their names. URL, URI, IRI is the way to name things on the Web and manipulate them. Some additional addressing needs in the Web Services stack motivated some additional layers.

Protocols Header link

Protocols are the vehicle for exchanging our ideas. HTTP is the core protocol of the Web. W3C is also working on XML Protocols and SOAP in relation to Web Services.

Meta Formats Header link

XML, the Extensible Markup Language, is used to build new formats at low cost (due to widely available tools to manipulate content in those new formats). RDF and OWL allow people to define vocabularies (“ontologies”) of terms as part of the Semantic Web.

Protocol and Meta Format Considerations Header link

Documents on the Web are loosely joined pieces by identifiers. It creates a maze of rich interactions between protocols and formats.

Internationalization Header link

W3C has worked with the community on the internationalization of identifiers (IRIs) and a general character model for the Web.

News Atom

This documentbuilds upon on the Character Model for the World Wide Web 1.0: Fundamentals to provide authors of specifications, software developers, and content developers a common reference on string matching on the World Wide Web and thereby increase interoperability. String matching is the process by which a specification or implementation defines whether two string values are the same or different from one another.

The main target audience of this specification is W3C specification developers. This specification and parts of it can be referenced from other W3C specifications and it defines conformance criteria for W3C specifications, as well as other specifications.

This version of this document represents a significant change from its previous edition. Much of the content is changed and the recommendations are significantly altered. This fact is reflected in a change to the name of the document from “Character Model: Normalization” to “Character Model for the World Wide Web: String Matching and Searching”.

The TAG will be holding a developer meetup along side of our next face-to-face meeting in Cambridge, Mass. The event will be in the evening of the 22nd of July, will be hosted by Akamai and organized by the BostonJS meetup group. Thanks to both Akamai and BostonJS for helping us out!

As with our previous TAG developer meet-ups, this will be a pretty simple format. We’ll get the TAG members up on stage for a panel discussion about some of the topics we’re covering. We’re going to let you know what we’re working on, answer questions and hopefully engage in some spirited discussion. The event is open to anyone interested in web architecture, web development, web standards and the future of web tech. It’s free to attend and you do not have to already be a member of BostonJS to attend (though you will have to join that meetup group if you want to register ). The event is also listed  on lanyrd (though you must register on the BostonJS meetup group to attend).

Version 7.0 of the Unicode Standardis now available, adding 2,834 new characters. This latest version adds the new currency symbols for the Russian ruble and Azerbaijani manat, approximately 250 emoji (pictographic symbols), many other symbols, and 23 new lesser-used and historic scripts, as well as character additions to many existing scripts. These additions extend support for written languages of North America, China, India, other Asian countries, and Africa. See the link above for full details.

Most of the new emoji characters derive from characters in long-standing and widespread use in Wingdings and Webdings fonts.

Major enhancements were made to the Indic script properties. New property values were added to enable a more algorithmic approach to rendering Indic scripts. These include properties for joining behavior, new classes for numbers, and a further division of the syllabic categories of viramas and rephas. With these enhancements, the default rendering for newly added Indic scripts can be significantly improved.

Unicode character properties were extended to the new characters. The old characters have enhancements to Script and Alphabetic properties, and casing and line-breaking behavior. There were also nearly 3,000 new Cantonese pronunciation entries, as well as new or clarified stability policies for promoting interoperable implementations.

Two other important Unicode specifications are maintained in synchrony with the Unicode Standard, and have updates for Version 7.0. These will be released at the same time:

UTS #10, Unicode Collation Algorithm— the standard for sorting Unicode text
UTS #46, Unicode IDNA Compatibility Processing— for processing of non-ASCII URLs (IDNs)

A Last Call Working Draft of Encodinghas been published.

While encodings have been defined to some extent, implementations have not always implemented them in the same way, have not always used the same labels, and often differ in dealing with undefined and former proprietary areas of encodings. This specification attempts to fill those gaps so that new implementations do not have to reverse engineer encoding implementations of the market leaders and existing implementations can converge.

The body of this spec is an exact copy of the WHATWG version as of the date of its publication, intended to provide a stable reference for other specifications. We are hoping for people to review the specification and send comments about any technical areas that need attention (see the Status section for details).

Please send comments by 1 July 2014.

The battle for web security and privacy is fought at many levels. Sometimes common practice in web application design can lead to data leakage with untended consequences for users. A good example of this came up recently where confidential files shared through common web-based document sharing services were being exposed unintentionaly to third parties because the private URLs used to share them had been unintentionally leaked.

URLs that allow a user to access an otherwise privileged resource or information are called  Capability URLs, and while they can be powerful, they can also cause potential problems when used improperly.

TAG member Jeni Tennison has been working on a draft defining the space of capability URLs and outlining some good practices for usage. We think this document should be useful for web builders who are thinking about incorporating this pattern into their applications. We think it’s pretty good, but we need your feedback before we finalize it and release it as a TAG finding.

The draft may be found here: http://www.w3.org/TR/capability-urls/ and if you have feedback you are encouraged to raise an issue on github or e-mail us on the TAG public mailing list. Thanks!

The Unicode Consortium is pleased to announce the release of version 2014-05-16 of the Unicode Ideographic Variation Database (IVD). This release registers the new Moji_Joho collection, along with the first 10,710 sequences in that collection, 9,685 of which are shared by the registered Hanyo-Denshi collection. Details can be found at http://www.unicode.org/ivd/.

The slides from the MultilingualWeb workshop (including several posters) and the LIDER roadmapping workshopare now available for download. Additional material (videos of the presentations, a workshop report and more) will follow in the next weeks – stay tuned.

On April 4 th, with the much-appreciated help and support of Adobe Systems, the TAG organized an event in San Francisco called the Extensible Web Summit. As I wrote before the event, the intention was to bring together web developers and web platform developers from the local area to discuss upcoming, in-development web platform technologies and standards both to throw a spotlight on some of the topics we think are key and to guide the TAG’s thinking. Judging from the feedback we’ve received, I we achieved these goals and more.

There were quite a few positive views shared on Twitter, including:

…and the summit has inspired a few blog posts, from Alan Sterns , Brian Kardell  and Simon St. Laurent.

The final schedule of sessions and links to the unfiltered notes from these sessions can be found on the Lanyrd pagefor the event. Thanks again to everyone who came along! Based on the feedback we received, I think it’s likely we’ll be running events in the future in the same format. Watch this space and follow @w3ctagon Twitter to keep up to date.

See the program.The keynote speaker will be Alolita Sharma, Director of Language Engineering from the Wikimedia Foundation. She is followed by a strong line up in sessions entitled Developers, Creators, Localizers, Machines, and Users, including speakers from Microsoft, Wikimedia Foundation, the UN FAO, W3C, Yandex, SDL, Lionbridge, Asia Pacific TLD, Verisign, DFKI, and many more. On the afternoon of the second day we will hold Open Space breakout discussions. Abstracts and details about an additional poster session will be provided shortly.

The program will also feature an LD4LT event on May 8-9, focusing on text analytics and the usefulness of Wikipedia and Dbpedia for multiilngual text and content analytics, and on language resources and aspects of converting selected types of language resources into RDF.

Participation in both events is free. See the Call for Participation for details about how to register for the MultilingualWeb workshop. The LD4LT event requires a separate registrationand you have the opportunity to submit position statements about language resources and RDF.

If you haven’t registered yet, note that space is limited, so please be sure to register soon to ensure that you get a place.

The MultilingualWeb workshops, funded by the European Commission and coordinated by the W3C, look at best practices and standards related to all aspects of creating, localizing and deploying the multilingual Web. The workshops are successful because they attract a wide range of participants, from fields such as localization, language technology, browser development, content authoring and tool development, etc., to create a holistic view of the interoperability needs of the multilingual Web.

We look forward to seeing you in Madrid!

We’re running an event on Friday the 4 thof April in San Francisco and you’re invited.

For the past year, along-side our regular face-to-face meetings, the TAG has been holding evening developer meet-ups under the moniker “Meet the TAG.” The radical idea has been to take advantage of the fact that our meetings are happening in cities with large concentrations of Web developers to connect with these developer communities in a meaningful and useful way. The hopeful outcome is to both keep developers informed about what we’re doing, presumably on their behalf, with their platform, and to drive some feedback back into the TAG to help guide our thinking and our work. The results have generally been good, generating useful  criticism and feedbackwhich we’ve tried to take on board, and making the TAG less of an echo chamber. In the mean time we’ve met lots of developers who take a keen interest in web architecture and the future of the web platform.

For our next face-to-face meeting in San Francisco, we’re planning to expand this idea to a full-fledged one-day event, bringing in web developers and web platformdevelopers, people who are deeply invested in the web platform but may not be participating directly in standards. We’re calling this event the Extensible Web Summit.

As Twitter denizen Daniel Buchner put it:

@briankardell  @wycats  @w3ctag are you telling me we’re going to try developing API “products” using direct “customer” feedback? Mind = blown

— Daniel Buchner (@csuwildcat)  December 9, 2013

The web is 25 years old. What do we want this platform to look like 25 years from now? This event will bring together web platform developers and practitioners from different communities and backgrounds to focus on the future of the web architecture and platform. With the exception of some curated lightning talks at the beginning of the day to set the scene, the event will be run as an unconference, with the agenda self-organized by the participants. We’d like to thank Adobe Systems for stepping forward as our host for this event.

Who should attend? We would ideally like to pack this event with platform developers, framework developers and web developers with an interest in helping to drive the future of the web platform. If you read and liked what you saw in the  Extensible Web Manifesto  and you’d like to learn more and influence the direction of this thinking, then we’d love to have you along. Likewise if you are interested in other web technologies such as real time communication, platform & device APIs, security, permissions, manifests & packaging, offline usage, JavaScript promises & streams, push notifications and touch. The event is free to attend, but is filling up fast. If this sounds like your cup of tea, visit our Lanyrd pageand grab a ticket.