SystemDoctor/V2GProtocol_CSharp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
master
V2GProtocol_CSharp/temp/exificient/data/W3C/xhtml/www.w3.org.htm
ChiKyun Kim 747aabe224 add files
2025-09-09 13:59:12 +09:00

382 lines
47 KiB
HTML
Raw Permalink Blame History

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
<head profile="http://www.w3.org/2000/08/w3c-synd/#">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="keywords" content="W3C, World Wide Web, Web, WWW, Consortium, computer, access, accessibility, semantic, worldwide, W3, HTML, XML, standard, language, technology, link, CSS, RDF, XSL, Berners-Lee, Berners, Lee, style sheet, cascading, schema, XHTML, mobile, SVG, PNG, PICS, DOM, SMIL, MathML, markup, Amaya, Jigsaw, free, open source, software" />
<meta name="description" content="The World Wide Web Consortium (W3C) is an international consortium where Member organizations, a full-time staff, and the public work together to develop Web standards. W3C primarily pursues its mission through the creation of Web standards and guidelines designed to ensure long-term growth for the Web. Over 400 organizations are Members of the Consortium. W3C is jointly run by the MIT Computer Science and Artificial Intelligence Laboratory (MIT CSAIL) in the USA, the European Research Consortium for Informatics and Mathematics (ERCIM) headquartered in France, Keio University in Japan, and has additional Offices worldwide." />
<title>World Wide Web Consortium - Web Standards</title>
<link rel="meta" href="/Overview-about.rdf" />
<link rel="stylesheet" type="text/css" href="/StyleSheets/home.css" />
<link rel="bookmark" href="#technologies" title="Technologies |" />
<link rel="bookmark" href="#news" title="News |" />
<link rel="bookmark" href="#search" title="Search |" />
<link rel="contents" href="#contents" title="Contents |" />
<link rel="bookmark" href="#Offices" title="Offices |" />
<link rel="bookmark" href="#systems" title="Systems |" />
<link rel="bookmark" href="#donors" title="Supporters |" />
<link rel="bookmark" href="#footnotes" title="Footnotes |" />
<link rel="alternate" type="application/rss+xml" title="W3C Home Page News RSS Channel" href="http://www.w3.org/2000/08/w3c-synd/home.rss" />
<style type="text/css">
/**/
div.spot-image img {
margin-bottom: 20px;
}
/**/</style>
</head>
<body>
<h1 id="logo"><img alt="The World Wide Web Consortium (W3C)" height="48" width="315" src="/Icons/w3c_main" /></h1>
<h2 id="slogan">Leading the Web to Its Full Potential...</h2>
<div>
<map name="introLinks" id="introLinks" title="Introductory Links">
<div class="banner">
<span class="invisible"><a class="bannerLink" title="Skip introductory links and the mission statement" href="#technologies">Skip to Technologies</a> |</span> <a class="bannerLink" title="W3C Activities" accesskey="A" href="/Consortium/activities">Activities</a> | <a class="bannerLink" title="Technical Reports and Recommendations" accesskey="T" href="/TR/">Technical Reports</a> | <a class="bannerLink" title="Alphabetical Site Index" accesskey="S" href="/Consortium/siteindex">Site Index</a> | <a class="bannerLink" title="Help for new visitors" accesskey="N" href="/Consortium/new-to-w3c">New Visitors</a> | <a class="bannerLink" title="About W3C" accesskey="B" href="/Consortium/">About W3C</a> | <a class="bannerLink" title="Join W3C" accesskey="J" href="/Consortium/join">Join W3C</a> | <a class="bannerLink" title="Contact W3C" accesskey="C" href="/Consortium/contact">Contact
W3C</a> </div>
</map>
</div>
<p class="small">The World Wide Web Consortium (<acronym title="World Wide Web Consortium">W3C</acronym>) develops interoperable
technologies (specifications, guidelines, software, and tools) to lead the
Web to its full potential. W3C is a forum for information, commerce,
communication, and collective understanding. On this page, you'll find <a href="#news">W3C news</a>, links to <a href="#technologies">W3C
technologies</a> and ways to <a href="#contents">get involved</a>. New
visitors can find help in <cite><a href="/Consortium/new-to-w3c">Finding Your
Way at W3C</a></cite>. We encourage organizations to learn more <a href="/Consortium/">about W3C</a> and <a href="/Consortium/membership">about
W3C Membership</a>.</p>
<div class="navBlock">
<h2 class="spot-head">Validator Donation Program</h2>
<div class="spot">
<p class="spot-block">
<a href="/QA/Tools/Donate"><img style="border:none" class="newsImage" alt="I Love Validator" src="/QA/Tools/I_heart_validator.png" /></a>
<a href="/QA/Tools/Donate">Make a donation</a> or become a
<a href="/QA/Tools/Donate#donate_sponsors">sponsor</a>
of the <a href="http://validator.w3.org/">W3C Validator</a>.</p>
</div>
<h2 style="clear:left" class="spot-head">W3C Supporters</h2>
<div class="spot">
<p class="spot-block">Help W3C by making a donation through the <a href="/Consortium/sup">W3C Supporters Program</a>.</p>
</div>
<h2 class="spot-head">Employment</h2>
<div class="spot">
<p class="spot-block">
<strong>W3C is seeking a
<a href="/Consortium/Recruitment/">Managing Director</a></strong>.</p>
<p class="spot-block">
Current <a href="/Consortium/Recruitment/Fellows#openings">W3C Fellows Program
openings</a> are <a href="/2007/01/comm-fellow1">Business and Technology
Communications Specialist</a>; <a href="/2007/01/SysteamFellowsPosition">Software Engineer</a>.</p>
</div>
<h2 class="navhead"><a name="technologies" id="technologies">W3C A to
Z</a></h2>
<ul>
<li class="invisible"><a class="navlink" title="Skip W3C A-Z" href="#news">Skip to News</a></li>
<li><a href="/WAI/" class="navlink">Accessibility</a></li>
<li><a href="/Amaya/" class="navlink">Amaya</a></li>
<li><a href="/Mobile/CCPP/" class="navlink"><abbr title="Composite Capability/Preference Profiles">CC/PP</abbr></a></li>
<li><a href="/2004/CDF/" class="navlink">Compound Document Formats
(CDF)</a></li>
<li><a href="/Style/CSS/" class="navlink"><abbr title="Cascading Style Sheets">CSS</abbr></a></li>
<li><a href="http://jigsaw.w3.org/css-validator/" class="navlink"><abbr title="Cascading Style Sheets">CSS</abbr> Validator</a></li>
<li><a href="/2002/ws/databinding/" class="navlink">Databinding</a></li>
<li><a href="/DOM/" class="navlink"><acronym title="Document Object Model">DOM</acronym></a></li>
<li><a href="/XML/EXI" class="navlink">Efficient XML Interchange</a></li>
<li><a href="/2008/geolocation/" class="navlink">Geolocation</a></li>
<li><a href="/2007/eGov/" class="navlink">eGovernment</a></li>
<li><a href="/2001/sw/grddl-wg/" class="navlink"><acronym title="Gleaning Resource Descriptions from Dialects of Languages">GRDDL</acronym></a></li>
<li><a href="/2001/sw/hcls/" class="navlink">Health Care and Life
Sciences</a></li>
<li><a href="/html/" class="navlink"><abbr title="HyperText Markup Language">HTML</abbr></a></li>
<li><a href="/People/Raggett/tidy/" class="navlink"><abbr title="HyperText Markup Language">HTML</abbr> Tidy</a></li>
<li><a href="http://validator.w3.org/" class="navlink"><abbr title="HyperText Markup Language">HTML</abbr> Validator</a></li>
<li><a href="/Protocols/" class="navlink"><abbr title="Hypertext Transfer Protocol">HTTP</abbr></a></li>
<li><a href="/2005/Incubator/" class="navlink">Incubator</a></li>
<li><a href="/2002/mmi/ink" class="navlink">InkML</a></li>
<li><a href="/International/" class="navlink">Internationalization</a></li>
<li><a href="/Jigsaw/" class="navlink">Jigsaw</a></li>
<li><a href="/Library/" class="navlink">Libwww</a></li>
<li><a href="/Math/" class="navlink">MathML</a></li>
<li><a href="/2008/WebVideo/Annotations/">Media Annotations</a></li>
<li><a href="/2008/WebVideo/Fragments/">Media Fragments</a></li>
<li><a href="/Mobile/" class="navlink">Mobile Web Initiative
(W3C-MWI)</a></li>
<li><a href="/2002/mmi/" class="navlink">Multimodal Interaction</a></li>
<li><a href="/2004/OWL/" class="navlink"><acronym title="OWL Web Ontology Language">OWL</acronym></a></li>
<li><a href="/2004/pp/" class="navlink">Patent Policy</a></li>
<li><a href="/PICS/" class="navlink"><acronym title="Platform for Internet Content Selection">PICS</acronym></a></li>
<li><a href="/Graphics/PNG/" class="navlink"><acronym title="Portable Network Graphics">PNG</acronym></a></li>
<li><a href="/2007/powder/" class="navlink"><acronym title="Protocol for Web Description Resources">POWDER</acronym></a></li>
<li><a href="/P3P/" class="navlink">Privacy and <abbr title="Platform for Privacy Preferences">P3P</abbr></a></li>
<li><a href="/RDF/" class="navlink"><abbr title="Resource Description Framework">RDF</abbr></a></li>
<li><a href="/2005/rules/" class="navlink">Rules</a></li>
<li><a href="/Security/" class="navlink">Security</a></li>
<li><a href="/2001/sw/" class="navlink">Semantic Web</a></li>
<li><a href="/XML/SML" class="navlink">Service Modeling Language (<abbr title="Service Modeling Language">SML</abbr>)</a></li>
<li><a href="/AudioVideo/" class="navlink"><acronym title="Synchronized Multimedia Integration Language">SMIL</acronym></a></li>
<li><a href="/2000/xp/Group/" class="navlink"><acronym title="Soap">SOAP</acronym>/<abbr title="XML Protocol">XMLP</abbr></a></li>
<li><a href="/2002/ws/soapjms/" class="navlink"><acronym title="Soap">SOAP-JMS</acronym></a></li>
<li><a href="/2001/sw/DataAccess/" class="navlink"><acronym title="Simple Protocol and RDF Query Language">SPARQL</acronym></a></li>
<li><a href="/Style/" class="navlink">Style</a></li>
<li><a href="/Graphics/SVG/" class="navlink"><abbr title="Scalable Vector Graphics">SVG</abbr></a></li>
<li><a href="/2001/tag/" class="navlink"><abbr title="Technical Architecture Group">TAG</abbr></a></li>
<li><a href="/AudioVideo/TT/" class="navlink">Timed Text</a></li>
<li><a href="/Addressing/" class="navlink"><abbr title="Uniform Resource Identifiers">URI/URL</abbr></a></li>
<li><a href="/QA/Tools/#validators" class="navlink">Validators</a></li>
<li><a href="/2008/WebVideo/">Video</a></li>
<li><a href="/Voice/" class="navlink">Voice</a></li>
<li><a href="/2007/uwa/" class="navlink">Ubiquitous Web
Applications</a></li>
<li><a href="/WAI/" class="navlink"><acronym title="Web Accessibility Initiative">WAI</acronym></a></li>
<li><a href="/2008/webapps/" class="navlink">Web Applications</a></li>
<li><a href="/2001/tag/" class="navlink">Web Architecture (<acronym title="Technical Architecture Group">TAG</acronym>)</a></li>
<li><a href="/Graphics/WebCGM/WG/" class="navlink"><abbr title="Web Computer Graphics Metafile">WebCGM</abbr></a></li>
<li><a href="/2002/ws/" class="navlink">Web Services</a></li>
<li><a href="/2008/webapps/wiki/Main_Page#Widgets" class="navlink">Widgets</a></li>
<li><a href="/2002/ws/addr/" class="navlink"><abbr title="Web Services">WS</abbr>-Addressing</a></li>
<li><a href="/2002/ws/chor/" class="navlink"><abbr title="Web Services Choreography Description Language">WS-CDL</abbr></a></li>
<li><a href="/2002/ws/ra/" class="navlink"><abbr title="Web Services Resource Access">WS-Resource Access</abbr></a></li>
<li><a href="/2002/ws/desc/" class="navlink"><acronym title="Web Services Description Language">WSDL</acronym></a></li>
<li><a href="/2002/ws/policy/" class="navlink"><abbr title="Web Services">WS</abbr>-Policy</a></li>
<li><a href="/MarkUp/Forms/" class="navlink"><acronym title="Next Generation Web Forms">XForms</acronym></a></li>
<li><a href="/MarkUp/" class="navlink"><abbr title="Extensible HyperText Markup Language">XHTML</abbr></a></li>
<li><a href="/MarkUp/" class="navlink"><abbr title="Extensible HyperText Markup Language">XHTML2</abbr></a></li>
<li><a href="/XML/Linking" class="navlink"><acronym title="XML Link">XLink</acronym></a></li>
<li><a href="/XML/" class="navlink"><abbr title="Extensible Markup Language">XML</abbr></a></li>
<li><a href="/TR/xmlbase/" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Base</a></li>
<li><a href="/2001/XKMS/" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Key Management</a></li>
<li><a href="/XML/Processing/" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Processing</a></li>
<li><a href="/XML/Query" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Query</a></li>
<li><a href="/XML/Schema" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Schema</a></li>
<li><a href="/2008/xmlsec/" class="navlink"><abbr title="Extensible Markup Language">XML</abbr> Signature and
Encryption</a></li>
<li><a href="/Style/XSL/" class="navlink">XPath</a></li>
<li><a href="/XML/Linking" class="navlink">XPointer</a></li>
<li><a href="/Style/XSL/" class="navlink"><acronym title="Extensible Stylesheet Language">XSL</acronym> and <acronym title="XSL Transformations">XSLT</acronym></a></li>
</ul>
<p><a href="/Consortium/siteindex" class="navlink">More topics...</a></p>
</div>
<div class="newsBlock">
<h2 class="newsHeading"><a name="news" id="news">News</a></h2>
<p class="invisible"><a title="Skip News" href="#search">Skip to
Search</a></p>
<div id="item136" class="item"><h3 class="headline">Six XML Security Documents Published</h3><p><span class="date">2009-07-31:</span> The <a href="/2008/xmlsec/">XML Security Working Group</a> published six documents related to XML signature and encryption. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. </p> <ul> <li><a href="/TR/2009/WD-xmldsig-bestpractices-20090730/">XML Signature Best Practices</a>. This Working Draft describes best practices related to improving security and mitigating attacks, yet others are for best practices in the practical use of XML Signature, such as signing XML that doesn't use namespaces, for example.</li> <li><a href="/TR/2009/WD-xmldsig-core1-20090730/">XML Signature Syntax and Processing Version 1.1</a>. This Working Draft updates the signature specification.</li> <li><a href="/TR/2009/WD-xmldsig-simplify-20090730/">XML Signature Transform Simplification: Requirements and Design</a>. This Working Draft outlines a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption.</li> <li><a href="/TR/2009/WD-xmlenc-core1-20090730/">W3C XML Encryption Syntax and Processing Version 1.1</a>. This Working Draft updates the encryption specification.</li> <li><a href="/TR/2009/WD-xmlsec-generic-hybrid-20090730/">XML Security Generic Hybrid Ciphers</a>. This First Public Working Draft augments XML Encryption Version 1.1 by defining algorithms, XML types and elements necessary to enable use of generic hybrid ciphers in XML Security applications.</li> <li><a href="/TR/2009/WD-xmlsec-algorithms-20090730/">XML Security Algorithm Cross-Reference</a>. This Group Note collects the various known URIs for encryption algorithms (at the time of its publication) and indicates which specifications define them.</li> </ul> <p>Learn more about the <a href="/Security/">Security Activity</a>.<span class="archive"> (<a title="Six XML Security Documents Published" href="/News/2009#item136" rel="details">Permalink</a>) </span></p></div>
<div id="item135" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Daniel Weitzner Named to Run US Government Internet Policy Unit</h3><p><span class="date">2009-07-30:</span> Daniel Weitzner has been named Associate Administrator for the Office of Policy Analysis and Development at the <a href="http://www.ntia.doc.gov/opadhome/staffbios.htm">US National Telecommunications and Information Administration (NTIA)</a>. Danny will have a leading role in fulfilling the NTIA's mandate to provide the President advice on telecommunications and information policy issues.</p> <p>Danny will thus be leaving the W3C staff, which he joined in 1998 as the Technology and Society Domain Lead. During these 11 years, Danny has contributed significantly to advances in many areas where policy meets technology, including privacy, security, intellectual property, and trust. As Chair of the Patent Policy Working Group, Danny led the effort that culminated in W3C's Royalty-Free Patent Policy, now a cornerstone of W3C's value proposition to the Web community.</p> <p>Before joining the W3C, Danny was co-founder and Deputy Director of the Center for Democracy and Technology and was Deputy Policy Director of the Electronic Frontier Foundation. Danny is also Director of the the <a href="http://dig.csail.mit.edu/">MIT CSAIL Decentralized Information Group</a> with Tim Berners- Lee and a founding director of the Web Science Research Initiative and holds an appointment as Principal Research Scientist at MIT's Computer Science and Artificial Intelligence Laboratory.</p> <p>While W3C regrets that Danny will be stepping down from W3C, it is encouraging that US policy may well be shaped by someone who has demonstrated a commitment to open standards as a tool for improving society. Danny, good luck!<span class="archive"> (<a title="Daniel Weitzner Named to Run US Government Internet Policy Unit" href="/News/2009#item135" rel="details">Permalink</a>) </span></p></div>
<div id="item134" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />W3C Invites Implementations of Widgets 1.0: Packaging and Configuration</h3><p><span class="date">2009-07-24:</span> The <a href="/2008/webapps/">Web Applications Working Group</a> invites implementation of the Candidate Recommendation of <a href="/TR/2009/CR-widgets-20090723/">Widgets 1.0: Packaging and Configuration</a>. This specification standardizes a packaging format for software known as widgets. Widgets are client-side applications that are authored using Web standards, but whose content can also be embedded into Web documents. The specification relies on PKWare's Zip specification as the archive format, XML as a configuration document format, and a series of steps that runtimes follow when processing and verifying various aspects of a package. The packaging format acts as a container for files used by a widget. The Working Group plans to develop a <a href="http://dev.w3.org/2006/waf/widgets/tests/">test suite</a> during the Candidate Recommendation phase. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.<span class="archive"> (<a title="W3C Invites Implementations of Widgets 1.0: Packaging and Configuration" href="/News/2009#item134" rel="details">Permalink</a>) </span></p></div>
<div id="item133" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft</h3><p><span class="date">2009-07-23:</span> The <a href="/WAI/UA/">User Agent Accessibility Guidelines Working Group</a> has published an updated Working Draft of the <a href="/TR/2009/WD-UAAG20-20090723/">User Agent Accessibility Guidelines (UAAG) 2.0</a>. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. Read the <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2009JulSep/0016.html">invitation to review the UAAG 2.0 Working Draft</a> and about the <a href="/WAI/">Web Accessibility Initiative (WAI)</a>. <span class="archive"> (<a title="User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft" href="/News/2009#item133" rel="details">Permalink</a>) </span></p></div>
<div id="item132" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Flexible Box Layout Module First Draft Published</h3><p><span class="date">2009-07-23:</span> The <a href="/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published the First Public Working Draft of <a href="/TR/2009/WD-css3-flexbox-20090723/">Flexible Box Layout Module</a>. The draft describes a CSS box model optimized for interface design. It provides an additional layout system alongside the ones already in CSS. This model is based on the box model in the XUL user-interface language. Learn more about the <a href="/Style/">Style Activity</a>.<span class="archive"> (<a title="Flexible Box Layout Module First Draft Published" href="/News/2009#item132" rel="details">Permalink</a>) </span></p></div>
<div id="item131" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />CSS Image Values Module Level 3 First Draft Published</h3><p><span class="date">2009-07-23:</span> The <a href="/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published the First Public Working Draft of <a href="/TR/2009/WD-css3-images-20090723/">CSS Image Values Module Level 3</a>. This CSS Image Values module defines the syntax for image values in CSS. Image values can be a single URI to an image, a list of URIs denoting a series of fallbacks, sprites (image slices), or gradients. Learn more about the <a href="/Style/">Style Activity</a>.<span class="archive"> (<a title="CSS Image Values Module Level 3 First Draft Published" href="/News/2009#item131" rel="details">Permalink</a>) </span></p></div>
<div id="item130" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />W3C Organizes Workshop on Improving Access to Financial Data on the Web</h3><p><span class="date">2009-07-16:</span> W3C invites people to participate in a <a href="/2009/03/xbrl/cfp.html">Workshop on Improving Access to Financial Data on the Web</a> on 5-6 October 2009 in Arlington, Virginia (USA). Workshop participants will discuss how to achieve greater transparency and more efficient reporting and analysis of business and financial data for companies and governments. The Workshop is jointly organized by W3C and <a href="http://www.xbrl.org/">XBRL International</a>, with hosting support from the <a href="http://www.fdic.gov/">Federal Deposit Insurance Corporation (FDIC)</a>. The extensible business reporting language (XBRL), is being widely adopted all around the world, and is set to become the standard way of recording, storing and transmitting business financial information. While effort on XBRL so far has gone into developing the standards and taxonomies of reporting concepts, comparatively little effort has been spent on how to exploit the expected flood of data. The goal of the Workshop is to identify opportunities, use cases, and challenges for interactive access to financial data expressed in XBRL and related languages, and the broader opportunities for using Semantic Web technologies. The Workshop is free of charge and open to anyone, subject to review of their statement of interest and space availability. Statements of interest (position papers) are due 21 August. See the <a href="/2009/03/xbrl/cfp">call for participation</a> for more information. Learn more about the <a href="/2001/sw/">Semantic Web</a>.<span class="archive"> (<a title="W3C Organizes Workshop on Improving Access to Financial Data on the Web" href="/News/2009#item130" rel="details">Permalink</a>) </span></p></div>
<div id="item129" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Best Practices for Authoring HTML: Handling Right-to-left Scripts Draft Published</h3><p><span class="date">2009-07-15:</span> The <a href="/International/core/">Internationalization Core Working Group</a> has published the Working Draft of <a href="/TR/2009/WD-i18n-html-tech-bidi-20090714/">Best Practices for Authoring HTML: Handling Right-to-left Scripts</a>. This document provides advice for the use of HTML markup and CSS style sheets to create pages for languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc. It explains how to create content in right-to-left scripts that builds on but goes beyond the Unicode bidirectional algorithm, as well as how to prepare content for localization into right-to-left scripts. Learn more about the <a href="/International/">Internationalization Activity</a>.<span class="archive"> (<a title="Best Practices for Authoring HTML: Handling Right-to-left Scripts Draft Published" href="/News/2009#item129" rel="details">Permalink</a>) </span></p></div>
<div id="item128" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />XML Signature Correction Addresses Security Issue</h3><p><span class="date">2009-07-14:</span> The <a href="/2008/xmlsec">XML Security Working Group</a> has published a <a href="/2008/06/xmldsigcore-errata.html#e03">proposed correction</a> to the <a href="/TR/xmldsig-core/">XML Signature</a> specification. The correction addresses a specification-level security issue that can lead to an authentication bypass (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217">CVE-2009-0217</a>). It will be incorporated into an upcoming Working Draft for the <a href="/TR/xmldsig-core1/">XML Signature 1.1</a> specification. For information about affected implementations, see <a href="http://www.kb.cert.org/vuls/id/466161">CERT Vulnerability Note 466161</a>. For more information about the issue, see the <a href="/QA/2009/07/hmac_truncation_in_xml_signatu.html">W3C Q&amp;A blog</a>. Learn more about W3C's <a href="/Security/">Security Activity</a>.<span class="archive"> (<a title="XML Signature Correction Addresses Security Issue" href="/News/2009#item128" rel="details">Permalink</a>) </span></p></div>
<div id="item127" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Relationship Between Mobile Web (MWBP) and Web Content Accessibility (WCAG) Note Published</h3><p><span class="date">2009-07-09:</span> The <a href="/2005/MWI/BPWG/">Mobile Web Best Practices Working Group</a> and the <a href="/WAI/EO/"><acronym title="Web Accessibility Initiative">WAI</acronym> Education and Outreach Working Group</a> have published <a href="/TR/2009/NOTE-mwbp-wcag-20090709/">Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)</a> as a W3C Working Group Note. The groups encourage people to <strong>start by reading</strong> <a href="/WAI/mobile/">Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices</a>, which shows how design goals for accessibility and mobile access overlap. A third document, <a href="/WAI/mobile/experiences">Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities</a>, provides examples of barriers that people (without disabilities) face when interacting with Web content via mobile devices, and similar barriers for people with disabilities using desktop computers. Learn more about the <a href="/Mobile/">Mobile Web Initiative (MWI)</a> and the <a href="/WAI/">Web Accessibility Initiative (WAI)</a>.<span class="archive"> (<a title="Relationship Between Mobile Web (MWBP) and Web Content Accessibility (WCAG) Note Published" href="/News/2009#item127" rel="details">Permalink</a>) </span></p></div>
<div id="item126" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />XPath 2.0 and XQuery 1.0 Full Text Facility Test Suite Published</h3><p><span class="date">2009-07-09:</span> The XSL and XML Query Working Groups have published version 1.0 of the <a href="http://dev.w3.org/cvsweb/2007/xpath-full-text-10-test-suite/">XPath 2.0 and XQuery 1.0 Full Text Facility Test Suite</a>, and are requesting that people with implementations report results. The Full Text Facility provides a standard way of searching by word or phrase across multilingual documents or data represented using the XPath and XQuery Data Model. As a result of preliminary implementation experience, and to reflect comments received, the <a href="/TR/2009/CR-xpath-full-text-10-20090709/">Candidate Recommendation for the Full Text Facility</a> has also been republished: the new version incorporates editorial changes but also clarifies some ambiguities that had been reported. The Working Groups hope to move the document to Proposed Recommendation once more test results have been submitted. The <a href="/XML/Query/">XML Query</a> and <a href="/Style/XSL/">XSL</a> Working Groups also published today an update of <a href="/TR/2009/WD-xpath-full-text-10-use-cases-20090709/">XQuery and XPath Full Text 1.0 Use Cases</a>. Learn more about the <a href="/XML/Activity">XML Activity</a>.<span class="archive"> (<a title="XPath 2.0 and XQuery 1.0 Full Text Facility Test Suite Published" href="/News/2009#item126" rel="details">Permalink</a>) </span></p></div>
<div id="item125" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Last Call: Geolocation API Specification</h3><p><span class="date">2009-07-07:</span> The <a href="/2008/geolocation/">Geolocation Working Group</a> has published a Last Call Working Draft of <a href="/TR/2009/WD-geolocation-API-20090707/">Geolocation API Specification</a>. The Geolocation API defines a high-level interface to location information associated only with the device hosting the implementation, such as latitude and longitude. Common sources of location information include Global Positioning System (GPS) and location inferred from network signals such as IP address, RFID, WiFi and Bluetooth MAC addresses, and GSM/CDMA cell IDs, as well as user input. Comments are welcome through 10 August. Learn more about the <a href="/2007/uwa/">Ubiquitous Web Applications Activity</a>.<span class="archive"> (<a title="Last Call: Geolocation API Specification" href="/News/2009#item125" rel="details">Permalink</a>) </span></p></div>
<div id="item122" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />W3C Launches Device APIs and Policy Working Group</h3><p><span class="date">2009-07-03:</span> W3C launched a new <a href="/2009/dap/">Device APIs and Policy Working Group</a>, co-Chaired by Robin Berjon (Vodafone) and Frederick Hirsch (Nokia). The group's mission is to create client-side APIs that enable the development of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, and Camera. Additionally, the group will produce a framework for the expression of security policies that govern access to security-critical APIs (such as the APIs listed previously). Per its <a href="/2009/05/DeviceAPICharter">charter</a>, this group will conduct its work in public. Learn more about the <a href="/2009/dap/">Device APIs and Policy Working Group</a>.<span class="archive"> (<a title="W3C Launches Device APIs and Policy Working Group" href="/News/2009#item122" rel="details">Permalink</a>) </span></p></div>
<div id="item123" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Last Call for Six Rule Interchange Format (RIF) Drafts</h3><p><span class="date">2009-07-03:</span> The <a href="/2005/rules">Rule Interchange Format (RIF) Working Group</a> has published six Last Call Working Drafts. Together, they allow systems using a variety of rule languages and rule-based technologies to interoperate with each other and with other Semantic Web technologies. Three of the drafts define XML formats with formal semantics for storing and transmitting rules: </p> <ul><li> The <a href="/TR/rif-prd/">RIF Production Rule Dialect (PRD)</a> is designed for the kinds of rules used in modern Business Rule Management systems. </li><li> The <a href="/TR/rif-bld/">RIF Basic Logic Dialect (BLD)</a> is a foundation for Logic Programming, classical logic, and related formalisms. </li><li> The <a href="/TR/rif-core/">RIF Core Dialect</a> is the common subset of PRD and BLD, useful when having a ubiquitous platform is paramount. </li></ul> <p>The other drafts:</p> <ul><li> <a href="/TR/rif-dtb/">RIF Datatypes and Builtins (DTB)</a> specifies the datatypes and standard operations (modeled on <a href="/TR/xpath-functions/">XPath Functions</a>) available in all RIF dialects </li><li> <a href="/TR/rif-rdf-owl/">RIF RDF and OWL Compatibility</a> specifies how RIF works with RDF, RDFS, OWL 1, and OWL 2. </li><li> <a href="/TR/rif-fld">RIF Framework for Logic Dialects (FLD)</a> provides a mechanism for specifying extended dialects, beyond BLD, when more expressive power is required. </li></ul> <p>The Working Group requests comments be sent to public-rif-comments@w3.org by 31 July 2009. Learn more about the <a href="/2001/sw">Semantic Web Activity</a>. <span class="archive"> (<a title="Last Call for Six Rule Interchange Format (RIF) Drafts" href="/News/2009#item123" rel="details">Permalink</a>) </span></p></div>
<div id="item124" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Live Training Sessions On Mobile Web Design Rescheduled</h3><p><span class="date">2009-07-03:</span> Originally scheduled for July, W3C has rescheduled a <a href="/2009/04/MobiWeb103/">Live Training Sessions On Mobile Web Design</a> for 13 October 2009. Students will attend a full day of lectures and hands on sessions about the <a href="/TR/2008/REC-mobile-bp-20080729/">W3C Mobile Web Best Practices</a> standard, and more generally on mobile Web design. Read the full <a href="/2009/06/live_mobile_training.html">announcement</a>, <a href="http://www.3gwebtrain.com/moodle/course/view.php?id=14">register</a>, and learn more about the <a href="/Mobile">W3C Mobile Web Initiative</a>.<span class="archive"> (<a title="Live Training Sessions On Mobile Web Design Rescheduled" href="/News/2009#item124" rel="details">Permalink</a>) </span></p></div>
<div id="item119" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />XHTML 2 Working Group Expected to Stop Work End of 2009, W3C to Increase Resources on HTML 5</h3><p><span class="date">2009-07-02:</span> Today the Director announces that when the <a href="/2007/03/XHTML2-WG-charter">XHTML 2 Working Group charter</a> expires as scheduled at the end of 2009, the charter will not be renewed. By doing so, and by increasing resources in the <a href="/html/wg/">HTML Working Group</a>, W3C hopes to accelerate the progress of <a href="/TR/html5">HTML 5</a> and clarify W3C's position regarding the future of HTML. A <a href="/2009/06/xhtml-faq.html">FAQ</a> answers questions about the future of deliverables of the XHTML 2 Working Group, and the status of various discussions related to HTML. Learn more about the <a href="/MarkUp/Activity">HTML Activity</a>. <span class="archive"> (<a title="XHTML 2 Working Group Expected to Stop Work End of 2009, W3C to Increase Resources on HTML 5" href="/News/2009#item119" rel="details">Permalink</a>) </span></p></div>
<div id="item121" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />Summary of Workshop on Speaker Biometrics and VoiceXML 3.0 Available</h3><p><a href="/2008/08/siv/summary.html"><img height="112" width="150" class="newsImage" alt="photo of Voice biometrics Workshop" src="/2008/08/siv/dsc_0004_480x360.jpg" /></a><span class="date">2009-07-02:</span> W3C has published a <a href="/2008/08/siv/summary.html">summary </a> and <a href="/2008/08/siv/minutes.html">full minutes</a> of the <a href="/2008/08/siv/cfp.html">Workshop on Speaker biometrics and VoiceXML 3.0</a>, that took place in Menlo Park, California on 5-6 March. Participants from 15 organizations focused discussion on Speaker Identification and Verification (SIV) functionality within VoiceXML 3.0, and identifying and prioritizing directions for the functionality. The major "takeaways" from the Workshop were confirmation that SIV fits into the VoiceXML space and creation of the "<a href="/2008/08/siv/MenloParkModel-v003.png">Menlo Park Model</a>", a SIV available VoiceXML architecture. The Working Group will continue to discuss how to include the requirements expressed at the Workshop into VoiceXML 3.0 and improve the specification. Learn more about the <a href="/Voice/">Voice Browser Activity</a>.<span class="archive"> (<a title="Summary of Workshop on Speaker biometrics and VoiceXML 3.0 Available" href="/News/2009#item121" rel="details">Permalink</a>) </span></p></div>
<div id="item120" class="item"><h3><img alt="" width="17" height="11" src="/Icons/right" />First Draft of SPARQL New Features and Rationale</h3><p><span class="date">2009-07-02:</span> The <a href="/2001/sw/DataAccess/">SPARQL Working Group</a> has published the First Public Working Draft of <a href="/TR/2009/WD-sparql-features-20090702/">SPARQL New Features and Rationale</a>. This document provides an overview of the main new features of SPARQL and their rationale. This is an update to SPARQL adding several new features that have been agreed by the SPARQL WG. These language features were determined based on real applications and user and tool-developer experience. Learn more about the <a href="/2001/sw/">Semantic Web Activity</a>.<span class="archive"> (<a title="First Draft of SPARQL New Features and Rationale" href="/News/2009#item120" rel="details">Permalink</a>) </span></p></div>
<h3 class="pastNews"><a href="/News/2009">Past News</a></h3>
</div>
<div class="navBlock">
<h2 class="navhead"><a name="search" id="search">Search</a></h2>
<p class="invisible"><a class="navlink" title="Skip search" href="#contents">Skip to Contents</a></p>
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<div>
<a class="navlink" href="http://www.google.com"><img src="/Icons/Logo_25wht.gif" width="75" height="32" alt="Google" /></a><br />
<label for="inputField">Search W3C<br />
<input type="text" size="15" id="inputField" name="q" accesskey="E" maxlength="255" /></label>
<input type="submit" value="Go" id="goButton" name="sa" accesskey="G" /><br />
<input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /> <input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org" /><input type="hidden" name="domains" value="www.w3.org" /> </div>
</form>
<p><a class="navlink" href="/Search/Mail/Public/">Search W3C Mailing
Lists</a></p>
<h2 class="navhead"><a name="contents" id="contents">Testimonials</a></h2>
<div class="hpmt"><div class="hpmt-name">Opera Software</div><div class="hpmt-logo"><a rel="nofollow" href="http://www.opera.com/"><img alt="Opera Software" src="http://www.w3.org/Consortium/Member/Testimonial/Logo/394" /></a></div><p class="hpmt-testimonial">Opera makes real cross-platform standards support a reality on mobile, desktop, and home media devices. Opera is proud to contribute its experience developing smaller, faster, more functional, friendly, secure browsers to W3C's open standards process, through significant participation. <a class="hpmt-more" href="http://www.w3.org/Consortium/Member/Testimonial/List">(Member testimonials)</a></p></div>
<h2 class="navhead">Members</h2>
<ul>
<li><a href="/Member/" class="navlink">Member Home Page</a></li>
<li><a href="/Submission/" class="navlink">Member Submissions</a></li>
<li><a href="/Consortium/Member/List" class="navlink">Current
Members</a></li>
<li><a href="/Consortium/meetings" class="navlink">Meetings</a></li>
<li><a href="/Consortium/Recruitment/Fellows" class="navlink">Fellows</a>
(<a href="/Consortium/Recruitment/Fellows#openings">New Openings</a>)</li>
</ul>
<h2 class="navhead">Get Involved</h2>
<ul>
<li><a href="/Consortium/membership-benefits" class="navlink">W3C
Membership Benefits</a></li>
<li><a href="/Consortium/membership#bizcase" class="navlink">Reasons to
Join W3C</a></li>
<li><a href="/Mail/" class="navlink">Mailing Lists</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-new-work/latest">Potential
New Work</a></li>
<li><a href="/Consortium/Translation/" class="navlink">Translations</a></li>
<li><a href="/2003/08/Workshops/" class="navlink">Workshops</a></li>
<li><a href="/2001/11/StdLiaison" class="navlink">Liaisons</a></li>
<li><a href="/Status" class="navlink">Open Source Software</a></li>
<li><a href="/QA/" class="navlink">Q&amp;A Blog</a></li>
<li><a href="/Consortium/Recruitment/" class="navlink">Employment</a></li>
<li><span class="navText">More ways to</span> <a href="/Consortium/org#public" class="navlink">participate</a></li>
</ul>
<h2 class="navhead">Introduction</h2>
<ul>
<li><a href="/Consortium/" class="navlink">About W3C</a></li>
<li><a href="/Consortium/faq" class="navlink">Frequently Asked Questions
(FAQ)</a></li>
<li><a href="/2003/glossary/" class="navlink">Glossary</a></li>
<li><a href="/Consortium/Process/" class="navlink">Process Document</a></li>
<li><a href="/2002/03/tutorials" class="navlink">Tutorials</a></li>
<li><a href="/2002/03/new-to-w3c" class="navlink">More...</a></li>
</ul>
<h2 class="navhead">W3C Team</h2>
<ul>
<li><a href="/People/" class="navlink">People</a></li>
<li><a href="/TeamSubmission/" class="navlink">Team Submissions</a></li>
</ul>
<h2 class="navhead">Presentations</h2>
<ul>
<li><a href="/Talks/" class="navlink">Public Presentations</a></li>
</ul>
<h2 class="navhead">News Room</h2>
<ul>
<li><a href="/News/" class="navlink">W3C News Archive</a> <span class="navText">(</span><a href="/2000/08/w3c-synd/home.rss" class="navlink">RSS</a><span class="navText">)</span></li>
<li><a href="/News/Public/" class="navlink">Weekly Public
Newsletter</a></li>
<li><a href="/Press/" class="navlink">Press Releases</a></li>
<li><a href="/Press/#rss" class="navlink">Multilingual Press Release
RSS</a></li>
<li><a href="/Press/Articles" class="navlink">W3C in the Press</a></li>
</ul>
<h2 class="navhead"><a name="Offices" id="Offices">World Offices</a></h2>
<p class="navPara">The <a href="/Consortium/Offices/" class="navlink">W3C
Offices</a>, part of the <a href="/2007/IntlRel.html">W3C International
Relations team</a> translate many W3C home page news items. W3C Offices are
located in these parts of the world:</p>
<ul>
<li><a href="http://www.w3c.org.au/" class="navlink" title="Australia">Australia</a></li>
<li><a href="http://www.w3c.nl/index.shtml.nl" class="navlink" hreflang="nl" title="Benelux"><span xml:lang="nl" lang="nl">Benelux</span></a>/<a href="http://www.w3c.nl/index.shtml.fr" class="navlink" title="Benelux" hreflang="fr"><span xml:lang="fr" lang="fr">Bénélux</span></a></li>
<li><a href="http://www.w3c.br/" class="navlink" title="Brazil" hreflang="pt-br"><span xml:lang="pt-br" lang="pt-br">Brasil</span>
(Brazil)</a></li>
<li><a href="http://www.chinaw3c.org/" class="navlink" title="China" hreflang="zh-hans"><span xml:lang="zh-hans" lang="zh-hans">中国</span>
(China)</a></li>
<li><a href="http://www.w3c.tut.fi/" class="navlink" title="Finland" hreflang="fi"><span xml:lang="fi" lang="fi">Suomi</span>
(Finland)</a></li>
<li><a href="http://www.w3c.de/" class="navlink" title="German and Austria" hreflang="de"><span xml:lang="de" lang="de">Deutschland und
Österreich</span> (Germany and Austria)</a></li>
<li><a href="http://www.w3c.gr/" class="navlink" title="Greece" hreflang="el"><span xml:lang="el" lang="el">Ελλάδα</span>
(Greece)</a></li>
<li><a href="http://www.w3c.hu/" class="navlink" title="Hungary" hreflang="hu"><span xml:lang="hu" lang="hu">Magyarország</span>
(Hungary)</a></li>
<li><a href="http://www.w3c.org.il/" class="navlink" title="Israel" hreflang="he"><span xml:lang="he" lang="he">ישראל</span>
(Israel)</a></li>
<li><a href="http://www.w3c.it/" class="navlink" title="Italy" hreflang="it"><span xml:lang="it" lang="it">Italia</span> (Italy)</a></li>
<li><a href="http://www.w3c.or.kr/" class="navlink" title="Korea" hreflang="ko"><span xml:lang="ko" lang="ko">한국</span> (Korea)</a></li>
<li><a href="http://www.w3c.org.ma/" class="navlink" title="Morocco" hreflang="ar"><span xml:lang="ar" lang="ar">المغرب</span>
(Morocco)</a></li>
<li><a href="http://www.w3c.sn/" class="navlink" title="Senegal" hreflang="fr">Sénégal</a></li>
<li><a href="http://www.w3c.org.za/" class="navlink" title="Southern Africa" hreflang="en">Southern Africa</a></li>
<li><a href="http://www.w3c.es/" class="navlink" title="Spain" hreflang="es"><span xml:lang="es" lang="es">España</span>
(Spain)</a></li>
<li><a href="http://www.w3c.se" class="navlink" title="Sweden" hreflang="sv"><span xml:lang="sv" lang="sv">Sverige</span>
(Sweden)</a></li>
<li><a href="http://www.w3c.rl.ac.uk/" class="navlink" title="UK and Ireland" hreflang="en-uk">United Kingdom and
Ireland</a></li>
</ul>
<h2 class="navhead"><a name="systems" id="systems">Systems</a></h2>
<ul>
<li><a href="/Help/Account/" class="navlink">Get Password</a></li>
<li><a href="/2003/08/system-status" class="navlink">System Status</a></li>
</ul>
<h2 class="navhead">World Wide Web Foundation</h2>
<p class="navPara">In 2008, W3C helped to create a separate organization, the
<a href="http://www.webfoundation.org/" class="navlink">World
Wide Web Foundation</a> with a
mission to advance the Web to connect humanity and empower people.
</p>
</div>
<hr class="hide" />
<p class="small">W3C would like to thank the <a name="donors" id="donors" href="/Consortium/sup">Supporters</a> who have contributed financially or
through a donation of goods to W3C.</p>
<p class="small"><a name="footnotes" id="footnotes">Read</a> <a href="/2002/11/homepage">about the layout</a> and <a href="http://lists.w3.org/Archives/Public/site-comments/">send comments</a>
about this page. <a href="/2000/08/w3c-synd/home.rss">Syndicate</a> this page
with <a href="http://purl.org/rss/1.0/">RSS 1.0</a>, an <a href="/RDF/">RDF</a> vocabulary used for <a href="/2000/08/w3c-synd/#">site
summaries</a>. </p>
<address class="small">
<a href="/Help/Webmaster">Webmaster</a> · Last modified:
$Date: 2009/07/31 02:15:25 $
<span class="whiteout">|</span><br />
<a href="http://validator.w3.org/check?uri=referer"><img src="/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" height="31" width="88" /></a> <span class="whiteout">|</span> <a href="http://jigsaw.w3.org/css-validator/"><img src="/Icons/valid-css" alt="Valid CSS!" height="31" width="88" /></a> <span class="whiteout">|</span> <a href="/WAI/WCAG1AA-Conformance" title="Explanation of Level Double-A Conformance"><img class="conform" height="31" width="88" src="/WAI/wcag1AA" alt="Level Double-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0" /> </a> <span class="whiteout">|</span>
</address>
<p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1994-2009 <a href="/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document use</a>
and <a rel="Copyright" href="/Consortium/Legal/copyright-software">software
licensing</a> rules apply. Your interactions with this site are in accordance
with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="/Consortium/Legal/privacy-statement#Members">Member</a> privacy
statements.</p>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink