David, I'm glad you understand my comment as it was ment. I didn't want to kick off a big discussion whether relational databases are better than XML databases, or not. There are surely arguments that make such an XML support reasonable. I'm personally very fond of XML and therefore happy to support this project if it's feasible for me.
I had a look at the MODS schema and agree, that it is a bit complex. But the complexity arises mainly from the possibility that so many elements can occur more than once. Therefore one would need a lot of relational tables to store the data. But this is no principle problem. One can deal with that. The import from SQL should be relatively easy. You only need a bunch of SQL queries that deliver the data in the right order. The other way around is much more complicated, as you have to generate the keys to establish the relationship between the different tables using primary keys and corresponding foreign keys. What concrete steps that I can do would be helpful for you? Cheers Ren� Klaus, I didn't get your point. Shredding XML documents, as you call it, is not a bad thing. There is no use in its own to preserve whitespaces outside of XML elements or attributes except the case that the document or fragment is digitally signed, which is still rarely the case. In all other cases the XML document is just another form of storing (more or less) structured data and by no means worse or better than storing the data in relational tables. By the way: Oracle can also store XML documents as a whole to preserve whitespace and make validation of digital signatures possible. -----Urspr�ngliche Nachricht----- Von: David N. Wilson [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. Januar 2005 23:05 An: [email protected] Betreff: Re: AW: [xml-dev] XML-Database Support in OOo ? Ren�, Thank you for your comments, we need critical input as well as encouragement and assistance. The situation we have with the Bibliographic data is the standard we intend to use is MODS "Metadata Object Description Schema" ( http://www.loc.gov/standards/mods/ ) which is expressed and maintained as an XML schema. We plan to store the bibliographic data in the documents internally in an XML file conforming to this schema in the save file package. The problem we have is that the MODS schema is complex and it is difficult producing a suitable SQL schema that will not be broken with any changes to the MODS schema. We have not yet found anyone who has produced a SQL schema that maps the MODS XML schema. This is a problem we need to tackle, as we need to be able to support the use of SQL databases for bibliographic system. So we will need to produce a MODS schema to SQL schema mapping and a MODS data - SQL data import/export filter. Any suggestions and help would be appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
