XHTML [SEP] based on
[{"answer": "XML", "provenance": [{"wikipedia_id": "18984580", "title": "XHTML", "start_paragraph_id": 1, "start_character": 0, "end_paragraph_id": 1, "end_character": 90, "bleu_score": 1.0, "meta": {}, "section": "Section::::Abstract."}]}]
XHTML Basic


XHTML Basic is an XML-based structured markup language primarily used for simple (mainly "handheld") user agents, typically mobile devices. XHTML Basic is a subset of XHTML 1.1, defined using XHTML Modularization including a reduced set of modules for document structure, images, forms, basic tables, and object support. XHTML Basic is suitable for mobile phones, PDAs, pagers, and settop boxes. It will replace WML and C-HTML as more compliant user agents are developed. One large advantage XHTML Basic has over
3944413
HTML


transitional (loose) versus frameset on the other axis. One difference in the latest HTML specifications lies in the distinction between the SGML-based specification and the XML-based specification. The XML-based specification is usually called XHTML to distinguish it clearly from the more traditional definition. However, the root element name continues to be "html" even in the XHTML-specified HTML. The W3C intended XHTML 1.0 to be identical to HTML 4.01 except where limitations of XML over the more complex SGML require workarounds. Because XHTML
12884046
XHTML+RDFa


became a World Wide Web Consortium (W3C) Recommendation on 14 October 2008. The current recommendation is RDFa+XHTML version 1.1, which became a W3C Recommendation on 7 June 2012 and was updated with a ”Second Edition” on 22 August 2013 and a ”Third Edition” on 17 March 2015. Version 1.1 is based on XHTML™ 1.1 - Module-based XHTML - Second Edition. Version 1.0 was based on the first edition. Conventional Web documents contain large amounts of structured data that can be rendered in web browsers. This
9173814
XHTML


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: 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
683737
XHTML


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 was created, it would include WAI-ARIA and codice_31 attributes to better
683750
HTML


XHTML 1.1 through a set of modular extensions to the base XHTML 1.1 specification. Likewise, someone looking for the loose (transitional) or frameset specifications will find similar extended XHTML 1.1 support (much of it is contained in the legacy or frame modules). The modularization also allows for separate features to develop on their own timetable. So for example, XHTML 1.1 will allow quicker migration to emerging XML standards such as MathML (a presentational and semantic math language based on XML) and XForms—a new highly advanced web-
12884055
XHTML


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 the W3C Markup Validation Service. In practice, many web development programs provide code validation based on the W3C standards. The root element of an XHTML document must be codice_57, and must contain an codice_58 attribute to associate it with the XHTML namespace. The namespace URI for XHTML is codice_59.
683756
Europass


-source software weblogs WordPress and Dotclear. The plugin allow users of those blogging services to store a Europass CV in all European official languages and export it into the following formats: PDF, ODT, HTML, XHTML, HR-XML. The plugin is compliant with HR-XML SEP specifications. Last version of the plugin has been released in January 2008. The Europass framework was established by Decision 2241/2004/EC of the European Parliament and of the Council of 15 December 2004 on a single Community framework for the transparency of
7751791
XHTML+Voice


best done from the server by checking the HTTP header "Accept" for the MIME type application/xhtml+voice+xml. Here is some PHP code that returns "true" if and only if the requesting browser supports XHTML+Voice: Speech Application Language Tags(SALT) is a very similar format developed by Microsoft in 2001 to compete with VoiceXML and XHTML+Voice. SALT also provides users with multimodal support including grammar based recognition and speech synthesized output. The main differences are in the providers of support. Many different companies support VoiceXML and XHTML+Voice by providing various development
22208701
XHTML+SMIL


XHTML+SMIL is a W3C Note that describes an integration of SMIL semantics with XHTML and CSS. It is based generally upon the HTML+TIME submission. The language is also known as HTML+SMIL. The XHTML+SMIL language profile shares many modules with the standard SMIL language profiles, including the core modules of timing, media objects, linking, animation, transitions and content control. Where the other SMIL profiles use a language-specific layout model, XHTML+SMIL leverages the HTML flow layout and CSS positioning model familiar to many web authors. The semantics of integrating
7985967
XHTML


work on advancing ordinary HTML not based on XHTML. The WHATWG eventually began working on a standard that supported both XML and non-XML serializations, HTML5, in parallel to W3C standards such as XHTML 2. 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 Working Group's charter to expire, acknowledging that HTML5 would be the sole next-generation HTML standard, including both XML and non
683729
HTML


form technology to replace the existing HTML forms. In summary, the HTML 4 specification primarily reined in all the various HTML implementations into a single clearly written specification based on SGML. XHTML 1.0, ported this specification, as is, to the new XML defined specification. Next, XHTML 1.1 takes advantage of the extensible nature of XML and modularizes the whole specification. XHTML 2.0 was intended to be the first step in adding new features to the specification in a standards-body-based approach. The HTML Living Standard, which
12884056
XHTML


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 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 was
683748
Confluence (software)


