W3C

Web of Services

Web of Services refers to message-based design frequently found on the Web and in enterprise software. The Web of Services is based on technologies such as HTTP, XML, SOAP, WSDL, SPARQL, and others.

Data Header link

Web services give access to data in a distributed environment. For a better interaction, these data are formally defined with vocabularies and grammars.

Protocols Header link

Depending on the application constraints for exchanging data across the Web, developers can choose among a series of protocols such as HTTP, SOAP and Web Services.

Service Description Header link

In specific environments, Web services description defines formally machine readable interfaces for accessing the data. WSDL, SML, and choreography and policy specifications enable descriptions, and Web Services and Semantic Web connect through semantic annotations.

Security Header link

Transferring data from one domain to another domain or between applications needs sometimes a secure transaction and well defined document authentication. XML Encryption and XML Signature are key pieces of the XML security stack.

Payment Header link

At one time, W3C examined core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area. W3C is not currently active in this area.

Internationalization Header link

Internationalization of Web services concerns service descriptions, communicating language and locale, and internationization of human-readable messages exchanged by services.

News Atom

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]

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]

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.

The IETF has published RFC 5646, an update of Tags for Identifying Languages. This specification obsoletes former RFCs 4646, 3066 and 1766.

RFC 5646 makes it possible to use over 7,000 three-letter ISO 639-3 language codes, in addition to the 2 letter codes that have been in use for some time. It also introduces 220 'extended language' subtags, mainly for backwards compatibility.

It continues to be best to refer to this specification as BCP47. This is a non-changing name and web address that points to the latest relevant RFCs.

The Internationalization Working Group at the W3C is working on an article to help users choose language tags, given the various types of subtag that are now available, and the sheer number of subtags.

You can look up language and other subtags in the IANA Language Subtag Registry.

(Richard Ishida has provided an

unofficial tool

for searching the registry that also provides advice for choosing subtags, and allows you to partially validate a hyphen-separated language tag.)

FAQ-based article: If I'm unable to use markup to correctly order bidirectional text, what can I do?

By Richard Ishida, W3C. [search key:  qa-bidi-unicode-controls]

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-bidi-unicode-controls]

The SOAP-JMS Binding Working Group published SOAP over Java Message Service 1.0 as a Candidate Recommendation. The review period ends 31 August 2009

17 March 2009

from Web Services @ W3C

The Web Services Resource Access Working Group published five Working Drafts: WS-Transfer, WS-Resource Transfer, WS-Enumeration, WS-Metadata Exchange and WS-Eventing.

The SOAP-JMS Binding Working Group published SOAP over Java Message Service 1.0 as a Last Call Working Draft. The review period ends 13 January 2009