Design principles and architecture of an information transferstandard based on XML and SOAP

[xkenneth]

All,

So i'm just about to undertake my first real open source project,
and I'm looking for a bit of advice. There's an oilfield standard
called WITSML (Wellsite Information Transfer Standard Markup Language
- witsml.org), it's basically a collection of XML schemas and a spec
for an client-server based communication standard based on SOAP and
WSDL. I'm looking for advice and past experience on how to architect
this project and implement it properly. I'm fairly new with concepts
such as threading, ORM, etc in a server/client context. If anyone has
any past experience they'd like to contribute, architecture theory,
documentation, anything at all, I'd be very grateful.

You can find our project here:
(also feel more than welcome to join and help!)
http://www.openplans.org/projects/openwitsml/summary

Regards,
Kenneth Miller
(e-mail address removed)

 

[Stefan Behnel]

I'm looking for a bit of advice. There's an oilfield standard
called WITSML (Wellsite Information Transfer Standard Markup Language
- witsml.org), it's basically a collection of XML schemas and a spec

For implementing XML languages, I (biasedly) advocate lxml's element class
features.

http://codespeak.net/lxml/dev/element_classes.html

I'll give a tutorial on them at EuroPython, in case you're interested.

Stefan