Style sheets describe how documents are presented on screens, in print, or perhaps how they are pronounced. W3C has actively promoted the use of style sheets on the Web since the Consortium was founded in 1994. The Style Activity has produced several W3C Recommendations (CSS1, CSS2, XPath, XSLT). CSS especially is widely implemented in browsers.

By attaching style sheets to structured documents on the Web (e.g. HTML), authors and readers can influence the presentation of documents without sacrificing device-independence or adding new HTML tags.

The easiest way to start experimenting with style sheets is to find a browser that supports CSS.

Source : http://www.w3.org/Style/

An XML Pipeline specifies a sequence of operations to be performed on a collection of XML input documents. Pipelines take zero or more XML documents as their input and produce zero or more XML documents as their output.A pipeline consists of steps. Like pipelines, steps take zero or more XML documents as their input and produce zero or more XML documents as their output. The inputs to a step come from the web, from the pipeline document, from the inputs to the pipeline itself, or from the outputs of other steps in the pipeline. The outputs from a step are consumed by other steps, are outputs of the pipeline as a whole, or are discarded.

There are two kinds of steps: atomic steps and compound steps. Atomic steps carry out single operations and have no substructure as far as the pipeline is concerned, whereas compound steps include a subpipeline of steps within themselves.

This specification defines a standard library, Appendix A, Standard Step Library, of steps. Pipeline implementations may support additional types of steps as well.

source: http://www.w3.org/TR/xproc/

XML is a markup language for structured documentation. Structured documents are documents that contain both content (words, pictures, etc.) and some indication of what role that content plays (for example, content in a section heading has a different meaning from content in a footnote, which means something different than content in a figure caption, etc.). Almost all documents have some structure.

A markup language is a mechanism to identify structures in a document. The XML specification defines a standard way of adding markup to documents.

So XML is Just Like HTML?

No. In HTML, both the tag semantics and the tag set are fixed. An <h1> is always a first level heading and the tag <ati.product.code> is meaningless. The W3C, in conjunction with browser vendors and the WWW community, is constantly working to extend the definition of HTML to allow new tags to keep pace with changing technology and to bring variations in presentation (stylesheets) to the Web. However, these changes are always rigidly confined by what the browser vendors have implemented and by the fact that backward compatibility is paramount. And for people who want to disseminate information widely, this has to include more than just the latest releases of Netscape and Internet Explorer.

XML specifies neither semantics nor a tag set. In fact XML is really a meta-language for describing markup languages. In other words, XML provides a facility to define tags and the structural relationships between them. Since there’s no predefined tag set, there can’t be any preconceived semantics. All of the semantics of an XML document will either be defined by the applications that process them or by stylesheets.

So XML Is Just Like SGML?

No. Well, yes, sort of. XML is defined as an application profile of SGML. SGML is the Standard Generalized Markup Language defined by ISO 8879. SGML has been the standard, vendor-independent way to maintain repositories of structured documentation for more than a decade, but it is not well suited to serving documents over the web (for a number of technical reasons beyond the scope of this article). Defining XML as an application profile of SGML means that any fully conformant SGML system will be able to read XML documents. However, using and understanding XML documents does not require a system that is capable of understanding the full generality of SGML. XML is a much-restricted form of SGML.

For technical purists, it’s important to note that there may also be subtle differences between documents as understood by XML systems and those same documents as understood by SGML systems. In particular, treatment of white space immediately adjacent to tags may be different.

Yes. While the motivation for PICS was concern over children accessing inappropriate materials, it is a general “meta-data” system, meaning that labels can provide any kind of descriptive information about Internet materials. For example, a labeling vocabulary could indicate the literary quality of an item rather than its appropriateness for children. Most immediately, PICS labels could help in finding particularly desirable materials (see, for example, NetShepherd’s label-informed Alta Vista search), and this is the main motivation for the ongoing work on a next generation label format that can include arbitrary text strings. More generally, the W3C is working to extend Web meta-data capabilities generally and is applying them specifically in the following projects:

Digital Signature Project

coupling the ability to make assertions with a cryptographic signature block that ensures integrity and authenticity.
Intellectual Property Rights Management
using a meta-data system to label Web resources with respect to their authors, owners, and rights management information.

