Lists Home |
Date Index |
> There are a lot of XML books today, but the fact is that few are really
> good and useful. Some of them contain a lot of technical errors and lack
> basic editing or proof reading.
There are some gems that come to mind (David Brownell's book on SAX is
one)....and coupled with the online resources, specs, tools and such, that is
usually more than sufficient to get a good grownding if you have a few
functioning grey cells and spend the time really looking into the technology.
> Even if you find a good XML book, mastering XML and all "Related
> Technologies" can be overwhelming.
I'm not sure I agree with that. If you try to absorb everything in one fell swoop,
then maybe so, but that is not a good way to learn. Best to master the basics
first (core XML, parsing, DOM, SAX and that's about all)...then start to build on
that foundation as interest and need dictate.
> For example, in a Web Services project, you might find yourself using all
> of the following technologies: XML1.0, Namespaces, DOM, SAX, XML Schemas,
> XPath, XSLT, XPointer, XInclude, XBase, SOAP, WSDL, XML
> Signature/Encryption, and UDDI. New specs are on their way to
Any beginner that tries to do this, under project deadline pressures, is likely to
produce an abysmal mess of an application. Not recommended. Any
company/manager that expects their people to absorb all that in a short period
(and many unfortunately do given the hype that surrounds Web Services), and
still produce a quality product is in for a rude awakening.
> The reality of enterprise projects is that people need to get up to speed
> on XML as quickly as possible.
I would suggest that enterprise projects need to build the "true" learning curve
into their planning.
> An XML Instructor who also has hands-on
> project experience can help you navigate through the essentials of each of
> these specs.
Most instructors are not good developers nor do they have current project
experience. Least not in my decades of experience.
> I also think that W3C working groups should create not only primers and
> use cases, but also quick references as part of their deliverables. The
> quick references will be very helpful in adopting and implementing the
I agree with you on that.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions