Misplaced Pages

#124875

54-501: CE-HTML is an XHTML -based standard for designing webpages with remote user interfaces for consumer electronic devices on Universal Plug and Play networks. The standard is intended for defining user interfaces that can gracefully scale on a variety of screen sizes and geometries, including those of mobile devices to high definition television sets . CE-HTML is part of the CEA-2014 standard (also referred to as " Web4CE " which

108-541: A web browser adapted for the CE-HTML standard running on a consumer electronics device. CE-HTML offers specific extensions for these browsers such as : Typical CE-HTML code looks like this: CE-HTML was developed within the Consumer Electronics Association R7WG9 working group – consisting of a number of CE-manufacturers – to formulate an answer to the problem of displaying HTML (web) content on

162-821: A W3C Recommendation. There are three formal Document Type Definitions (DTD) for XHTML 1.0, corresponding to the three different versions of HTML 4.01: The second edition of XHTML 1.0 became a W3C Recommendation in August 2002. Modularization provides an abstract collection of components through which XHTML can be subsetted and extended. The feature is intended to help XHTML extend its reach onto emerging platforms, such as mobile devices and Web-enabled televisions. The initial draft of Modularization of XHTML became available in April 1999, and reached Recommendation status in April 2001. The first modular XHTML variants were XHTML 1.1 and XHTML Basic 1.0. In October 2008 Modularization of XHTML

216-585: A W3C recommendation on 31 May 2001. XHTML is now referred to as "the XML syntax for HTML" and being developed as an XML adaptation of the HTML living standard. XHTML 1.0 was "a reformulation of the three HTML 4 document types as applications of XML 1.0". The World Wide Web Consortium (W3C) also simultaneously maintained the HTML 4.01 Recommendation. In the XHTML 1.0 Recommendation document, as published and revised in August 2002,

270-661: A component of their OMA Browsing Specification. To this version, finalized in 2004, the OMA added partial support for the Scripting Module and partial support for Intrinsic Events. XHTML MP 1.1 is part of v2.1 of the OMA Browsing Specification (1 November 2002). This version, finalized on 27 February 2007, expands the capabilities of XHTML MP 1.1 with full support for the Forms Module and OMA Text Input Modes. XHTML MP 1.2

324-455: A copy of the DTD to use, if the validator cannot locate one based on the public identifier (the other quoted string). It does not need to be the specific URL that is in these examples; in fact, authors are encouraged to use local copies of the DTD files when possible. The public identifier, however, must be character-for-character the same as in the examples. A character encoding may be specified at

378-399: A device that does not possess the characteristics of a typical personal computer. CE devices have problems displaying regular web pages because these pages make use of: Further difficulties with using a CE device to display web content are caused by the fact that CE devices typically have different capabilities such as different resolutions, remote controls and audio/video codecs . CE-HTML

432-558: A feature-limited XHTML specification called XHTML Basic. It provides a minimal feature subset sufficient for the most common content-authoring. The specification became a W3C recommendation in December 2000. Of all the versions of XHTML, XHTML Basic 1.0 provides the fewest features. With XHTML 1.1, it is one of the two first implementations of modular XHTML. In addition to the Core Modules (Structure, Text, Hypertext, and List), it implements

486-499: A new HTML specification, posted in his blog that "[t]he attempt to get the world to switch to XML ... all at once didn't work. The large HTML-generating public did not move ... Some large communities did shift and are enjoying the fruits of well-formed systems ... The plan is to charter a completely new HTML group." The current HTML5 working draft says "special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability ... while at

540-547: A patent policy. This spurred a renewed attempt to allow the W3C and the WHATWG to work together on specifications. In 2019, the W3C and WHATWG agreed to a memorandum of understanding where development of HTML and DOM specifications would be done principally in the WHATWG. The editor has significant control over the specification, but the community can influence the decisions of the editor. In one case, editor Ian Hickson proposed replacing

594-449: A standard that supported both XML and non-XML serializations , HTML5 , in parallel to W3C standards such as XHTML 2.0. In 2007, the W3C's HTML working group voted to officially recognize HTML5 and work on it as the next-generation HTML standard. In 2009, the W3C allowed the XHTML 2.0 Working Group's charter to expire, acknowledging that HTML5 would be the sole next-generation HTML standard, including both XML and non-XML serializations. Of

SECTION 10

#1732854786125

648-470: Is 1.1 Second Edition (23 November 2010), in which the language is re-implemented in the W3C's XML Schema language. This version also supports the lang attribute. XHTML-Print, which became a W3C Recommendation in September 2006, is a specialized version of XHTML Basic designed for documents printed from information appliances to low-end printers . XHTML Mobile Profile (abbreviated XHTML MP or XHTML-MP)

702-783: Is a community of people interested in evolving HTML and related technologies. The WHATWG was founded by individuals from Apple Inc. , the Mozilla Foundation and Opera Software , leading Web browser vendors in 2004. WHATWG is responsible for maintaining multiple web-related technical standards , including the specifications for the HyperText Markup Language (HTML) and the Document Object Model (DOM). The central organizational membership and control of WHATWG – its "Steering Group" – consists of Apple, Mozilla, Google, and Microsoft. WHATWG community members work with

756-580: Is a third-party variant of the W3C's XHTML Basic specification. Like XHTML Basic, XHTML was developed for information appliances with limited system resources. In October 2001, a limited company called the Wireless Application Protocol Forum began adapting XHTML Basic for WAP 2.0 , the second major version of the Wireless Application Protocol . WAP Forum based their DTD on the W3C's Modularization of XHTML, incorporating

810-562: Is an extended version of the XHTML markup language for supporting RDF through a collection of attributes and processing rules in the form of well-formed XML documents. This host language is one of the techniques used to develop Semantic Web content by embedding rich semantic markup. An XHTML document that conforms to an XHTML specification is said to be valid . Validity assures consistency in document code, which in turn eases processing, but does not necessarily ensure consistent rendering by browsers. A document can be checked for validity with

864-931: Is important to distinguish whether it is media type usage or actual document contents that are being compared. Most web browsers have mature support for all of the possible XHTML media types. The notable exception is Internet Explorer versions 8 and earlier by Microsoft ; rather than rendering application/xhtml+xml content, a dialog box invites the user to save the content to disk instead. Both Internet Explorer 7 (released in 2006) and Internet Explorer 8 (released in March 2009) exhibit this behavior. Microsoft developer Chris Wilson explained in 2005 that IE7's priorities were improved browser security and CSS support, and that proper XHTML support would be difficult to graft onto IE's compatibility-oriented HTML parser; however, Microsoft added support for true XHTML in IE9 . As long as support

918-598: Is increasingly used within other standards, such as the Open IPTV Forum , the Digital Living Network Alliance (as of version 2) and HbbTV . Some research suggests that CEA-2014 (of which CE-HTML is an important part) will be one of the key technologies in the living room internet experience. There are currently a number of browser vendors and solution providers that claim to have a CE-HTML capable browser, such as Oregan developed by Oregan Networks Ltd and

972-654: Is more expressive than HTML (for example, arbitrary namespaces are not allowed in HTML). XHTML uses an XML syntax, while HTML uses a pseudo- SGML syntax (officially SGML for HTML 4 and under, but never in practice, and standardized away from SGML in HTML5). Because the expressible contents of the DOM in syntax are slightly different, there are some changes in actual behavior between the two models. Syntax differences, however, can be overcome by implementing an alternate translational framework within

1026-437: Is not widespread, most web developers avoid using XHTML that is not HTML-compatible, so advantages of XML such as namespaces, faster parsing, and smaller-footprint browsers do not benefit the user. In the early 2000s, some Web developers began to question why Web authors ever made the leap into authoring in XHTML. Others countered that the problems ascribed to the use of XHTML could mostly be attributed to two main sources:

1080-551: Is part of v2.3 of the OMA Browsing Specification (13 March 2007). XHTML MP 1.3 (finalized on 23 September 2008) uses the XHTML Basic 1.1 document type definition , which includes the Target Module. Events in this version of the specification are updated to DOM Level 3 specifications (i.e., they are platform- and language-neutral). The XHTML 2 Working Group considered the creation of a new language based on XHTML 1.1. If XHTML 1.2

1134-543: Is short for Web for Consumer Electronics), defined within the Consumer Electronics Association (CEA). CE-HTML consists of the following internet languages: CE-HTML can both be used in-home through UPnP as via the Internet. It allows the content creator to use the common and known languages in the web to define a user interface that can be controlled on a CE device. A CE-HTML client typically consists of

