[
Lists Home |
Date Index |
Thread Index
]
>>just as straightforward<<
I don't know. Is there a bulk data methodology that is generically understood,
or could one be proposed? If so, then it might be another parallel idea.
Not familiar with bulk data, but I am supposing that bulk data breaks a
hierarchical xml document into two or more flat tables that are linked on a key
element. My suggestion may actually work on such flat tables to remove
remaining "syntactical excesses" Also I guess it is a similiar approach
except that when using hierarchical xml no key is needed to accomplish the
normalization.
>>shim in-between to handle an abbreviated syntax<<
Yes, but I am suggesting that it could be some kind of generic xml structure
and so the "shim" is then not application specific.
regards,
bill p
Bill Kearney wrote:
> > Sorry if this is an old idea. The more I have experimented with the idea
> > recently, the more compelling it seems.
>
> This seems more like an application level argument. That is, if your
> application is geared toward individual transations how would this help?
> You're going to have to add some sort of shim in-between to handle an
> abbreviated syntax, so wouldn't it be just as straightforward to do this
> with a bulk transaction set of data instead?
>
> But there would seem to be some merit in having a more standardized way to
> express repetitive , regular data without all the syntactical excesses of a
> plain XML file.
>
> -Bill Kearney
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
|