, which allows advanced users the ability to edit the underlying XHTML-based document source. However, although the new source markup is XHTML-based, it is not XHTML compliant. Additionally, wiki markup can be typed into the editor and Confluence's autocomplete and auto-format function converts the wiki markup to the new format. After the real-time conversion, content can not be edited as wiki markup again. Confluence Cloud data is encrypted in transit and at rest. Two pages cannot have the same title within
4887589
Document type declaration


are also Strict, Transitional and Frameset. XHTML Strict DTD. No deprecated tags are supported and the code must be written correctly according to XML Specification. XHTML Transitional DTD is like the XHTML Strict DTD, but deprecated tags are allowed. XHTML Frameset DTD is the only XHTML DTD that supports Frameset. The DTD is below. XHTML 1.1 is the most current finalized revision of XHTML, introducing support for XHTML Modularization. XHTML 1.1 has the stringency of XHTML 1.0 Strict. XHTML Basic 1.0 XHTML Basic 1.1 HTML5 uses a codice_6 declaration
15615114
RDFa


in the form of a W3C note entitled "XHTML and RDF", which was then presented to the Semantic Web Interest Group at the W3C's 2004 Technical Plenary. Later that year the work became part of the sixth public Working Draft of XHTML 2.0. Although it is generally assumed that RDFa was originally intended only for XHTML 2, in fact the purpose of RDFa was always to provide a way to add a metadata to "any" XML-based language. Indeed, one of the earliest documents bearing the "RDF
5022214
XHTML


the claim that XHTML would be needed for mobile devices 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 a W3C Recommendation. There are three formal DTDs
683740
Apache Wicket


Swing components react to mouse and keystroke events. Wicket is categorized as a component-based framework. Wicket uses plain XHTML for templating (which enforces a clear separation of presentation and business logic and allows templates to be edited with conventional WYSIWYG design tools). Each component is bound to a named element in the XHTML and becomes responsible for rendering that element in the final output. The "page" is simply the top-level containing component and is paired with exactly one XHTML template. Using a special tag, a group
12589588
XHTML Mobile Profile


XHTML Mobile Profile (XHTML MP) is a hypertextual computer language standard designed specifically for mobile phones and other resource-constrained devices. It is an XHTML document type defined by the Open Mobile Alliance. XHTML-MP is derived from XHTML Basic 1.0 by adding XHTML Modules, with later versions of the standard adding more modules. However, for certain modules, XHTML-MP does not mandate a complete implementation so an XHTML-MP browser may not be fully conforming on all modules. The XHTML MP 1.2 DTD is the current
13349784
XOXO (microformat)


XOXO (eXtensible Open XHTML Outlines) is an XML microformat for outlines built on top of XHTML. Developed by several authors as an attempt to reuse XHTML building blocks instead of inventing unnecessary new XML elements/attributes, XOXO is based on existing conventions for publishing outlines, lists, and blogrolls on the Web. The XOXO specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data. E.g. the more semantic version of the S5 presentation
12916090
Flying Saucer (library)


Flying Saucer (also called XHTML renderer) is a pure Java library for rendering XML, XHTML, and CSS 2.1 content. It is intended for embedding web-based user interfaces into Java applications, but cannot be used as a general purpose web browser since it does not support HTML. Thanks to its capability to save rendered XHTML to PDF (using iText), it is often used as a server side library to generate PDF documents. It has extended support for print-related things like pagination and page headers and
18407212
XHTML


, it implements 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 is 1.1 Second Edition (23 November 2010), in which the language is re-
683746
XHTML


implemented in the W3C's XML Schema language. This version also supports the codice_26 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) 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
683747
XHTML+Voice


XHTML+Voice (commonly X+V) is an XML language for describing multimodal user interfaces. The two essential modalities are visual and auditory. Visual interaction is defined like most current web pages via XHTML. Auditory components are defined by a subset of Voice XML. Interfacing the voice and visual components of X+V documents is accomplished through a combination of ECMAScript, JavaScript, and XML Events. Voice input or speech recognition is based on grammars that define the set of possible input text. In contrast to a probabilistic approach employed by popular software packages such
22208698
XHTML


XHTML Basic 1.0. In October 2008 "Modularization of XHTML" was superseded by "XHTML Modularization 1.1", which adds an XML Schema implementation. It was itself 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 a first draft in September 1999; Recommendation status was reached in May 2001. The modules combined within XHTML 1.1 effectively recreate XHTML 1.0 Strict, with the addition of ruby annotation elements (codice_17, codice_18, codice_19
683742
XHTML


Since information appliances may lack the system resources to implement all XHTML abstract modules, the W3C defined 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 on 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)
683745
Markup language


