- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 25 Nov 2009 01:10:28 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8365 --- Comment #12 from Shelley Powers <shelleyp@burningbird.net> 2009-11-25 01:10:27 --- > It looks like there is link traversal, navigation, and networking support, even > if somewhat restricted. It looks like there are no frames or scripting. > I wouldn't include networking per se. > > > > Now, it doesn't make use of all HTML elements. At the same time, the ePub folks > > aren't coming into the HTML WG and demanding that we support OPF in HTML5, > > either. Why? Because that's application specific, and doesn't have a place in a > > general purpose language such as HTML. > > Since ePub is defined as a subset of XHTML, it doesn't make sense to me to > remove anything from the HTML5 spec on the basis that ePub doesn't need it. > It's already a subset specification. > I wouldn't remove any element of HTML because only one user agent uses only a subset. But I don't think user agents should impose their own unique requirements, either. > > > > All applications that make use of HTML or XHTML have their own requirements and > > needs. The appropriate procedure is to define specifications for the > > application functionality, and leave the HTML markup for the HTML WG. > > > > It's true that there are different kinds of HTML clients. HTML5 provides for > this with a variety of conformance classes: > http://dev.w3.org/html5/spec/Overview.html#conformance-requirements > There should be a simplified set of conformation requirements for all clients related to HTML, XHTML, and the DOM. > It clearly says that non-scripting UAs are exempt from implementing any of the > scripting features, for instance. The scripting features in section 6 don't > look any different to me in this regard than other scripting- and event-related > requirements throughout the spec. > Again, though, I don't think that we should be including application specific requirements into what should be a general markup language, and associated DOM. To be honest, we're in a real risk of never being able to be finished with HTML5 because we keep letting new requirements push out the scope. > There doesn't seem to be explicit provision for HTML clients that support > interaction, but never navigate (such as mail clients). > -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 25 November 2009 01:10:37 UTC