Skip to Content.
Sympa Menu

xom-interest - RE: [XOM-interest] javascript

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: "Jacobs, Robert A." <ra.jacobs AT ngc.com>
  • To: "xom-interest" <xom-interest AT lists.ibiblio.org>
  • Subject: RE: [XOM-interest] javascript
  • Date: Fri, 6 May 2005 11:03:39 -0500

If you are going to make the switch to XML, you need to understand that,
to be truly effective, you probably will have to read a number of books.

You are learning a new programming paradigm. You will need to combine
technologies, parsers, schemas, namespaces, xpath, xquery, and
transformations. In the short time I've been working with XML (3-6
months,
off and on) I have had to study all of these things. From my experience,

learning "XML" is really learning a family of technologies. Certainly,
this complicates the communication; it is not a trivial,
pick-it-up-and-go
family of technologies. XML, in my opinion, is a *transport* mechanism
that, by itself, is of limited use; what makes XML really powerful is
all
those other manipulators you can bring to bear on the base document -
learning those takes time.

As Elliotte and others have already tried to tell you: it is absolutely,
unequivocally, *incorrect* to think you can embed the '<' character into
a text-node of an XML document. This is explicitly not allowed by XML.
You need to treat it like a reserved word and accept the fact that the
foundation upon which all XML technologies are built is an assumption
that every XML document will be well-formed.

I think the technology you are really after is XSLT. You produce an XML
document and then pass it through an XSLT to render the XML into HTML.

-----Original Message-----
From: xom-interest-bounces AT lists.ibiblio.org
[mailto:xom-interest-bounces AT lists.ibiblio.org] On Behalf Of Luca
Passani
Sent: Friday, May 06, 2005 9:04 AM
To: Elliotte Harold
Cc: xom-interest
Subject: Re: [XOM-interest] javascript

Elliotte Harold wrote:

>
> Right there is your problem. XOM does not generate text/html. It
> generates application/xml or perhaps application/xhtml+xml. Try one of

> those media types instead. But right now it's like you're pumping
> diesel fuel into an engine that expects regular and wondering why your

> car keeps backfiring.
>
Elliotte, I think you are really a smart guy and you have created a
totally cool tool. I respect you for that and I give praise where praise
is due.
On the other hand, please also try to see it the way of those poor
bastards like me who have multiple tasks to perform in their everyday
job but so little time for details. I need to build a small
proof-of-concept prototype, which implies the need to inject a tiny bit
of client-side scripting into my page. I am just a tiny step away from
the goal: turning &lt; into '<'.
That's how JavaScript has worked for years before XML and how all
browser still understand it.
How many books should I study before I can achieve that? do I need to go
back to the university?

RegExps are not powerful enough to parse XML/HTML. You are right about
that, but, once I switch to XML, there must be an easier way than this
to take care of details, don't you think?

Thank you

Luca

_______________________________________________
XOM-interest mailing list
XOM-interest AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/xom-interest




Archive powered by MHonArc 2.6.24.

Top of Page