uses. XML is now widely used for communicating data between applications, for serializing program data, and many other uses as well as documents. Since January 2000, all W3C Recommendations for HTML have been based on XML rather than SGML, using the abbreviation XHTML (Extensible HyperText Markup Language). The language specification requires that XHTML Web documents must be "well-formed" XML documents. This allows for more rigorous and robust documents while using tags familiar from HTML. One of the most noticeable differences between HTML and XHTML is
19256639
XHTML


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
683741
XHTML Modularization


XHTML modularization is a methodology for producing modularized markup languages in a number of different schema languages (currently DTDs, XML Schema and Relax NG) so that the modules can easily be plugged together to create markup languages. Although it was originally designed to help manage the development of various XHTML Profiles, such as XHTML 1.1, XHTML Basic for mobile devices, and XHTML Print for sending to printers, the methodology is independent of XHTML, and has been used for the definition of other markup languages as well, such as SVG and
3944417
Comparison of layout engines (XHTML)


The following tables compare XHTML compatibility and support for a number of layout engines. Only XHTML 1.1 is considered. XHTML 1.1 is necessarily XHTML 1.0 Strict with more elements and attributes deprecated. XHTML 2.0 was a working draft with no layout engine support, but work on it was abandoned in 2009 in favor of work on HTML5 and XHTML5. XHTML 1.0 and HTML 4 (both served with codice_1) are covered in comparison of layout engines (HTML). The comparison of XML capabilities are covered in comparison of layout engines (XML
21813108
XHTML+RDFa


straightforward to use CSS selectors to style the code. The combination of XHTML 1.1 and RDFa modules is claimed to be an example markup language. The Document Type Definition (DTD) is published at the W3C website. According to the document type declaration, the identifiers of an XHTML+RDFa document should look like the following: An example XHTML+RDFa document: The RDFa metadata is embedded as an XHTML attribute of the document element, generally the XHTML tag. The annotation syntax provided by RDFa can be used to express RDF statements in XHTML documents
9173817
XHTML+RDFa


XHTML+RDFa (Extensible Hypertext Markup Language + Resource Description Framework in attributes) 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. XHTML+RDFa is one of the techniques used to develop Semantic Web content by embedding rich semantic markup. Version 1.1 of the language is a superset of XHTML 1.1, integrating the attributes according to RDFa Core 1.1. In other words, it is an RDFa support through XHTML Modularization. RDFa in XHTML version 1.0
9173813
Thymeleaf


Thymeleaf is a Java XML/XHTML/HTML5 template engine that can work both in web (servlet-based) and non-web environments. It is better suited for serving XHTML/HTML5 at the view layer of MVC-based web applications, but it can process any XML file even in offline environments. It provides full Spring Framework integration. In web applications Thymeleaf aims to be a complete substitute for JavaServer Pages (JSP), and implements the concept of "Natural Templates": template files that can be directly
20332868
BlueGriffon


BlueGriffon is a WYSIWYG content editor for the World Wide Web. It is based on the discontinued Nvu editor, which in turn is based on the Composer component of the Mozilla Application Suite. Powered by Gecko, the rendering engine of Firefox, it can edit Web pages in conformance to Web Standards. It runs on Microsoft Windows, macOS and Linux. BlueGriffon complies with the W3C's web standards. It can create and edit pages in accordance to HTML 4, XHTML 1.1, HTML 5 and XHTML 5. It supports CSS
2344022
ZK (framework)


ZK is an open-source Ajax Web application framework, written in Java, that enables creation of graphical user interfaces for Web applications with little required programming knowledge. The core of ZK consists of an Ajax-based event-driven mechanism, over 123 XUL and 83 XHTML-based components, and a mark-up language for designing user interfaces. Programmers design their application pages in feature-rich XUL/XHTML components, and manipulate them upon events triggered by end user's activity. It is similar to the programming model
19242172
Ruby character


and has been superseded by the inclusion of Ruby support in HTML5. For more information visit w3 ruby markup reference. In 2001, the W3C published the Ruby Annotation specification for supplementing XHTML with ruby markup. Ruby markup is not a standard part of HTML 4.01 or any of the XHTML 1.0 specifications (XHTML-1.0-Strict, XHTML-1.0-Transitional, and XHTML-1.0-Frameset), but was incorporated into the XHTML 1.1 specification, and is expected to be a core part of HTML5 once the specification becomes finalised by the W3C. Support for ruby markup in web browsers is
20951094
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 the web developer community. Some parts of the language (such as the codice_31 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. A ninth draft of XHTML 2.0 was expected to appear in 2009, but
683752
Speech Application Language Tags


Speech Application Language Tags (SALT) is an XML-based markup language that is used in HTML and XHTML pages to add voice recognition capabilities to web-based applications. Speech Application Language Tags enables multimodal and telephony-enabled access to information, applications, and Web services from PCs, telephones, tablet PCs, and wireless personal digital assistants (PDAs). The Speech Application Language Tags extend existing mark-up languages such as HTML, XHTML, and XML. Multimodal access will enable users to interact with an application in
2187641
XHTML


", need only point to 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 the beginning of an XHTML document in the
683758
XML namespace


codice_2, the value of which must be a valid namespace name. For example, the following declaration maps the "xhtml:" prefix to the XHTML namespace: Any element or attribute whose name starts with the prefix "xhtml:" is considered to be in the XHTML namespace, if it or an ancestor has the above namespace declaration. It is also possible to declare a default namespace. For example: In this case, any element without a namespace prefix is considered to be in the XHTML namespace, if it or
13512795
XHTML


would provide an opportunity to divide HTML into reusable components (XHTML Modularization) and clean up untidy parts of 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
683732
XHTML Mobile Profile


recommendation, finalized in March 2008. "XHTML Basic 1.1" became a W3C Recommendation in July 2008, superseding XHTML-MP 1.2. To validate as XHTML-MP, a document must contain a proper Document Type Declaration, (DTD) or DOCTYPE, depending on the version of specification followed Note that a series of revisions have been issued to correct technical errors in the above DTDs, and the DTD format is more complex and less widely supported than that of standard HTML. The MIME type for XHTML Mobile Profile is "
13349785
Wireless Application Protocol


additional information to each request. This would be configured by the operator and could include telephone numbers, location, billing information, and handset information. Mobile devices process XHTML Mobile Profile (XHTML MP), the markup language defined in WAP 2.0. It is a subset of XHTML and a superset of XHTML Basic. A version of Cascading Style Sheets (CSS) called WAP CSS is supported by XHTML MP. Multimedia Messaging Service (MMS) is a combination of WAP and SMS allowing for sending of picture messages. The WAP
16175460
XHTML


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 web sites and content management systems to adopt the initial W3C XHTML 1.0 Recommendation. To aid authors in the transition, 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 (codice_11
683734
XHTML


subsumed into the Open Mobile Alliance (OMA), which continued to develop XHTML Mobile Profile as 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 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
683749
XHTML


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 codice_11 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 the existing HTML form elements and events model. It adds many new elements not found in XHTML 1.x, however, such as codice_55
683754
HTML


coding in HTML or XHTML it may just be best to always include the optional tags within an HTML document rather than remembering which tags can be omitted. A well-formed XHTML document adheres to all the syntax requirements of XML. A valid document adheres to the content specification for XHTML, which describes the document structure. The W3C recommends several conventions to ensure an easy migration between HTML and XHTML (see HTML Compatibility Guidelines). The following steps can be applied to XHTML 1.0 documents only: By carefully following the W3C's
12884050
XHTML


and codice_56 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 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
683755
XHTML


an XML declaration in a document served as codice_11. XHTML 1.x documents are mostly backward compatible with HTML 4 user agents when the appropriate guidelines are followed. XHTML 1.1 is essentially compatible, although the elements for ruby annotation are not part of the HTML 4 specification and thus generally ignored by HTML 4 browsers. Later XHTML 1.x modules such as those for the codice_31 attribute, RDFa and WAI-ARIA degrade gracefully in a similar manner. XHTML 2.0 is significantly less compatible, although this can be mitigated to some degree through the use
683760
XHTML


" html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" /html Example 2. ?xml version="1.0" encoding="UTF-8"? !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" /html Notes: HTML5 and XHTML5 serializations are largely inter-compatible if adhering to the stricter XHTML5 syntax, but there are some cases in which XHTML will not work as valid HTML5 (e.g., processing instructions are deprecated in , are treated as comments, and close on the first "", whereas they
683762
Metadata


Dublin Core Metadata Element Set are endorsed in the following standards documents: Although not a standard, Microformat (also mentioned in the section metadata on the internet below) is a web-based approach to semantic markup which seeks to re-use existing HTML/XHTML tags to convey metadata. Microformat follows XHTML and HTML standards but is not a standard in itself. One advocate of microformats, Tantek Çelik, characterized a problem with alternative approaches: Metadata may be written into a digital photo file that will identify who owns it,
21235113
Quotation mark


" HTML includes a set of entities for curved quotes: codice_9 (left single), codice_10 (right single or apostrophe), codice_11 (low 9 single), codice_12 (left double), codice_13 (right double), and codice_14 (low 9 double). XML does not define these by default, but specifications based on it can do so, and XHTML does. In addition, while the HTML 4, XHTML and XML specifications allow specifying numeric character references in either hexadecimal or decimal, SGML and older versions
3056988
MathML


(support incomplete) can display Presentation MathML embedded in XHTML. Inline MathML is also supported in HTML5 files in the current versions of WebKit (Safari and JavaFX/WebView ), Gecko (Firefox). There is no need to specify namespaces like in the XHTML. Of the major web browsers, Gecko-based browsers (e.g., Firefox and Camino) have the most complete native support for MathML. While the WebKit layout engine has a development version of MathML, this feature is only available in version 5.1 and higher of
7082224
Mobile browser


, and wireless data connection called WAP. In Japan, DoCoMo defined the i-mode service based on i-mode HTML, which is an extension of Compact HTML (C-HTML), a simple subset of HTML. WAP 2.0 specifies XHTML Mobile Profile plus WAP CSS, subsets of the W3C's standard XHTML and CSS with minor mobile extensions. Newer mobile browsers are full-featured Web browsers capable of HTML, CSS, ECMAScript, as well as mobile technologies such as WML, i-mode HTML, or
5529694
XHTML


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 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
683731
Signal Transfer Point


A Signal Transfer Point (STP) is a router that relays SS7 messages between "signaling end-points" (SEPs) and other signaling transfer points (STPs). Typical SEPs include "service switching points" (SSPs) and "service control points" (SCPs). The STP is connected to adjacent SEPs and STPs via signaling links. Based on the address fields of the SS7 messages, the STP routes the messages to the appropriate outgoing signaling link. Edge STPs can also route based upon message body content using
21819466
Tag soup


specific HTML tags. CSS uses style rules to accomplish these tasks while leaving the markup cleaner and simpler. XHTML is a reformulation of the HTML language based on XML. XHTML was developed to address many of the problems associated with tag soup. XML allows parsers to separate the process of interpreting the document syntax and its structure. In HTML and SGML, a parser needed to know certain rules about elements during parsing, such as what elements could be contained within other elements and which elements implicitly close the previous element. This is
11919424
RDFa


RDFa (or Resource Description Framework in Attributes) is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The RDF data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents. The RDFa community runs a wiki website to host tools, examples, and tutorials. RDFa was first proposed by Mark Birbeck
5022213
XHTML


and XHTML5 are being actively developed. In the current XHTML 1.0 Recommendation document, as published and revised to August 2002, 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
683728
HTML


this is to include a space before closing the tag, as such: . To understand the subtle differences between HTML and XHTML, consider the transformation of a valid and well-formed XHTML 1.0 document that adheres to Appendix C (see below) into a valid HTML 4.01 document. To make this translation requires the following steps: Those are the main changes necessary to translate a document from XHTML 1.0 to HTML 4.01. To translate from HTML to XHTML would also require the addition of any omitted opening or closing tags. Whether
12884049
HTML


compatibility guidelines, a user agent should be able to interpret the document equally as HTML or XHTML. For documents that are XHTML 1.0 and have been made compatible in this way, the W3C permits them to be served either as HTML (with a codice_52 MIME type), or as XHTML (with an codice_57 or codice_58 MIME type). When delivered as XHTML, browsers should use an XML parser, which adheres strictly to the XML specifications for parsing the document's contents. HTML 4 defined three different versions of the language
12884051
XML namespace


as a string. For example, the document at http://www.w3.org/1999/xhtml itself does not contain any code. It simply describes the XHTML namespace to human readers. Using a URI (such as "http://www.w3.org/1999/xhtml") to identify a namespace, rather than a simple string (such as "xhtml"), reduces the probability of different namespaces using duplicate identifiers. Although the term "namespace URI" is widespread, the W3C Recommendation refers to it as the "namespace name". The specification is not entirely prescriptive about the precise rules for
13512791
RDFa


/A Syntax" name has the sub-title "A collection of attributes for layering RDF on XML languages". The document was written by Mark Birbeck and Steven Pemberton, and was made available for discussion on October 11, 2004. In April 2007 the XHTML 2 Working Group produced a module to support RDF annotation within the XHTML 1 family. As an example, it included an extended version of XHTML 1.1 dubbed XHTML+RDFa 1.0. Although described as not representing an intended direction in terms of a formal markup language from the
5022215
XHTML


eXtensible HyperText Markup Language (XHTML) is part of the family of XML markup languages. It mirrors or extends versions of the widely used HyperText Markup Language (HTML), the language in which Web pages are formulated. While HTML, prior to HTML5, 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
683726
XHTML


, codice_20, codice_21 and codice_22) to better support East-Asian languages. Other changes include removal of the codice_23 attribute from the codice_24 and codice_25 elements, and (in the first edition of the language) removal of the codice_26 attribute in favour of codice_27. Although XHTML 1.1 is largely compatible with XHTML 1.0 and HTML 4, in August 2002 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 codice_12 media type, XHTML 1.1 proved
683743
XHTML


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 codice_11. A second edition of XHTML 1.1 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.)
683744
Zope


making many changes that are not backwards compatible with Zope 2. As mentioned previously, Zope Page Templates are themselves XHTML documents, which means they can be viewed and edited using normal HTML editors or XHTML compliant tools (a big advantage compared to other template languages used for Web applications). Templates can also be checked for XHTML compliance so you can be fairly confident that they will automatically expand into proper XHTML. However, these page templates are not meant to be rendered as is. Instead they are marked up with additional elements
15780354
XHTML


HTML, which requires a lenient HTML-specific parser. XHTML 1.0 became a World Wide Web Consortium (W3C) recommendation on January 26, 2000. XHTML 1.1 became a W3C recommendation on May 31, 2001. The standard known as XHTML5 is being developed as an XML adaptation of the HTML5 specification. XHTML 1.0 is "a reformulation of the three HTML 4 document types as applications of XML 1.0". The World Wide Web Consortium (W3C) also continues to maintain the HTML 4.01 Recommendation, and the specifications for HTML5
683727
XHTML


-XML serializations. Of the two serializations, the W3C suggests that most authors use the HTML syntax, rather than the XHTML syntax. 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 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
683730
XHTML


) rather than the official Internet media type for XHTML (codice_12). When measuring the adoption of XHTML to that of regular HTML, therefore, it is important to distinguish whether it is media type usage or actual document contents that is 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 codice_12 content, a dialog box invites the user to save the content to disk instead. Both Internet Explorer 7
683735
XHTML


