OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: parser for xml-data?

[ Lists Home | Date Index | Thread Index ]
  • From: Sudarshan Purohit <sudar@pspl.co.in>
  • To: Yosr HMAIED <yosr.hmaied@inria.fr>
  • Date: Fri, 08 May 1998 10:36:02 +0530

Yosr HMAIED wrote:

> Do you know parser for xml-data?

    I think this is a good place to talk of the project I'm doing right now.
Basically, it's a translator between an XML-Data document and any
ODBC interface. This involves :
1. Taking an input XML-Data file and outputting a series of SQL
statements that result in the same information being stored in an RDBMS.
2. Using an ODBC Recordset interface to get an equivalent XML-Data
file. ( I'm still working out this one)
    The first part involves parsing the XML file, so I might be able to help out
somewhere, Yosr.

While we're on the topic, I'd like to ask a few things.
1. XML-Data stores Data as "entities". This implies that we've got
a more abstract representaion of data than what would have been
possible through relational databases. For example, we've got this
"ONEORMORE,ZEROORMORE" occurence attribute for child elements.
Implementing this in an RDBMS would mean creating another linked
table for that data item. The same goes for complex data types.
Am I on the right track?

2. If we're creating XML specifically for this purpose, it'll have to
be in the format

<elementType id="Name">

<elementType id="SerialNo">

<elementType id="Tuple">
<!--contains Name and Serial No: as children, occuring once.
Also all key declarations, constarints, .... of teh table as such-->

<elementType id="TheRealTable">
<element type="#Tuple" occurs="ONEORMORE">

This restrictive structure, of course, means that you end up
not using this kind of document for anything else. Am I right
in thinking that this has to be done?

3. The XML-Data specification says that it's open-ended
and new types of entities may be added. I'm assuming this means
I'm able to add  lines like

<level lev="COLUMN">
or <level lev="TUPLE">
into my element delcarations, which will be ignored by other
parsers than mine. Am I right ?

I came rather late into the discussion, so it's possible that
this stuff may have been figured out already. If so, tell me.


Sudarshan                             1030hrs.

The only difference between a rut and a grave is
the depth.
Sudarshan "Connection Machine" Purohit
Persistent Systems Private Limited, Pune

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS