Skip to main content

Home/ Future of the Web/ Group items tagged w3c

Rss Feed Group items tagged

Paul Merrell

Archive of W3C News in 2009 - 0 views

  • 2009-08-26: The HTML Working Group has published Working Drafts of HTML 5 and HTML 5 differences from HTML 4. In HTML 5, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. Learn more about HTML. (Permalink)
Gary Edwards

Official Google Webmaster Central Blog: Introducing Rich Snippets - 0 views

  •  
    Google "Rich Snippets" is a new presentation of HTML snippets that applies Google's algorithms to highlight structured data embedded in web pages. Rich Snippets give end-users convenient summary information about their search results at a glance. Google is currently supporting a very limited subset of data about reviews and people. When searching for a product or service, users can easily see reviews and ratings, and when searching for a person, they'll get help distinguishing between people with the same name. It's a simple change to the display of search results, yet our experiments have shown that users find the new data valuable. For this to work though, both Web-masters and Web-workers have to annotate thier pages with structured data in a standard format. Google snippets supports microformats and RDFa. Existing Web data can be wrapped with some additional tags to accomplish this. Notice that Google avoids mention of RDF and the W3C's vision of a "Semantic Web" where Web objects are fully described in machine readable semantics. Over at the WHATWG group, where work on HTML5 continues, Google's Ian Hickson has been fighting RDFa and the Semantic Web in what looks to be an effort to protect the infamous Google algorithms. RDFa provides a means for Web-workers, knowledge-workers, line-of-business managers and document generating end-users to enrich their HTML+ with machine semantics. The idea being that the document experts creating Web content can best describe to search engine and content management machines the objects-of-information used. The google algorithms provide a proprietary semantics of this same content. The best solution to the tsunami of conten the Web has wrought would be to combine end-user semantic expertise with Google algorithms. Let's hope Google stays the RDFa course and comes around to recognize the full potential of organizing the world's information with the input of content providers. One thing the world desperatel
Paul Merrell

HTML 5 differences from HTML 4 - 0 views

  • W3C Working Draft 12 February 2009
  • HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. This document may not provide accurate information as the HTML 5 specification is still actively in development. When in doubt, always check the HTML 5 specification itself. [HTML5]
Paul Merrell

W3C releases Working Draft for Widgets 1.0: APIs and Events - 0 views

  • This specification defines a set of APIs and events for the Widgets 1.0 Family of Specifications that enable baseline functionality for widgets. The APIs and Events defined by this specification defines, amongst other things, the means to:access the metadata declared in a widget's configuration document, receive events related to changes in the view state of a widget, determine the locale under which a widget is currently running, be notified of events relating to the widget being updated, invoke a widget to open a URL on the system's default browser, requests the user's attention in a device independent manner, and check if any additional APIs requested via the configuration document's feature element have successfully loaded.
  • This specification defines a set of APIs and events for widgets that enable baseline functionality for widgets. Widgets are full-fledged client-side applications that are authored using Web standards. They are typically downloaded and installed on a client machine or device where they typically run as stand-alone applications outside of a Web browser. Examples range from simple clocks, stock tickers, news casters, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way
  • This specification is part of the Widgets 1.0 family of specifications, which together standardize widgets as a whole. The Widgets 1.0: Packaging and Configuration [Widgets-Packaging] standardizes a Zip-based packaging format, an XML-based configuration document format and a series of steps that user agents follow when processing and verifying various aspects of widgets. The Widgets 1.0: Digital Signature [Widgets-DigSig] specification defines a means for widgets to be digitally signed using a custom profile of the XML-Signature Syntax and Processing Specification. The Widgets: 1.0: Automatic Updates [Widgets-Updates] specification defines a version control model that allows widgets to be kept up-to-date over [HTTP].
Paul Merrell