SECTION 20

#1732854786125

1188-462: Is simply a myth". December 1998 saw the publication of a W3C Working Draft entitled Reformulating HTML in XML . This introduced Voyager, the codename for a new markup language based on HTML 4, but adhering to the stricter syntax rules of XML. By February 1999 the name of the specification had changed to XHTML 1.0: The Extensible HyperText Markup Language , and in January 2000 it was officially adopted as

1242-412: The <time> tag with a more generic <data> tag, but the community disagreed and the change was reverted. Initially, the name Web Hypertext Application Technology Task Force was also used, along with variant abbreviations including WHAT Working Group , WHAT Task Force and WHATTF . After some time using both the whattf.org and whatwg.org domain names , the name WHATWG

1296-662: The W3C Markup Validation Service (for XHTML5, the Validator. nu Living Validator should be used instead). In practice, many web development programs provide code validation based on the W3C standards. The root element of an XHTML document must be html , and must contain an xmlns attribute to associate it with the XHTML namespace . The namespace URI for XHTML is http://www.w3.org/1999/xhtml . The example tag below additionally features an xml:lang attribute to identify

1350-593: The W3C commented that "The XHTML family is the next step in the evolution of the Internet. By migrating to XHTML today, content developers can enter the XML world with all of its attendant benefits, while still remaining confident in their content's backward and future compatibility." However, in 2005, the Web Hypertext Application Technology Working Group (WHATWG) formed, independently of the W3C, to work on advancing ordinary HTML not based on XHTML. The WHATWG eventually began working on

1404-517: The W3C members at the W3C Workshop on Web Applications and Compound Documents. On 10 April 2007, the Mozilla Foundation, Apple, and Opera Software proposed that the new HTML working group of the W3C adopt the WHATWG's HTML5 as the starting point of its work and name its future deliverable as "HTML5" (though the WHATWG specification was later renamed HTML Living Standard ). On 9 May 2007,

1458-399: The W3C provided guidance on how to publish XHTML 1.0 documents in an HTML-compatible manner, and serve them to browsers that were not designed for XHTML. Such "HTML-compatible" content is sent using the HTML media type ( text/html ) rather than the official Internet media type for XHTML ( application/xhtml+xml ). When measuring the adoption of XHTML to that of regular HTML, therefore, it

1512-643: The Wedison project which is based on Webkit . Philips released the first devices which support the CE-HTML standard through the Net TV feature in Europe in April, 2009, which in 2010 expanded to include Sharp and Loewe platforms. Smart TV (sometimes referred to as Connected TV or Hybrid TV ) devices are also being released by Samsung , Panasonic and Sony , although these base their work on many other programming languages. XHTML While HTML, prior to HTML5 ,

1566-512: The Working Group issued a formal Note advising that it should not be transmitted with the HTML media type. With limited browser support for the alternate application/xhtml+xml media type, XHTML 1.1 proved unable to gain widespread use. In January 2009 a second edition of the document ( XHTML Media Types – Second Edition ) was issued, relaxing this restriction and allowing XHTML 1.1 to be served as text/html . The second edition of XHTML 1.1

1620-500: The XHTML2 WG, and closed the WG in December 2010, this means that XHTML 1.2 proposal would not eventuate. Between August 2002 and July 2006, the W3C released eight Working Drafts of XHTML 2.0, a new version of XHTML able to make a clean break from the past by discarding the requirement of backward compatibility. This lack of compatibility with XHTML 1.x and HTML 4 caused some early controversy in

1674-427: The addition of ruby annotation elements ( ruby , rbc , rtc , rb , rt and rp ) to better support East-Asian languages. Other changes include the removal of the name attribute from the a and map elements, and (in the first edition of the language) the removal of the lang attribute in favor of xml:lang . Although XHTML 1.1 is largely compatible with XHTML 1.0 and HTML 4, in August 2002

CE-HTML - Misplaced Pages Continue

1728-411: The beginning of an XHTML document in the XML declaration when the document is served using the application/xhtml+xml MIME type. (If an XML document lacks encoding specification, an XML parser assumes that the encoding is UTF-8 or UTF-16 , unless the encoding has already been determined by a higher protocol.) For example: The declaration may be optionally omitted because it declares its encoding