Privacy (P3)

Using a meta-data system to allow sites to make assertions about their privacy practices, and for users to express their preferences for the type of interaction they want to have with those sites.

Regardless of content control, meta-data systems such as PICS are going to be an important part of the Web, because they enable more sophisticated commerce (build and manage trust relationships), communication, indexing, and searching services.

“The promise of digital commerce is that it will allow you to use the Internet to purchase the services of the best organic gardening advisors or mad cow disease specialists, whether they live in Santa Clara or Timbuktu. To do this, you need to do more than verify that the person at the other end of the wire is who he says he is. You need to assess competence, reliability, judgment. In other words, you need a system of branding, but applied much more widely for highly specialized and hard-to-evaluate services and products. You need value-added services that will not only lead you to the right product or service but also rate its quality or otherwise vouch for it.”

The W3C (World Wide Web consortium) sports the following motto: “Release early, release often.” It’s a sage maxim to follow when changing the development course of a Web standard. The most recent release of SMIL (SMIL Boston) by the W3C Working Group demonstrates why getting a preliminary model out early is so important.

Synchronized Multimedia Integration Language (SMIL) was introduced in July of 1998. This mark-up language enables Web multimedia authors to schedule presentations so that users experience images, sounds, and text as a choreographed whole (a skill dubbers of Japanese action films never quite mastered). It also allows load balancing of data so that media can be reused. SMIL’s greatest advantage, however, may be that it requires only a simple text editor to write scripts, keeping multimedia authoring as accessible as HTML.

SMIL’s synchronization capability was an exciting improvement for streaming media technology. A little more than a year after its release, SMIL’s impact on multimedia design is even more sweeping.

On August 3, the W3C released the first working draft of SMIL Boston. This version introduces a whole new format strategy: modularity. SMIL’s functionality has been partitioned into nine new modules, all reusable extensions written in XML, each with an associated Document Object Model (DOM).

The new modules deepen the functionality within the SMIL format itself. The strongest example of this may be the Timing and Synchronization Module, with its expansion of hard and soft sync utility. Hard sync confines an entire presentation to the exact description of synchronous relationships in a time graph, while soft sync allows for a looser performance, taking into account changes in network congestion. Changes in network traffic would disrupt the SMIL 1.0 hard sync of an entire document. But SMIL Boston allows authors to apply hard and soft sync to separate elements within the document, making it much less vulnerable to fluctuations in network activity.

These new modules improve interactivity and navigation as well. Users can now navigate within the presentation, changing only part of the display. (In SMIL 1.0, either the entire display changed or a new one was created with each click.) This function is ideal for presentations with a table of contents as the tables can be integrated into the same SMIL file, simplifying authoring.

In addition to being a format for synchronized streaming media, the new SMIL modules can also be integrated into other XML-based languages such as XHTML. For instance, the new Animation Module adds animation capabilities to XHTML. Authors can create animations with JPEG and PNG images, video clips, SVG vector graphics, XHTML headlines, and other media formats. Plus, they can create these robust animations using a plain text editor. For both these reasons, the SMIL Animation Module far surpasses GIF animation, and therefore could very likely supplant it as the most popular animation type on the Web.

From an author’s perspective, SMIL Boston seems headed in the right direction. However, only four of the nine new extensions are detailed in the current SMIL Boston specification, and there is much more functionality planned. The W3C SMIL Working Group may have invited feedback at such an early stage because this modular strategy has implications beyond simply authoring. Another of SMIL Boston’s goals is to encourage accessibility to multimedia for the visually and auditorily impaired.
Accessibility

Since its inception, the W3C has advocated the accessibility of Web content to people with physical disabilities such as poor vision and hearing. This concern is especially pertinent when talking about multimedia content. On September 20, the W3C published the note, Accessibility Features of SMIL. As with HTML, alternative content (such as text descriptions of images) should be included in a SMIL script. Additionally, alternative or equivalent content must remain in sync with the rest of the presentation. The note explains, “Alternatives to video and audio content must be synchronized with video and audio tracks. Alternatives that are improperly synchronized may be so confusing as to be unusable.”

