| Home : Web : HTML |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
HTML Listings
|
|
Total:
59 | Displaying: 11 - 20 | Pages: << 1 2 3 4 5 6 >> |
|
|
|
The SALT (Speech Application Language Tags) specification pairs speech with HTML, XHTML, and XML. The specification boasts a 70-member consortium of backers including industry heavyweights Microsoft, Cisco, and Intel. The group submitted SALT 1.0 to the W3C. SALT is not a W3C standard, though. SALT was submitted to the W3C\'s Voice Browser working group, which will consider it as a part of the next VoiceXML standard. This article will touch on the SALT/VoiceXML relationship again near the end.
Updated: 05/17/2005
|
|
|
When all is said and done, XHTML is one of the most important W3C specifications because, in principle, it affects the greatest number of users -- at least that\'s the theory. XHTML, like RDF, is still more often talked about and evangelized than it is actually used, but there are good reasons to think that it will eventually catch on. Which means that the continual evolution of XHTML is a key element of the future health of the Web as a means of intra-human exchange.
Updated: 05/17/2005
|
|
|
When the first public XHTML 2.0 Working Draft was released in early August, one of the most common reactions, at least in the XML developer community, was to wonder why the HTML Working Group (HWG) wasn\'t using XLink. XHTML 2.0\'s refusal to use XLink as its hypertext linking layer was seen as its chief defect. Perhaps, if it isn\'t suitable or appropriate for use in XHTML 2.0, XLink hasn\'t any future at all? As early as the Final Call for comments on XLink, (members of the) HWG suggested that XLink
Updated: 05/17/2005
|
|
|
Creating unified solutions has always been a challenge in the mobile space. Until recently the industry has been solidly divided: all mobile providers aggressively pushed their own proprietary platforms and languages. For example, Nokia and Openwave developed WML and WAP for consumption in North America. In 1999, NTT DoCoMo launched the popular i-Mode service in Japan based on Compact HTML. Mobile developers had to become specialists, learning the intricacies of each platform.
Updated: 05/17/2005
|
|
|
HTML (HyperText Markup Language) exploded into the savvy computer user and developer\'s consciousness around 1994. Although it had been around before that, this was roughly the tipping point when HTML went from obscure scientific curiosity to the point where you could pick up a mainstream computer magazine or go to a bookstore and be assaulted by an overwhelming number of articles and books about HTML. Over the next several years, the W3C (World Wide Web Consortium) codified several new versions of HTML, driven by the leaps in technology from the Mosaic, then Netscape and Internet Explorer web browsers.
Updated: 05/17/2005
|
|
|
If the Semantic Web means anything, it means changing the Web\'s infrastructure just enough so that inter-machine exchanges become as ubiquitous, cheap, and easy as inter-human exchanges already are. One vital goal, however, is to make inter-machine exchanges possible without doing permanent damage to the ecology of the Web: inter-machine exchanges are not meant to replace or supplant inter-human ones, merely to supplement them.
Updated: 05/17/2005
|
|
|
The first article in this series will concentrate on the HtmlForm control and its child controls, deciding how we can best modify the default implementation and extend its capabilities so that it will validate to the W3C\'s XHTML 1.0 and 1.1 strict standards. Additionally we\'ll look at how the default instance uses client-side validation and how this too can be improved.
Updated: 05/17/2005
|
|
|
As with all facets of web design, there are many ways to do a task and get the same (or similar) results. This chapter presents methods for making lists using XHTML and how the lists will look on a variety of devices, including handhelds. (From the book Web Standards Solutions:
Updated: 05/17/2005
|
|
|
In the previous lesson entitled Java JAXP, Writing Java Code to Emulate an XSLT Transformation, I showed you how to write a Java program that mimics an XSLT transformation for converting an XML file into a text file. I also showed that once you have a library of Java methods that emulate XSLT elements, it is no more difficult to write a Java program to transform an XML document than it is to write an XSL stylesheet to transform the same document.
Updated: 05/17/2005
|
|
|
Mapping a Migration Path. Why bother talking about a migration path at all? All the work I have seen so far in the XHTML 2.0 world has been about what it would be like to be there. Which makes sense, since it\'s not finished yet and the HTML Working Group is still hashing out the details. However, there has been a distressing lack of information about what it will take to get there from where we are now. Even assuming that where we are now is \"valid XHTML 1, used properly\" (a huge assumption for most sites), there is still no information about how to make the leap from there to XHTML 2.
Updated: 05/17/2005
|
|
|
HTML Listings
|
|
Total:
59 | Displaying: 11 - 20 | Pages: << 1 2 3 4 5 6 >> |
|
|
