RE: [xml-dev] XML support in browsers?

["Laurens van den Oever" <laurens@xopus.com>]

> (b) a transformation model for style that seemed like massive overkill

> compared to the annotation approach of CSS.
>
> The way things turned out, these costs pretty much only get inflicted
on 
> people who have problems difficult enough to make them seem
worthwhile.

As the vendor of a browser/XSLT based XML editor those people often come
to us. Introducing XML/XSLT at the publishing side of the web only makes
sense if the XML is semantically richer than HTML. And that makes it
harder to edit than HTML. We focus on the usability of that task.

That said: we see a trend towards XML/XSLT for web publishing. The rise
of Web 2.0 has shifted the large enterprise view of the web from a
platform for online brochures and references to a strategic marketing
channel.

With that comes the need for richer-than-html and consistently
structured content. For instance consider a page like this:
http://pages.ebay.com/help/account/registration.html
This page is not very complex, but significantly easier to edit and
maintain if you have specific XML markup for each section and a XSD/DTD
to control allowed content. Separating the foldout question XML content
from the browser specific HTML implementation also has huge benefits
with a plural browser/platform/screensize target audience.

As more and more people have these needs, they will see that XML/XSLT is
the best technology for rich web content publishing. 

Laurens van den Oever
CEO, Xopus BV

http://xopus.com
+31 70 4452345
KvK 27301795


-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com] 
Sent: maandag 8 juni 2009 21:51
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] XML support in browsers?

Andrew Welch wrote:
>> Ten years later, it's clearer and clearer why XSL didn't take the Web
by
>> storm!  I guess I really had nothing to worry about.
> 
> So what were you worried about - learning XSLT ?

No - I've done that.

I was worried about:

(a) the Web getting a lot harder to learn than it previously was, and

(b) a transformation model for style that seemed like massive overkill 
compared to the annotation approach of CSS.

The way things turned out, these costs pretty much only get inflicted on

people who have problems difficult enough to make them seem worthwhile. 
  Even though I sometimes wish XLink had worked out, in general I'm 
pretty happy that "SGML for the Web" wound up "XML for not necessarily 
the Web."

-- 
Simon St.Laurent
http://simonstl.com/

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php