(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 is not widespread, most web developers avoid using XHTML that is not HTML-compatible, so advantages of XML such as namespaces, faster parsing and
683736
XHTML


of scripting. (This can be simple one-liners, such as the use of “codice_65” to register a new HTML element within Internet Explorer, or complete JavaScript frameworks, such as the FormFaces implementation of XForms.) The following are examples of XHTML 1.0 Strict, with both having the same visual output. The former one follows the HTML Compatibility Guidelines of the XHTML Media Types Note while the latter one breaks backward compatibility, but provides cleaner markup. Example 1. !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN
683761
XHTML


support accessible web applications, and improved Semantic Web support through RDFa. The codice_32 attribute from XHTML Basic 1.1, along with the codice_33 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 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
683751
United States hydrogen policy


programs. Each states energy office gets SEP funding and manages all SEP funded projects. For more information about the SEP, including project descriptions, visit the SEP website. Clean Ports USA is an incentive-based program designed to help reduce emissions by encouraging port authorities to redesign and replace older diesel engines with new technologies and cleaner fuels. The U.S. Environmental Protection Agency's National Clean Diesel Campaign offers funding to port authorities to help them overcome the obstacles that prevent the adoption of cleaner diesel technologies. Clean Construction USA promotes the reduction
8426000
XHTML+Voice


as Dragon Naturally Speaking, the grammar based approach provides the recognizer with important contextual information that significantly boosts recognition accuracy. The specific formats for grammars include JSGF. Voice output or speech synthesis can read any string at virtually any time. Pitch, volume, and other characteristics can be customized using CSS and Speech Synthesis Markup Language (SSML) however the Opera web browser doesn't currently support all these features. The previously recommended MIME type for any X+V document is application/xhtml+voice+xml which is what the Opera browser uses. Opera will
22208699
World Qualification Series (2009)


18 - Aug 23" 30th Anniversary of the Lacanau Pro and good conditions this year. Surf, concerts, events scheduled. Check out the video for a summary of the event http://vimeo.com/6994555 "Aug 25 - Aug 30" "Sep 01 - Sep 06" "Sep 01 - Sep 06" "Sep 04 - Sep 06" "Sep 09 - Sep 12" "Sep 10 - Sep 13" "Sep 08 - Sep 13" "Sep 15 - Sep 20" "Sep 16 - Sep 22" "Sep
1986943
List of 1982–83 NBA season transactions


1982 Oct 2, 1982 Oct 1, 1982 Sep 30, 1982 Sep 29, 1982 Sep 28, 1982 Sep 27, 1982 Sep 24, 1982 Sep 22, 1982 Sep 20, 1982 Sep 19, 1982 Sep 18, 1982 Sep 17, 1982 Sep 15, 1982 Sep 14, 1982 Sep 13, 1982 Sep 10, 1982 Sep 9, 1982 Sep 7, 1982 Sep 2, 1982 Sep 1, 1982 Aug 31, 1982 Aug 27, 1982 Aug 26, 1982 Aug 16, 1982 Aug 8,
557049
RDFa


defined in 2008 with the "RDFa in XHTML: Syntax and Processing" Recommendation. Its first application was to be a module of XHTML. The HTML applications remained, ""a collection of attributes and processing rules for extending XHTML to support RDF"" expanded to HTML5, are now expressed in a specialized standard, the "HTML+RDFa" (the last is ""HTML+RDFa 1.1 - Support for RDFa in HTML4 and HTML5""). The ""HTML+RDFa"" syntax of 2008 was also termed ""RDFa
5022218
Richard Mattern Montgomery


staff. Sep 1956-Aug 1959 In 1956 he was assigned as deputy commander of the 2d Air Force (SAC). Following this two-year tour, he became commander of the 3d Air Division at Guam, with responsibility for SAC Forces West of the 180th meridian. Sep 1952-Sep 1956 The assignment which did most to shape his subsequent career was that of chief of staff, Headquarters, Strategic Air Command, Offutt Air Force Base, Nebraska, in September 1952, a post he held until September 1956. As a principal staff
10835420
HTML


codice_142 elements, or optionally codice_63 with a codice_59. As this list demonstrates, the loose versions of the specification are maintained for legacy support. However, contrary to popular misconceptions, the move to XHTML does not imply a removal of this legacy support. Rather the X in XML stands for extensible and the W3C is modularizing the entire specification and opening it up to independent extensions. The primary achievement in the move from XHTML 1.0 to XHTML 1.1 is the modularization of the entire specification. The strict version of HTML is deployed in
12884054
HTML


and HTML are closely related, they are sometimes documented in parallel. In such circumstances, some authors conflate the two names as (X)HTML or X(HTML). Like HTML 4.01, XHTML 1.0 has three sub-specifications: strict, transitional and frameset. Aside from the different opening declarations for a document, the differences between an HTML 4.01 and XHTML 1.0 document—in each of the corresponding DTDs—are largely syntactic. The underlying syntax of HTML allows many shortcuts that XHTML does not, such as elements with optional opening or
12884047
HTML


closing tags, and even empty elements which must not have an end tag. By contrast, XHTML requires all elements to have an opening tag and a closing tag. XHTML, however, also introduces a new shortcut: an XHTML tag may be opened and closed within the same tag, by including a slash before the end of the tag like this: . The introduction of this shorthand, which is not used in the SGML declaration for HTML 4.01, may confuse earlier software unfamiliar with this new convention. A fix for
12884048
Unicode and HTML


all, of the characters jointly defined by Unicode and ISO/IEC 10646: the Universal Character Set (UCS). Like HTML documents, an XHTML document is a sequence of Unicode characters. However, an XHTML document is an XML document, which, while not having an explicit "document character" layer of abstraction, nevertheless relies upon a similar definition of permissible characters that cover most, but not all, of the Unicode/UCS character definitions. The sets used by HTML and XHTML/XML are slightly different,
13358460
SAML 2.0


a document containing an XHTML form: The value of the codice_22 parameter is the base64-encoding of a codice_17 element, which is transmitted to the identity provider via the browser. The SSO service at the identity provider validates the request and responds with a document containing another XHTML form: The value of the codice_23 parameter is the base64 encoding of a codice_15 element, which likewise is transmitted to the service provider via the browser. To automate the submission of the form, the following line of JavaScript may appear anywhere on the XHTML page:
17720386
XHTML Basic


WML and C-HTML is that XHTML Basic pages can be rendered differently in web browsers and on handhelds, without the need for two different versions of the same page. In 2006, the specification was revised to version 1.1. Six new features have been incorporated into the language in order to better serve the small-device community. To validate as XHTML Basic, a document must contain the following Document Type Declaration, or DOCTYPE: A complete valid and well-formed example is: Served with a MIME type of "
3944414
XHTML


HTML — and generally XHTML's XML syntax 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 standardised 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. First, there are some differences in syntax: In addition to
683733
XHTML


The example tag below additionally features an codice_27 attribute to identify the document with a natural language: html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" 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://
683757
HTML element


be displayed improperly. In 1998, XML (a simplified form of SGML) introduced mechanisms to allow anyone to develop their own elements and incorporate them in XHTML documents, for use with XML-aware user agents. Subsequently, HTML 4.01 was rewritten in an XML-compatible form, XHTML 1.0 ("eXtensible HTML"). The elements in each are identical, and in most cases valid XHTML 1.0 documents will be valid or nearly valid HTML 4.01 documents. This article mainly focuses on real HTML, unless noted otherwise;
893518
Access key


a mouse is not an option for them. Their research showed that most key stroke combinations did in fact present a conflict for one or more of these technologies, and their final recommendation was to avoid using accesskeys altogether. In XHTML 2, a revised web authoring language, the HTML Working Group of the World Wide Web Consortium deprecated the accesskey attribute in favor of the XHTML Role Access Module. However, XHTML 2 has been retired in favor of HTML5, which (as of August 2009) continues to permit accesskeys. For
9758160
Textile (markup language)


creation of a common specification across Textile implementations. Text marked-up with Textile converts into valid HTML when rendered in a web browser, and though it probably varies from one implementation type to another, an installation of Textile can be set for a Doctype Declaration of XHTML or HTML5, with XHTML being the default for backward compatibility. In the PHP implementation, for example, when using Textile's all-caps abbreviation syntax – codice_1 – the result will render as an codice_2 element in HTML5 and as an codice_3 element in XHTML
10766943
Global Multimedia Protocols Group


The Global Multimedia Protocols Group (GMPG) was founded in March 2003 by Tantek Çelik, Eric A. Meyer, and Matt Mullenweg. The group has developed methods to represent human relationships using XHTML called XHTML Friends Network (XFN) and XHTML Meta Data Profiles (XMDP), for use in weblogs. It is an informal organization who engages in experiments in metamemetics. It was first mentioned in 1992 by author Neal Stephenson in his novel "Snow Crash". GMPG was founded by Tantek Çelik, Eric Meyer, and Matthew Mullenweg
13222436
Vision Mobile Browser


Vision (formerly nWeb) was a mobile browser developed by Novarra Inc. that ran on Java Platform, Micro Edition. It was first released in 2002, and the final release was in 2009. Mobile phone users can access and use the same web sites on their wireless handsets that they visit using personal computers. Full web pages load in seconds due to compression and in-network processing of content by the server. Content Type Support: “Street” HTML, HTML 4.01, XHTML 1.0, XHTML Basic, XHTML MP,
20496299
XHTML+RDFa


while indexing. Yahoo indexes RDFa and microformats since 2008 and Google since 2009. The RDFa attribute specifications make it possible to describe structured data in any markup language. The RDFa markup in XHTML+RDFa reuses the markup code, thus eliminating the need for unnecessary duplications. XHTML+RDFa is not widely distributed yet, probably due to the lack of support in authoring tools and content management systems. However, there is good tendency. Drupal 7, for example, supports RDFa. Since the “a” in RDFa stands for attributes, it is
9173816
September 1941 lunar eclipse


A partial lunar eclipse took place on Friday, September 5, 1941. It was a shallow partial lunar eclipse, with less than 10% of the Moon covered in Earth's shadow. Aug 31, 1941 = Sunday Sep 1, 1941 = Monday Sep 2, 1941 = Tuesday Sep 3, 1941 = Wednesday Sep 4, 1941 = Thursday Sep 5, 1941 = Friday Sep 6, 1941 = Saturday Sep 7, 1941 = Sunday Sep 8, 1941 = Monday Sep 9, 1941 = Tuesday Sep 10, 1941
5363349
EPUB


are required to display at least a placeholder for characters that cannot be displayed fully. An example skeleton of an XHTML file for EPUB looks like this: ?xml version="1.0" encoding="UTF-8" ? !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" /html The OPF specification's purpose is to "...[define] the mechanism by which the various components of an OPS publication are tied together and provides additional structure and semantics to the electronic publication." This is accomplished
10252105
Document type declaration


only accept XHTML DTDs of certain FPIs and to prefer using internal logic over fetching external DTD files. It further specifies an "internal DTD" for XHTML which is merely a list of HTML entity names. Strict DTD does not allow presentational markup with the argument that Cascading Style Sheets should be used for that instead. This is how the Strict DTD looks: Transitional DTD allows some older PUBLIC and attributes that have been deprecated: If frames are used, the Frameset DTD must be used instead, like this: XHTML's DTDs
15615113
XHTML


on July 2, 2009, the W3C decided to let the XHTML2 Working Group charter expire by that year's end, effectively halting any further development of 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 initially 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
683753
19th Air Refueling Squadron


The 19th Air Refueling Squadron (19 ARS) is an inactive unit of the United States Air Force. At the time of its inactivation, it was based at Otis Air Force Base. On 19 Sep 1985 the 19th Air Refueling Squadron,(Medium), was consolidated with the 19th Ferrying Squadron, a unit that was last active 31 Mar 1944. This action was directed by Department of the Air Force Letter DAF/MPM 662q Attachment 2 (Inactive Units), 19 Sep 1985. The Consolidated Unit will retain the Designation of 19th
8077229
Tag soup


, XHTML combined with CSS allow authoring communities to easily extend the semantic vocabulary of documents. This accommodates the use of proprietary elements so long as those elements can be presented to the intended audience through complete style sheet definitions (including aural/speech and tactile styles). XHTML documents may be served on the web using the internet media type codice_2 or codice_3 Current Microsoft Internet Explorer versions (6, 7 and 8) do not display XHTML documents served as codice_2. IE9 beta releases appear to be compliant. See also the discussion of
11919428
Form-based authentication


often used, it strongly implies default employment of HTTP and HTML (or XHTML) as part of the technique. This particular technique is specifically discussed in the article HTTP+HTML form-based authentication. A defining characteristic of the general notion of form-based authentication, as it is commonly used, is that the credential prompting and subsequent credential conveyance is conducted out-of-band relative to the transfer protocol employed between the client and server. For example, in the case of HTTP+HTML form-based authentication, the authentication features
11949675