W3C home > Mailing lists > Public > www-html@w3.org > April 2000


From: Ashvil <ashvil@i3connect.com>
Date: Sun, 2 Apr 2000 22:14:33 -0700
Message-ID: <002101bf9d2b$7f5c6760$2ae3c53f@pacbell.net>
To: <www-html@w3.org>
I had posted this message to the XML-DEV list, apologies if you get this

The new MS Media Player 7 uses XML for skins.

Sample Theme file
      clippingColor = "#CCCC00"
      backgroundImage = "background.bmp"
      titleBar = "false">

         mappingImage = "map.bmp"
         hoverImage = "hover.bmp">

         mappingColor = "#00FF00" />

         mappingColor = "#FF0000" />



There are two ways of looking at this
1. This is Bad and will encourage every one to come up with their own flavor
of XML applications. XHTML should have been used to describe Skins and any
other UI standards.
If Skins require more than what XHTML currently provides, then that
functionality needs to be added as an XHTML module. etc...

2. This is good. It allows developers to focus on the task of creating the
Theme using simple tags (and not having to learn XHTML). XSLT could then be
used to convert this into XHTML. etc...

Counter point to 2.
If the focus is to hide the developers from XHTML, then a visual XHTML tool
could be used to generate XHTML directly. etc...


What do other list members think of everyone generating their own XML file
format to represent common data, in this case the data is visual data. Or is
this a small issue due to tools like XSLT ? Or should XHTML be used for all
visual data ?

Received on Monday, 3 April 2000 01:09:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:53 UTC