marbux 's Bookmarks tagged xhtml → View Popular

You are here: Diigo Home > marbux 's Bookmarks

Expand All 1 - 2 of 2

Digital Web Magazine - HTML5, XHTML2, and the Future of the Web

The browser-centric view of why HTML5 is better than XHTML2. Notice that the entire discussion does not address the need for interoperable data exchange between different web applications, let alone for their interaction with more traditional desktop or mobile device editors. HTML5 is enormously under-specified for data exchange among anything but web browsers. As only one small example, neither HTML5 nor CSS Selectors have a specified standard element for footnotes and footnote calls, let alone attributes for their numbering style, formatting, and location. And even if CSS Selectors included such elements and attributes, CSS lives in web site page templates, not in the web app editors for site content that use HTML forms. Easy pickings for Microsoft and its proprietary stack that does interoperably integrate the desktop, servers, devices, and the Web.

Tags: html5, xhtml, xml, xhtml2, html, standards, CSS, interop, blunders on 2008-05-29 and saved by11 people -All Annotations (0) -About

more fromwww.digital-web.com

6Expand

Sir Tim Berners-Lee on 'Reinventing HTML'

Tags: Berners-Lee, HTML5, XHTML, XForms, standards, w3c, html on 2008-05-29 and saved by11 people -All Annotations (0) -About

more fromdig.csail.mit.edu

The perceived accountability of the HTML group has been an issue. Sometimes this was a departure from the W3C process, sometimes a sticking to it in principle, but not actually providing assurances to commenters. An issue was the formation of the breakaway WHAT WG, which attracted reviewers though it did not have a process or specific accountability measures itself.
Some things are very clear. It is really important to have real developers on the ground involved with the development of HTML. It is also really important to have browser makers intimately involved and committed. And also all the other stakeholders, including users and user companies and makers of related products.
Some things are clearer with hindsight of several years. It is necessary to evolve HTML incrementally. The attempt to get the world to switch to XML, including quotes around attribute values and slashes in empty tags and namespaces all at once didn't work. The large HTML-generating public did not move, largely because the browsers didn't complain.
Some large communities did shift and are enjoying the fruits of well-formed systems, but not all. It is important to maintain HTML incrementally, as well as continuing
a transition to well-formed world, and developing more power in that world.
The plan is, informed by Webforms, to extend HTML forms. At the same time, there is a work item to look at how HTML forms (existing and extended) can be thought of as XForm equivalents, to allow an easy escalation path. A goal would be to have an HTML forms language which is a superset of the existing HTML language, and a subset of a XForms language wit added HTML compatibility.
There will be no dependency of HTML work on the XHTML2 work.
This is going to be a very major collaboration on a very important spec, one of the crown jewels of web technology. Even though hundreds of people will be involved, we are evolving the technology which millions going on billions will use in the future. There won't seem like enough thankyous to go around some days.

1 - 2 of 2

List 20 50 100

Notation: * = Private bookmark and comment|… = Clipping [?] | … = Public highlight [?]

marbux 's Related Tags

Selected tags

xhtml

Related tags

See More Top Contributors

isaac Mao Toshiro Shimura Mr U1 eniope alfred westerveld Gary Edwards

Related Groups on Diigo

In-the-Clouds-with-SOA-XML-and-the-Open-Web

Members (3)

bookmarks (80)
Future of the Web

Members (7)

bookmarks (92)
Coders

Members (115)

bookmarks (941)