XHTMLBasic is an XML-based structured markup language primarily used for simple (mainly handheld) user agents, typically mobile devices.
XHTMLBasic is a subset of XHTML, including a minimal set of XHTML modules for document structure, images, forms, basic tables, and object support.
One large advantage XHTMLBasic has over WML and C-HTML is that XHTMLBasic pages can be rendered differently in web browsers and on handhelds, without the need for two different versions of the same page.
The system identifier, which in these examples is the URL that begins with "http", 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).
The need for a more strict version of HTML was felt primarily because World Wide Web content now needs to be delivered to many devices (like mobile devices) apart from traditional computers, where extra resources cannot be devoted to support the additional complexity of HTML syntax.
eXtensible HyperText Markup Language, or XHTML, is a markup language that has the same expressive possibilities as HTML, but a stricter syntax.
Basic forms are important for managing input and basic tables—in this case not for design or layout, but for their original intent: tabular data formatting.
So, with XHTMLBasic, I could have body markup that's limited to paragraph markup like Example 1(a); paragraphs, headers, and lists as in Example 1(b); or a more complex sample using a basic table as in Example 1(c)).
XHTML modularization is the first step toward giving us the flexibility—and extensibility—we need to author documents for multiple devices.
With respect to XHTML Modularization [XHTMLMOD] and the existence of XHTML based languages (referred to as XHTML family members) that are not XHTML 1.0 conformant languages, it is possible that 'application/xhtml+xml' may be used to describe some of these documents.
Work continues in the Modularization of XHTML Recommendation [XHTMLM12N], the decomposition of XHTML 1.0 into modules that can be used to compose new XHTML based languages, plus a framework for supporting this composition.
In addition, because of the extensibility features for XHTML as provided by XHTML Modularization, it is possible that 'application/xhtml+xml' may describe content that has security implications beyond those described here.
The goal of XHTMLBasic is to serve as a common language supported by various kinds of user agents.
XHTML Family document types are all XML-based, and ultimately are designed to work in conjunction with XML-based user agents.
The XHTMLBasicdocument type includes the minimal set of modules required to be an XHTML Host Language document type, and in addition it includes images, forms, basic tables, and object support.
The XHTMLBasic specification is the result of significant collaborative efforts of the W3C HTML Working Group, including participants from AOL/Netscape; CWI; Ericsson; IBM; Intel; Matsushita Electric Industrial Co., Ltd.; Microsoft; Mozquito Technologies; Openwave Systems Inc.; Philips Electronics; Quark Inc.; and Sun Microsystems.
In another W3C specification entitled "Modularization of XHTML", W3C's HTML Working Group describes a mechanism that allows authors to mix and match content from well-defined subsets of XHTML 1.0 elements and attributes.
Today, content developers interested in making XHTMLBasicdocuments can create them with W3C's own browser/editor, Amaya.
Currently, I'm serving either HTML/XHTML or XHTMLBasic using content negotiation based on the user agent's Accept header.
However, luckily enough, it is lenient in its error handling and just interprets as a weird variant of , meaning that in practice, XHTML pages look fine in IE6 - maybe the only problem with IE6 not understanding XHTML is the much talked about text/html mime issue.
And these browsers are advancing so fast that the need for WAP has virtually disappeared, and a similar thing has happened to XHTMLBasic.
The lack of support for proper XHTML, or even XHTMLBasic is to be lameted but is not worthy of fretting over too much.
If you had your files stored at XML (although XHTML is nearly as sufficient for this purpose) you could build your own translator mechanism or make use of XSL(T) to transform the document as necessary for the end user.
Thus you are forced to reformat your code into a less syntatically pleasing file for them.
For sites with more than one page, and where one of those pages is the main ("home") page, you should add links to the home page in both the header and body for ease of navigation.
XHTMLBasic is built on the general markup language
The site project file manages links and site assets, lets you use site diagramming to design the structure of your site, and save pages as templates and stationery to increase your consistency and work efficiently.
You'll need to configure the Objects palette so that you can drag only valid XHTML-Basic elements to your page.
Follow these basic steps and guidelines to develop your site.
Specifically, the W3C combined its XHTML 1.0 Recommendation, which was originally published in January with aspects of another specification entitled "Modularization of XHTML" to create XHTMLBasic as a markup language that works better on mobile Web devices, Jacobs said.
The group also used input from the WAP Forum, which is working on its Version 2.0 of Wireless Application Protocol, W3C said.
"XHTML 1.0 is based on HTML 4, which is a rather big specification; about 400 pages.
If you have the basics of an XML format in mind, but know that you will not be able to get everyone at the table to agree to every detail of the schema, consider Schematron abstract patterns.
But the Basic Table module of XHTML 1.1 uses a different vocabulary for tables than DocBook.
Investigate XHTML 1.1 and its modules defined in "Modularization of XHTML" -- section 5.6.1 is the "Basic Tables Module." Note that for actual use, the author suggests the "Tables Module", which might be better named and defines a table model more suited for accessibility.
The Library has standardized on XHTML 1.0 Transitional, a version of XHTML that works well in both old and new browsers, and that accommodates the needs of older browsers (such as Netscape Navigator 4 and Internet Explorer 4) that are used by a significant portion of the NYPL audience.
The declaration above should be typed (or cut and pasted) into the very top of every XHTMLdocument, before any other code or markup.
But the W3C currently recommends using XHTML instead.
XHTMLBasic is derived from XHTML 1.1 using the modularization mechanism described in the draft Modularization of XHTML.
XHTMLBasic looks like an attempt to bring Wireless Markup Language (WML) into the W3C's HTML development process, with the apparent consent of WML's creators, the WAP Forum.
The W3C, using input from the Wireless Application Protocol (WAP) Forum and its own Mobile Access Interest Group released a draft of XHTML aimed at users of smaller devices - like cell phones, PDAs, and other small appliances.
XHTMLBasic provides a subset of XHTML intended for use with small information appliances - cell phones, PDAs, and other systems without full-fledged HTML/XHTML browsers.
Based on that review, the W3C HTML Working Group believes that the definition of modules used in XHTMLBasic is stable, and the Working Group does not expect to make changes to 'Modularization of XHTML' that would be incompatible with XHTMLBasic.
XHTML An abbreviation for eXtensible HyperText Markup Language, an application of XML which uses a DTD to produce a reformulation of HTML in XML terms so that an XML structure can be used within a document otherwise looking like HTML.
Several depths of XHTML can be envoked by the DTD statement, including STRICT where XML patches can be used in the ordinary way and TRANSITIONAL where an XML namespace must be declared at the beginning of an XML coding patch.
It does not support such HTML and XHTML features such as frames, imagemaps, objects, and scripting.
> From: Jonathan Borden [mailto:jborden@mediaone.net] > How should this be resolved: > > 1) don't use XHTMLBasic (or any XHTML modularization) > 2) require all documents to be prefixed even those that don't > have XHTML > content.
But educating Web authors and application developers about these standards, and keeping them honest about their code once they implement them, is another task altogether, and the idea behind the proposed initiative.
While the W3C already offers tools that let authors check the validity of their XHTML or XML code, the consortium doesn't exert much authority when it comes to the "W3C compliant" tags that appear on many Web pages.
The W3C has issued numerous standards, or versions of standards, tailored for the mobile Web.
] > How should this be resolved: > > 1) don't use XHTMLBasic (or any XHTML modularization) > 2) require all documents to be prefixed even those that don't > have XHTML > content.
The current releases, Amaya 8.8.1 (old User Interface) and Amaya 9.2.1 (new User Interface), supports HTML 4.01, XHTML 1.0, XHTMLBasic, XHTML 1.1, HTTP 1.1, MathML 2.0, many CSS 2 features, and includes SVG support (transformation, transparency, and SMIL animation on OpenGL platforms).
Since that time it was extended to support XML and an increasing number of XML applications such as the XHTML family, MathML, and SVG.
It allows all those vocabularies to be edited simultaneously in compound documents.
If it does, then I would think a client that supports XHTML should support forms anyway, even if jep-04 already exists.
I'm not sure any of the clients that support XHTML (JIM, > Jabber Messenger, etc..) will support embedded HTML forms inside of the > XHTML msg.
On Wednesday 08 January 2003 06:47 am, Peter Millard wrote: > Aaron McBride wrote: > > Are there any known jabber clients that fully support XHTMLBasic > > (including support for the form element)?
A WAP browser that supports WML 1.2.1, cHTML, and XHTMLbasic standards.
It provides access to numerous kinds of data resources, such as Microsoft Exchange Server via Microsoft Mobile Information Server 2002, Lotus Notes via Domino Everyplace, or any other enterprise application you may want to enable for mobile use using Oracle9iAS Wireless or the Microsoft Mobile Internet Toolkit.