W3C Helps Authors Go Mobile - 0 views

  • http://www.w3.org/ -- 8 December 2008 -- Today, W3C has made it easier to create content designed to improve people's mobile experience using a broad range of devices. W3C invites the community to try the W3C mobileOK checker, which is based on the newly published standard, the mobileOK Basic Tests 1.0 Recommendation. "The new checker builds on the suite of quality assurance tools offered by W3C to help authors and authoring tool developers create clean content," said Tim Berners-Lee, W3C Director. "Clean content offers a number of benefits to authors and users alike. The mobileOK checker does a nice job helping you improve your content one step at a time. Your mobile audience will thank you each time you improve your score."
  • The mobileOK Basic tests are based on the part of the Mobile Web Best Practices that can be verified automatically with software. The checker makes use of the popular W3C validator to help improve content quality. In addition to the mobile-friendliness score, the checker offers tips for meeting the needs of people on the go.
Paul Merrell

OWL 2 Web Ontology Language:New Features and Rationale - 0 views

  • Abstract OWL 2 extends the W3C OWL Web Ontology Language with a small but useful set of features that have been requested by users, for which effective reasoning algorithms are now available, and that OWL tool developers are willing to support. The new features include extra syntactic sugar, additional property and qualified cardinality constructors, extended datatype support, simple metamodeling, and extended annotations. This document is a simple introduction to the new features of the OWL 2 Web Ontology Language, including an explanation of its differences with respect to OWL 1. It also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective.
Paul Merrell

The Self-Describing Web - 0 views

  • Abstract The Web is designed to support flexible exploration of information by human users and by automated agents. For such exploration to be productive, information published by many different sources and for a variety of purposes must be comprehensible to a wide range of Web client software, and to users of that software. HTTP and other Web technologies can be used to deploy resource representations that are in an important sense self-describing: information about the encodings used for each representation is provided explicitly within the representation. Starting with a URI, there is a standard algorithm that a user agent can apply to retrieve and interpret such representations. Furthermore, representations can be grounded in the Web, by ensuring that specifications required to interpret them are determined unambiguously based on the URI, and that explicit references connect the pertinent specifications to each other. Web-grounding reduces ambiguity as to what has been published in the Web, and by whom. When such self-describing, Web-grounded resources are linked together, the Web as a whole can support reliable, ad hoc discovery of information. This finding describes how document formats, markup conventions, attribute values, and other data formats can be designed to facilitate the deployment of self-describing, Web-grounded Web content.
Paul Merrell

[ANN] Markup Validator 0.8.4 released from Olivier Thereaux on 2008-11-20 (www-validato... - 0 views

  • I am thrilled to announce today the release of a new version of the W3C Markup Validation Service, also known as "HTML Validator". Use it online http://validator.w3.org/ .... or download it: it is Free and Open Source http://validator.w3.org/source/ The new version, 0.8.4 may sound like a very minor step from the version 0.8.3 released in August, but this new release of the W3C Markup Validator brings some very important change: in addition to checking documents against etablished standards such as HTML 4.01 and XHTML 1.0, the validator can now check documents for conformance to HTML5, thanks to the integration with the Validator.nu html5 engine.
  • HTML5 is still work in progress and support for this next generation of the publishing language of the World Wide Web will remain experimental. The integration of the html5 engine in the validator should provide experimentation grounds for those interested in trying on authoring in this new version of HTML, as well as a feedback channel for the group working on building a stable, open standard.
Gary Edwards

Coding In Paradise: Fixing the Web, Part I - 0 views

  •  
    Must read: "This blog post is part of a new, semi-regular series called Fixing the Web. The goal is to highlight these issues, identify potential solutions, and have a dialogue. I don't claim to have the answers for the situation we are in. However, I do know this -- if there is any community that potentially has what it takes to solve these issues I believe it's the Ajax and JavaScript communities, which is why this is a perfect place to have these discussions. To start, I see four areas that are broken that must be fixed: ..... "
Paul Merrell

W3C Public Newsletter 2008 06 09 - 0 views

  • W3C launched a new Web Applications (WebApps) Working Group, co-Chaired by Art Barstow (Nokia) and Charles McCathieNevile (Opera Software). This group merges the former Web APIs and Web Application Formats Working Groups. Per the charter for the Web Applications Working Group, the group's mission is to provide specifications that enable improved client-side application development on the Web, including specifications both for application programming interfaces (APIs) for client-side development and for markup vocabularies for describing and controlling client-side application behavior.
Paul Merrell

W3C Public Newsletter, 2008-11-03 from W3C Newsletter on 2008-11-03 (w3c-announce@w3.or... - 0 views

  • The Web Content Accessibility Guidelines (WCAG) Working Group has published the "Web Content Accessibility Guidelines 2.0" as a Proposed Recommendation, and published updated Working Drafts of "Understanding WCAG 2.0," "Techniques for WCAG 2.0," and How to Meet WCAG 2.0. WCAG defines how to make Web sites, Web applications, and other Web content accessible to people with disabilities. Comments are welcome through 2 December 2008. Read the announcement, Overview of WCAG 2.0 Documents, and about the Web Accessibility Initiative. http://www.w3.org/WAI/GL/ http://www.w3.org/TR/2008/PR-WCAG20-20081103/ http://www.w3.org/TR/2008/CR-UNDERSTANDING-WCAG20-20081103/ http://www.w3.org/TR/2008/CR-WCAG20-TECHS-20081103/ http://www.w3.org/WAI/WCAG20/quickref/ http://lists.w3.org/Archives/Public/w3c-wai-ig/2008OctDec/0091 http://www.w3.org/WAI/intro/wcag20.php http://www.w3.org/WAI/
Paul Merrell

Pronunciation Lexicon Specification (PLS) Version 1.0 - 0 views

  • Pronunciation Lexicon Specification (PLS) Version 1.0 W3C Recommendation 14 October 2008
  • The accurate specification of pronunciation is critical to the success of speech applications. Most Automatic Speech Recognition (ASR) and Text-To-Speech (TTS) engines internally provide extensive high quality lexicons with pronunciation information for many words or phrases. To ensure a maximum coverage of the words or phrases used by an application, application-specific pronunciations may be required. For example, these may be needed for proper nouns such as surnames or business names. The Pronunciation Lexicon Specification (PLS) is designed to enable interoperable specification of pronunciation information for both ASR and TTS engines. The language is intended to be easy to use by developers while supporting the accurate specification of pronunciation information for international use.
Paul Merrell

Fight over 'forms' clouds future of Net applications | Pagalz.com - Blog - 0 views

  • As Net heavyweights vie to define the next generation of Web applications, the Web’s main standards body is facing a revolt within its own ranks over electronic forms, a cornerstone of interactive documents.
  • “The W3C is saying the answer is XForms. Microsoft is saying it’s XAML. Macromedia is saying its Flash MX. And Mozilla is saying it’s XUL.
  • Though the success of one method or another might not seem to make much difference to the person filling out an order form, the fate of open standards in the process could determine whether that form can relay the data it collects to any standards-compliant database or banking system, or whether it can only operate within certain proprietary systems. The fate of a standard could also determine whether the order form could be accessed in any standards-compliant Web browser, or if it would be available only to users of a particular operating system–an outcome that has browser makers and others worried about the role of Microsoft.
  • ...5 more annotations...
  • browser makers still want a standards-based forms technology to help the Web steer clear of proprietary application platforms. They’re particularly concerned about Microsoft’s sprawling vision for Windows “Longhorn” applications built in the XML-based XAML markup language using Longhorn’s Avalon graphics system. Browsers like Mozilla Firefox, Opera and Apple’s Safari will be useless to access these Internet-based Windows applications.
  • “The WHAT approach works OK for small examples,” Pemberton said. “But actors like the Department of Defense say ‘no scripting.’”
  • HAT approach works OK for small examples,” Pemberton said. “But actors like the Department of Defense say ‘no scripting.’”
  • The evolution versus revolution debate over forms centers on the use of scripting–specifically JavaScript–to perform important tasks in forms-based applications.
  • “I understand where WHAT is coming from, but they are browser makers, not forms experts,” Pemberton said. “It is important to build something that is future-proof and not a Band-Aid solution. Forms (technology) is the basis of the e-commerce revolution and so it is important to do it right.”
Gary Edwards

Ajaxian » In Praise of Evolvable Systems - 0 views

  •  
    "Why something as poorly designed as the Web became The Next Big Thing, and what that means for the future." Well designed but "fixed" systems were over taken by the evolvable but poorly designed Web. I'm wonderig if these same "evolving" principles apply to standard organizations? Put WebKit up against the standard orgs in charge of key WebKit components, and you see clearly that WebKit would fail misably if they stuck to the hapless efforts of the W3C, Ecma and ISO. Besides the fact that entrenched players such as Microsoft are sitting on those standards orgs in position to dumb down or put into terminal stall much needed innovations. For instance, WebKit deepneds on HTML5, CSS3, SVG, and JavaScript. All of which are stalled at various standards orgs. As a reaction to this org stall, the WebKit group pushes forward anyway relying instead on OSS Community style innovation and consensus model sharing.
Paul Merrell

W3C Standards Make Mobile Web Experience More Inviting - 0 views

  • W3C today announced new standards that will make it easier for people to browse the Web on mobile devices. Mobile Web Best Practices 1.0, published as a W3C Recommendation, condenses the experience of many mobile Web stakeholders into practical advice on creating mobile-friendly content.
  • Until today, content developers faced an additional challenge: a variety of mobile markup languages to choose from. With the publication of the XHTML Basic 1.1 Recommendation today, the preferred format specification of the Best Practices, there is now a full convergence in mobile markup languages, including those developed by the Open Mobile Alliance (OMA). The W3C mobileOK checker (beta), when used with the familiar W3C validator, helps developers test mobile-friendly Web content.
  • W3C is also developing resources to help authors understand how to create content that is both mobile-friendly and accessible to people with disabilities. A draft of Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) is jointly published by the The Mobile Web Best Practices Working Group and WAI's Education & Outreach Working Group (EOWG).
  •  
    Most quality online stores. Know whether you are a trusted online retailer in the world. Whatever we can buy very good quality. and do not hesitate. Everything is very high quality. Including clothes, accessories, bags, cups. Highly recommended. This is one of the trusted online store in the world. View now www.retrostyler.com
Gary Edwards

Is the W3C to Blame for the Breaking of the Web? | Continuing Intermittent In... - 0 views

  • Consider the recent CSS features added by WebKit: transformations, animations, gradients, masks, et cetera. They’ve very nearly _run out_ of standards to implement, so they’re starting to implement the wouldn’t-it-be-cool-if stuff. If I’m not mistaken, this is the exact sort of thing you’re wishing for.
  • Changing the renderer (which is what we’re taking about when we talk about upgrading “the web”) goes hand-in-hand today with upgrading the *rest* of the browser as well, which requires the user to care…and users (to a one) don’t give a flying leap about CSS 2.1 support.
    • Gary Edwards
       
      Note to marbux: the browser is the layout/rendering engine for web applications and services. Nothing happens on the web unless and until the browser, or a browser RiA alternative, implements a compliant end user interface. Focus on the browser layout engines, and Web applications will follow.
  •  
    Another article taking up the issue of "Blame the W3C" for what increasingly looks like a proprietary Web future. The author is an Ajax-DOJO supporter, and he tries to defend the W3C by saying it's not their job, they don't have the "power" or the "authority" to push the Web forward. About the best they can do is, at the end of the day, try to corral big vendors into agreement. Meanwhile, the Web has become the wild wild west with browser vendors innovating into their corporate web stacks where vast profits and future monopolies rest. For me, WebKit represents the best effort insisting that the Web remain Open. It's OSS with excellent big vendor support. And they are pushing the envelope. Finally!
Gary Edwards

WebKit and the Future of the Open Web - 0 views

  •  
    I reformatted my response to marbux concerning HTML5 and web application lack of interoperability. The original article these comments were posted to is titled, "Siding with HTML over XHTML, My Decision to Switch.... ".
‹ Previous 21 - 40 of 43 Next ›
Showing 20 items per page