Geoff Freed understands this point well. He is the Product Manager for the Web Access Project at WGBH’s National Center for Accessible Media. (WGBH, the public television station in Boston, was the initial developer of closed captioning, which provided access to televised programming for the estimated 20 million Americans who are deaf or hard of hearing.) Freed has created several SMIL 1.0 demos for the RealSystems G2 player that illustrate how a presentation can be made accessible. His demo “car.smi” is an educational clip about the effects of Einstein’s theory of relativity. The SMIL file consists of a video track, audio narration, auditory description, and text captions. The two audio tracks are timed so that the auditory descriptions do not overlap with the narration. They are also in sync with the video track, so a blind user would know exactly what content the narration is referring to. Freed’s demo is also multilingual: text captions can be viewed in either English or German.

The term Timed Text or (TT) is the term of text media synchronized with other media that of the Video and Audio. In other words, simply put text media with a foreign film, or for the hearing impaired, or subtitles. This term of time text applications came up with the first SMIL 2.0 applications and thus became part of the W3C over all indulgent to implement this tool into all forms of Audio and Video applications. Since then the W3C has formed a working Group that will initiate the Time Text to all existing XML application software that can be implemented to audio and Video text formats.

So when you think of Time Text it is not a new thing of today, it’s just an application added to the part of Audio and Video to enhance the outsourcing of media on the applications widely used today such as SMIL, SAMI, Windows Media Players, Quick, Mpeg’s to name a few examples. Therefore, we will look at the everyday use in the world of technology and see where we implement these areas of Timed Text ( TT ) and how it is used.
Timed Text what it is exactly

Timed Text is not a new invention by any means, but as we, all know the W3c saw that we need a TT that we can all use for most common world texting. HTML, and XHTML along with XHTML + Time can all use this application, it was up to the W3C to finally look at an alternative constructive use of Time Texting in a software format that could be used widely by applications. Therefore, the saw a need for the HTML, as it needs a Time Text in HTML format that can be adapted to all applications of Audio and Video. A tool of text plus timing of Audio and Video for countless reasons, some of Subtitles, from foreign language to the world of adding time Text to Video and Audio, like that of Karaoke and Closed Captioning for the hearing impaired. The W3C first attempt at this was a release development in 2003 for the adaptation of SMIL version 2.0 called the Distribution Format Exchange Profile or the (DFXP)

Therefore, you can read what is being said when volume is low or spoken in a different language adaptation or made for the hearing impaired. A tool to be added to Mpegs, and Mp3 and Mp4 formats, as well as other software’s like that of HTML, XHTML and so forth. The first draft was compatible to Quick Time, SMIL, SAMI, and many other Audio and Playing devices on the net for presentations of Time Text synchronization with the Audio and video Presentation. A Synchronized word texting with the application of video and audio like we mentioned before is not a new area but a necessary one when giving presentation to foreign clients in the business world today. Do they not only see the rich text image or hear sound but also can follow along in text format when the presentation is presented to them.

Timed Text and its Uses

As we can see there are many different uses and implications why we would use Time Text technology tool in the world of our Business and personal lives today. For the Business reasons we would use this in presentations to a large variety of reasons such as Closed Captioning, and Hearing Impaired, Foreign Language, with subtitles. Thus to give a clear crisp presentation of text with synchronized wording to the Audio and Video of the Presentation for audience that cannot hear everything you say but can follow along with the presentation. In the personal Life of the everyday person we use Text Time tool in Karaoke, and in Audio and Video of our everyday lives, when you watch that foreign film, and thus or the volume is just too low, for the hearing impaired to be able to follow the film, or Audio of entertainment. Therefore, if you have ever watched a foreign film with subtitles then you have done Time Text , or sang at a party or night out at a Karaoke again you have used Time Text.

Timed Text refers to the presentation of text media in synchrony with other media, such as audio and video.Typical applications of timed text are the real time subtitling of foreign-language movies on the Web, captioning for people lacking audio devices or having hearing impairments, karaoke, scrolling news items or teleprompter applications.

Timed text for MPEG-4 movies and cellphone media is specified in MPEG-4 Part 17, and is also referred to by RFC 3839.

