Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Shredding XML

From: "Jim Tivy" <jimt@----------.--->
To: "'Petite Abeille'" <petite.abeille@-----.--->, <xml-dev@-----.---.--->
Date: 11/1/2009 7:57:00 PM
Interesting post, but I am not sure that "now is the time to talk of many
things".

Let me try to focus: 

Proper software execution comes from the choice of appropriate
actions/technologies to match the driving requirements.  But more
importantly, the greatest Wisdom, is to frame the driving requirements
correctly before "going off half cocked" or doing something that is
unnecessary and unwarranted.  

So lets start by framing the requirements again:

Fraser Gofin wrote:

"
The basics are we receive XML messages from an external trading partner and
process those messages, enriching and routing to a number of internal
subscriber applications. One of these applications is MI and the deal here
is that they want the data to been put into a relational database so that
they can create a number of interfaces 'files' which are sent to still more
applications.
"

OR

"
I am mainly interested in the process of LOADING XML data to a database
rather than extracting (at least for the purposes of this discussion).
"

It is possible that the "mother persistent application datamodel" is
contained in the relational database in all its normalized glory.  If so,
then, "processing the messages" is simply a "data import" operation.  So the
question is, how do I get XML X* to tables T*.  It would strike me that lots
of people are doing this.  Are there common techniques and technologies for
doing this import?

Fraser, is that a proper framing of the question/requirements?

Jim


-----Original Message-----
From: Petite Abeille [mailto:petite.abeille@g...] 
Sent: Sunday, November 01, 2009 9:56 AM
To: xml-dev@l...
Subject: Re: [xml-dev] Shredding XML


On Oct 29, 2009, at 10:20 PM, Fraser Goffin wrote:

> opinions on the subject of decomposing XML into relational databases

Outside of the most trivial case, this is a major PITA of the same  
epic proportion as the object-relational one:

http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx

Good luck.



_______________________________________________________________________

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@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php




_______________________________________________________________________

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@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent