My conclusion is that for storing XML data would be usefull ut using a
ODBMS based on the ODMG 3.0 specification that incorporates advances in
object database technology (e.g., replication), data management (e.g.,
spatial indexing), and data formats (e.g., XML) and to include new
features into the
[EMAIL PROTECTED] wrote:
> GinTon wrote:
>
> > I think that would be a big step if we could implement a NXD in Django,
> > but I don't speak of substitute a RDBMS by NXD else of using NXD when
> > it was really necessary.
>
> I think you'd first have to go 'up' a layer, and define an API onto
>
I´ve looked into some Oasis-specs (UBL) a while ago, and while i can
see some sense in applying detailed standards in specific
B2B-procurement areas, I´m more skeptical, whether these complex
approaches will really scale beyond those markets.
Adam Bosworth, VP, Engineering at Google stated in his
[EMAIL PROTECTED] wrote:
> I can't see any reason why you cant use an object database in Django,
> its just that the admin interface to it won't work like the current
> admin interface.
As you can read in the down link I am trying to implementig the free
specifications of OASIS (xNAL, xPIL).
The
GinTon wrote:
> I think that would be a big step if we could implement a NXD in Django,
> but I don't speak of substitute a RDBMS by NXD else of using NXD when
> it was really necessary.
I think you'd first have to go 'up' a layer, and define an API onto
semi-structured data, and then you coul