The W3C is developing a Timed Text (TT) specification that covers many aspects of timed text on the Web. As of April 2006, this was in second Last Call, but had not yet been adopted as a W3C Recommendation.

The issue of developing an interoperable timed text format came up during the development of the SMIL 2.0 specification. Today, there are a number of incompatible formats for captioning, subtitling and other forms of timed text used on the Web. This means that when creating a SMIL presentation, the text portion often needs to be targeted to one particular playback environment. This poses an issue for creating interoperable SMIL presentations. Moreover, the accessibility community relies heavily on captioning to make audiovisual content accessible to a hearing-impaired audience. The lack of an interoperable format adds a significant additional cost to the costs of captioning Web content, which are already high.

Timed Text enriches the user experience for services involving timed text, and is seen as an important stimulus for instance in the usage of captioning and subtitling. The organizations willing to work on Timed Text include vendors of streaming multimedia technology, web browser companies, representatives of the accessibility community, caption content producers and consumer electronics companies.

Since the draft of the SMIL standard in 1995 many organizations implement one of the available versions of the W3C SMIL standard in there end-user products. Macromedia, RealNetworks and Microsoft have some products supporting the SMIL standards, but especially Microsoft with the more dominant role in the browser market have failed to support SMIL fully in the in the past. With Internet Explorer 6 many functions of SMIL did work, but will this be the same for Internet Explorer 7 and even 8 is something that we look at in this review of SMIL and Micosoft Internet Explorer.

SMIL (Synchronized Multimedia Integration Language) pronounced (SMILE) was designed to be a web-based tool like PowerPoint and the ability to run audio, video, and documentation for company presentations of multimedia. Companies like RealNetworks wholeheartedly support this multimedia and of other vendors adopting the standard. “The value of SMIL is that it completely complements important Web components like these [DHTML, CSS, and XML],” said Peter Zaballos, director, systems marketing at RealNetworks. On the other hand some companies think SMIL cannot compete with proprietary products, Macromedia was one of them. Norm Meyrowitz president, Macromedia Products explains “We don’t feel that SMIL integrates well with HTML and the current evolution of the DOM, SMIL is a decent standard for synchronizing audio and video, but isn’t really a multimedia standard. And it does not enable an author to create a rich, interactive multimedia presentation with any kind of sophistication.”

What is SMIL?

The W3C, which stands for the World Wide Web Consortium, develops interoperable technologies that will let people use the Internet to it’s fullest. The W3C is the standard body for HTTP and HTML. In today’s world many new technologies are introduced and one that has shown great promise is SMIL. The proper pronunciation for SMIL is “smile” SMIL actually stands for Synchronized Multimedia Integration Language and it’s a language for describing audiovisual presentations.

SMIL has many advantages; it is also an easy to learn language that functions for many applications. For that reason alone SMIL will be with us for a very long time. Some of the things that SMIL is used for are to create slide-show presentations, which in recent years have gained popularity on the Internet. Internet and Intranet presentations are also soaring and SMIL makes this all possible. One of the most important things about SMIL is the ability of it to display multiple file types like text, video, and audio. With the ability of this software you can give great presentations to clients anywhere in the world.

SMIL is similar to an HTML like language that is written in XML and can be written using something as simple as a text editor. SMIL was development in 1997 and has been improving ever since. SMIL is a language that makes multimedia presentations stand out. If you were doing a media presentation you probably already used SMIL and haven’t realized you were doing so. SMIL has many options like containing links to other SMIL presentations, it also contains features that have buttons such as stop, start and next.

With SMIL you can take your multi-presentations into a new level of appearance with enhancements that help you present your presentation to a higher level of composition. One of the things that SMIL presentations also let you do is display files from multiple web servers. This let’s you display multiple files even if you don’t have them all in one place. This can be valuable especially if you travel frequently and have business presentations to do. The W3C main purpose is to have the Web evolve in one direction so you don’t have many applications being splintered among competing factions. This can be a problem especially if everyone is trying to create something different. Having everyone on the same page is very important. SMIL is the future of the Internet and looks to be around for a very long time.

Microsoft Internet Explorer (IE) 6 and SMIL

SMIL is that of open faced XML Language similar to that of HTML. Currently SMIL is still developing its software and upgrading towards implementing to work with other innovative Web Browsers, but it ran into major problems when Internet Explorer 7 was launched, we will take a closer in- depth look on why this was. SMIL version 2.0 was developed as integrated software capable of running all media formats, and all audio formats, like that of flash players, with the ability of adding dynamic text script to it. No other player has ever been able to do this all in one by simply using a text editor, and when they upgraded SMIL 2.0 version into version 2.1, they made it a static dynamic conversion capable of handling screening online video and audio as a multimedia application. As when SMIL came out in the first version SMIL version 1.0 and later to the developing of the 2.0 they released it as a static dynamic platform.

SMIL version 2.0 and version 2.1 worked well with Internet Explorer 6.0 and its upgrades this is probably thank to the fact that when SMIL was being developed it had the full schematic of Internet Explorer 6.0; Internet Explorer 6.0 was developed and released on August 27, 2001 one month before Windows XP was released. SMIL was first drafted and presented to the W3C in 1995, it then was developed into a Beta draft in 1997. Before it was completed it had to be modified and formatted many times to integrate with many Net Providers Netscape, Java, Internet Explorer, AOL etc along with applications of Hotmail and DOM.

IE 6 and its compatibility with SMIL 2.0 and 2.1

Internet Explorer 6 supports inline transitions, which are based on Synchronized Multimedia Integration Language’s (SMIL) latest specifications. Throughout the HTML+TIME environment, these specifications are put into place through the aid of a transition filter element. The new frame of transitions is designed to add more power to the HTML system. Internet Explorer 6 allows continued support for SMIL 2.0 and 2.1 the developing framework in progress at W3C. The most notable support is in the area of transitions, which allows for effect and filter applications, which can include image and text fades, and application of graduated color backgrounds to elements. This is accomplished at precisely designated times and without the added need for script.

SMIL’s current version (2.1) is fairly complete and comprehensive enough to use efficiently. Broken up into modules, each section describes various aspects of the entire presentation. There is a module that describes the documentation of the SMIL structure itself, and a metadata module that more clearly defines this SMIL document. SMIL schematics benefit from this modularity by allowing them to extend on a module-to-module basis as needed. This is all accomplished without causing unwanted element interactions in other modules.

As the end of Internet Explorer 6’s Beta testing was drawing to a close, the browser was found to be still not fully supportive of SMIL 2.0. There were still too many bugs and necessary updates that had not been put into its structural platform. It took many more tests to incorporate the SMIL platform before the browser could be released to the world. Few Internet Explorer platform systems support SMIL because of their XHTML+TIME frameworks that Microsoft use’s in all Internet Explorer Software. There was a definite need however that the browser support systems such as interactive media, which at the time it did not.

Internet Explorer 7 why was it not compatible with SMIL 2.0 and 2.1

Compatibility issues are a major problem for Internet Explorer 7. The designers failed when they did not add support for SMIL 2.0 and 2.1 versions. This was a considerable complication for web masters and individuals who explore the internet. XHTML+TIME was introduced into Internet Explorer 7, which went beyond the functions of SMIL. When the work was started on Internet Explorer 7, it was officially approved within a couple of months. The design for this software was in development for a substantial period of time which added new features that was conflicting with numerous end-users and website innovators. Which made Internet Explorer 7 not a prime choice for integrating SMIL.

The Internet Explorer platform’s has always used the HTML+TIME function. As always this method will still be in place for Microsoft’s existing clients. The developers do not remove pieces of the software unless a major problem has occurred. However, XHTML+TIME have been newly incorporated into this software. The SMIL 2.0 and 2.1 versions are similar to the new technique. In addition to what this tool can do, but may not be able to use this software with current IE 6 platform incorporated into their software. IE 7 can accomplish even more tasks. Compared to SMIL, the XML Timing language can be seen as a different approach to the timing of XML documents. It reuses a subset of timing primitives from the Timing and Synchronization module of SMIL 2.0. It allows separating content, styling and timing for authoring and maintenance of multimedia documents.