1782-403: The default encoding. However, if the document instead makes use of XML 1.1 or another character encoding, a declaration is necessary. Internet Explorer prior to version 7 enters quirks mode , if it encounters an XML declaration in a document served as text/html . Web Hypertext Application Technology Working Group The Web Hypertext Application Technology Working Group ( WHATWG )

1836-608: The document with a natural language : In order to validate an XHTML document, a Document Type Declaration , or DOCTYPE , may be used. A DOCTYPE declares to the browser the Document Type Definition (DTD) to which the document conforms. A Document Type Declaration should be placed before the root element . The system identifier part of the DOCTYPE, which in these examples is the URL that begins with http:// , need only point to

1890-456: The draft into a standard. Instead, XHTML 2.0 and its related documents were released as W3C Notes in 2010. New features to have been introduced by XHTML 2.0 included: HTML5 grew independently of the W3C, through a loose group of browser manufacturers and other interested parties calling themselves the WHATWG , or Web Hypertext Application Technology Working Group. The key motive of the group

1944-404: The editor of the specifications to ensure correct implementation. The WHATWG was formed in response to the slow development of World Wide Web Consortium (W3C) Web standards and W3C's decision to abandon HTML in favor of XML -based technologies. The WHATWG mailing list was announced on 4 June 2004, two days after the initiatives of a joint Opera–Mozilla position paper had been voted down by

1998-423: The existing HTML form elements and events model. It adds many new elements not found in XHTML 1.x, however, such as section and aside tags. The XHTML5 language, like HTML5, uses a DOCTYPE declaration without a DTD. Furthermore, the specification deprecates earlier XHTML DTDs by asking the browsers to replace them with one containing only entity definitions for named characters during parsing. XHTML+RDFa

2052-553: The following abstract modules: Base, Basic Forms, Basic Tables, Image, Link, Metainformation, Object, Style Sheet, and Target. XHTML Basic 1.1 replaces the Basic Forms Module with the Forms Module and adds the Intrinsic Events, Presentation, and Scripting modules. It also supports additional tags and attributes from other modules. This version became a W3C recommendation on 29 July 2008. The current version of XHTML Basic

2106-446: The language. There are various differences between XHTML and HTML. The Document Object Model (DOM) is a tree structure that represents the page internally in applications, and XHTML and HTML are two different ways of representing that in markup. Both are less expressive than the DOM – for example, "--" may be placed in comments in the DOM, but cannot be represented in a comment in either XHTML or HTML – and generally, XHTML's XML syntax

2160-409: The markup. First, there are some differences in syntax: In addition to the syntactical differences, there are some behavioral differences, mostly arising from the underlying differences in serialization. For example: The similarities between HTML 4.01 and XHTML 1.0 led many websites and content management systems to adopt the initial W3C XHTML 1.0 Recommendation. To aid authors in the transition,

2214-407: The markup; XHTML introduced stricter error handling. HTML 4 was ostensibly an application of Standard Generalized Markup Language (SGML); however the specification for SGML was complex, and neither web browsers nor the HTML 4 Recommendation were fully conformant to it. The XML standard, approved in 1998, provided a simpler data format closer in simplicity to HTML 4. By shifting to an XML format, it

CE-HTML - Misplaced Pages Continue

2268-471: The new HTML working group of the W3C resolved to do that. An Internet Explorer platform architect from Microsoft was invited but did not join, citing the lack of a patent policy to ensure all specifications can be implemented on a royalty-free basis. Since then, the W3C and the WHATWG had been developing HTML independently, at times causing specifications to diverge. In 2017, the WHATWG established an intellectual property rights agreement that includes

2322-449: The production of invalid XHTML documents by some Web authors and the lack of support for XHTML built into Internet Explorer 6 . They went on to describe the benefits of XML-based Web documents (i.e. XHTML) regarding searching, indexing, and parsing as well as future-proofing the Web itself. In October 2006, HTML inventor and W3C chair Tim Berners-Lee , introducing a major W3C effort to develop