The issues that surfaced were mainly the web masters having to change some of their codes for people to view their web page properly. This increased individuals to seek out other forms of browsers to be able to observe the websites they choose. The developers of Internet Explorer 7 stood by this method. They chose not to support SMIL 2.0 and 2.1 because they felt that XHTML was a more productive measure because of their own software like SMIL that they developed called SAMI (Synchronized Accessible Media Interchange) which works with Microsoft software only. Although SMIL only had to include a patch given to be able to be supported by Internet Explorer 7 which later on they gave out to SMIL so they could run properly 2.0 and 2.1 after a report Microsoft said Quote we will support SMIL versions 2.0 and 2.1.

Microsoft felt there product was better suited and sophisticated version of SMIL. This is important in a new era of internet browsing. The developers believe that people will see a massive difference in their online experience. This method will assist in videos and other multimedia ventures in loading more quickly like SMIL. The bandwidth will be increasingly slower which will assist in more products being placed on one page. This new technique will be helpful in enhancing the way different multimedia objects are offered. With a new time frame motion, add-ons will not be needed to show various videos and displays. The web masters will be able to locate these items quickly and they could relocate them just as easy. This is a new method of bringing the internet to a more active environment. The designers of Internet Explorer 7 have chosen to implement their new HTML as an extended version of SMIL for Microsoft launch of SAMI a perfect clone of SMIL. This technique has all the functions of SMIL plus additional performance; however it will be more user friendly.

Internet Explorer 7 implementing SMIL is simply because Internet Explorer 7 replaced their HTML+TIME with a new ID enhanced Script now known as XHTML+TIME. This is because Internet explorer 7 was implementing their software development Synchronized Accessible Media Interchange (SAMI) into their script software similar to SMIL. A Feature added to Microsoft Internet Explorer 7. While SMIL kept saying to end-users to ask Microsoft for updates, to be able to run SMIL versions 2.0 and 2.1 like the latest version of IE 6. Microsoft did state they would be supporting SMIL and talked to end users and webmasters of the innovative way of the new Web Browser IE 7. The developers of Internet Explorer 7 did state that they knew there would be some changes to the new Internet Explorer, but didn’t state what these changes initialed for SMIL users trying to use the new Internet Explorer 7.

SMIL is still going through upgrades and patchwork for versions 2.0 and 2.1 to implement the new Internet Explorer 7. Microsoft is currently working on the next Internet Explorer, but are not saying if it is IE 8 or just an updated version of 7. As seen in the report. Many webmasters that seen Internet Explorer day View had similar problems with the program as SMIL versions 2.0 and 2.1 simply because they were running the Internet Explorer 6 platform on their web sites. As time dealt out Microsoft released a series of updates to help patch the source of I.E. 6 HOTMAIL + TIME to the new work of XHOTMAIL+TIME to make all sites compatible to the new upgrade program, as SMIL has seen.

Will Internet Explorer 8 support SMIL?

As SMIL continues, they will need to integrate their software, and have proposed a new SMIL 3.0 in December of 2006. This new SMIL will be compatible with Internet Explorer 7 for it has its patch for XHOTMAIL+TIME. SMIL needs to enhanced there platforms not only with Microsoft but Firefox, the new version of Netscape, and so on to keep up with modern advances, or these companies. Which will service a new form of faster Internet browser solutions. No True Clarity is set rather, if Microsoft will support SMIL 2.0 and 2.1 in the next release either it be a new version of Microsoft 7, or moved right through to Version Microsoft Explorer 8. As Microsoft leeks out its new development at a Conference “Chris Wilson said “Microsoft intends to create a follow-on version, IE8, within two years of IE7’s release, which came out in October. The priorities Microsoft set for IE7, Wilson said, are the same for IE8: strong security, ease of use and Web development improvements.” All we know is that Internet Explorer 8 will still have XHOTMAIL incorporated into it, and be that of IE 7 user interface, with easy to use buttons and tabs. As well “Wilson told media that security “Will be the key priority. The development team will also focus on ease of use and seek to improve web development with current standards compatibility”. But what ever happens in truth that SMIL needs to upgrade to the new 3.0 version that is still in development from the draft. As Web Browsers keep Focusing on Security and unlimited bandwidth for the Companies like Microsoft that Develop Operating systems like Windows XP, and the New Windows Vista.