2376-680: The same modules the W3C used in XHTML Basic 1.0—except for the Target Module. Starting with this foundation, the WAP Forum replaced the Basic Forms Module with a partial implementation of the Forms Module, added partial support for the Legacy and Presentation modules, and added full support for the Style Attribute Module. In 2002, the WAP Forum has subsumed into the Open Mobile Alliance (OMA), which continued to develop XHTML Mobile Profile as

2430-559: The same time updating the HTML specifications to address issues raised in the past few years." Ian Hickson , editor of the HTML5 specification criticizing the improper use of XHTML in 2002, is a member of the group developing this specification and is listed as one of the co-editors of the current working draft. Simon Pieters researched the XML-compliance of mobile browsers and concluded "the claim that XHTML would be needed for mobile devices

2484-475: The two serializations, the W3C suggests that most authors use the HTML syntax, rather than the XHTML syntax. The W3C recommendations of both XHTML 1.0 and XHTML 1.1 were retired on 27 March 2018, along with HTML 4.0, HTML 4.01, and HTML5. XHTML was developed to make HTML more extensible and increase interoperability with other data formats. In addition, browsers were forgiving of errors in HTML, and most websites were displayed despite technical errors in

2538-533: The web developer community. Some parts of the language (such as the role and RDFa attributes) were subsequently split out of the specification and worked on as separate modules, partially to help make the transition from XHTML 1.x to XHTML 2.0 smoother. The ninth draft of XHTML 2.0 was expected to appear in 2009, but on 2 July 2009, the W3C decided to let the XHTML2 Working Group charter expire by that year's end, effectively halting any further development of

2592-445: Was created, it would include WAI-ARIA and role attributes to better support accessible web applications, and improved Semantic Web support through RDFa . The inputmode attribute from XHTML Basic 1.1, along with the target attribute (for specifying frame targets) might also be present. The XHTML2 WG had not been chartered to carry out the development of XHTML1.2. Since the W3C announced that it does not intend to recharter

2646-446: Was defined as an application of Standard Generalized Markup Language (SGML), a flexible markup language framework, XHTML is an application of XML , a more restrictive subset of SGML. XHTML documents are well-formed and may therefore be parsed using standard XML parsers, unlike HTML, which requires a lenient HTML-specific parser. XHTML 1.0 became a World Wide Web Consortium (W3C) recommendation on 26 January 2000. XHTML 1.1 became

2700-513: Was eventually standardized on. The namespace URI http://whattf.org/datatype-draft remains in use for the HTML validator's data type library . On 28 May 2019, the W3C announced that WHATWG would be the sole publisher of the HTML and DOM standards. The W3C and WHATWG had been publishing competing standards since 2012. While the W3C standard was identical to the WHATWG in 2007 the standards have since progressively diverged due to different design decisions. The WHATWG "Living Standard" had been

2754-500: Was hoped HTML would become compatible with common XML tools; servers and proxies would be able to transform content, as necessary, for constrained devices such as mobile phones. By using namespaces , XHTML documents could provide extensibility by including fragments from other XML-based languages such as Scalable Vector Graphics and MathML . Finally, the renewed work would provide an opportunity to divide HTML into reusable components ( XHTML Modularization ) and clean up untidy parts of

SECTION 50

#1732854786125

2808-411: Was issued on 23 November 2010, which addresses various errata and adds an XML Schema implementation not included in the original specification. (It was first released briefly on 7 May 2009 as a "Proposed Edited Recommendation" before being rescinded on 19 May due to unresolved issues.) Since information appliances may lack the system resources to implement all XHTML abstract modules, the W3C defined

2862-578: Was superseded by XHTML Modularization 1.1 , which adds an XML Schema implementation. It was superseded by a second edition in July 2010. XHTML 1.1 evolved out of the work surrounding the initial Modularization of XHTML specification. The W3C released the first draft in September 1999; the Recommendation status was reached in May 2001. The modules combined within XHTML 1.1 effectively recreate XHTML 1.0 Strict, with

2916-403: Was to create a platform for dynamic web applications; they considered XHTML 2.0 to be too document-centric, and not suitable for the creation of internet forum sites or online shops. HTML5 has both a regular text/html serialization and an XML serialization, which is also known as XHTML5 . The language is more compatible with HTML 4 and XHTML 1.x than XHTML 2.0, due to the decision to keep

#124875