Resources

• Wired - Microsoft snubs SMIL - Microsoft frowns on SMIL
  http://www.wired.com/science/discoveries/news/1998/07/13478
• W3C - World Wide Web Consortium Issues SMIL 2.0 as a W3C Recommendation
  http://www.w3.org/2001/08/smil2-pressrelease
• Synchronized Multimedia Integration Language
  http://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language
• Wikipedia Internet Explorer 6
  http://en.wikipedia.org/wiki/Internet_Explorer#Version_6
• Wikipedia Internet Explorer 8
  http://en.wikipedia.org/wiki/Internet_Explorer#Version_8
• Wikipedia - Synchronized Multimedia Integration Language
  http://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language
• W3C - Accessibility Features of SMIL
  http://www.w3.org/TR/SMIL-access/
• Microsoft - The Microsoft DHTML Platform
  http://www.microsoft.com/technet/prodtechnol/ie/reskit/6/part3/c11ie6rk.mspx?mfr=true
• Your guide to Microsoft’s next browser
  http://internetexplorer8.net/
• W3C - Synchronized Multimedia Integration Language (SMIL 3.0)
  http://www.w3.org/TR/2006/WD-SMIL3-20061220/
• XML.org XML and Web Services In The News - 26 December 2006
  http://www.xml.org/xml/news/archives/archive.12262006.shtml#2
• ZDnet Microsoft hints at general plan for IE8
  http://www.zdnet.com.au/news/software/soa/-Microsoft-hints-at-general-plan-for-IE8/0,130061733,339275254,00.htm
• India Times - Microsoft hints at IE8
  http://infotech.indiatimes.com/articleshow/2004959.cms
• Microsoft - Understanding SAMI 1.0
  http://msdn2.microsoft.com/en-us/library/ms971327.aspx
• Access-IT - What is the difference between SMIL and SAMI?
  http://www.washington.edu/accessit/articles?74
• CNet.com - Internet Explorer 7
  http://www.cnet.com.au/software/internet/0,239029524,339271767,00.htm
• Microsoft IEblog - The prolog, strict mode, and XHTML in IE
  http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx
• Sitepoint Newsletter
  http://www.sitepoint.com/newsletter/viewissue.php?id=3&issue=107#4
• No, Internet Explorer did not handle it properly
  http://www.howtocreate.co.uk/wrongWithIE/?chapter=Summary
• Understanding Xhtml - A practical introduction to XHTML
  http://www.astahost.com/info.php/understanding-xhtml_t5338.html
• Wikipedia Internet Explorer 7
  http://en.wikipedia.org/wiki/Internet_Explorer#Version_7
• Microsoft - Internet Explorer (March 9, 2006)
  http://www.microsoft.com/windowsxp/expertzone/chats/transcripts/06_0309_ez_ie.mspx
• Microsoft IEblog - Time, Time, Time, see what’s become of me…
  http://blogs.msdn.com/ie/archive/2006/04/07/571198.aspx
• W3Schools - W3C SMIL Activities
  http://www.w3schools.com/w3c/w3c_smil.asp
• Cover Pages - Synchronized Multimedia Integration Language (SMIL)
  http://xml.coverpages.org/smil.html
• XML.com - A Realist’s SMIL Manifesto
  http://www.xml.com/lpt/a/976
• BetaNews - Internet Explorer 6 in Final Stretches
  http://www.betanews.com/article/996813882

Microsoft Internet Explorer 7 (IE7) does not fully support Cascading Style Sheets (CSS). Why the call for standards in browserworld again did not reach the producer of the world most used browser? (more…)

Ever since the word was used, Semantic Web we wondered what it all entailed why it came about and what purpose could it have. The term is simple enough to integrate people, data, software, publications, and clinical trials. Therefore, this means majority of the common use of a Semantic Web Life Science is used by Clinical research development and studies. In addition, is under the needful watch of the W3C (World Wide Web Consortium) to come up with a program software that is adaptable for all areas of the Life Science divisions. (more…)