XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] What is the general direction you are seeing these daysto store and query lots of large complex XML?


On Wed, Mar 11, 2015 at 2:52 PM, Liam R. E. Quin <liam@w3.org> wrote:
On Wed, 2015-03-11 at 12:11 +0000, Ihe Onwuka wrote:
>
[...] an additional
> shortcoming I
> found with eXist - the insistence on a strictly hierarchical
> collection structure. This forces me into choice I do not want to
> have to make for a
> movie repository -  whether a rom/com goes in the romantic
> collection or the comedy collecton - and of course genre is not the
> only facet worthy of
> modelling collections on.


For http://www.fromoldbooks.org/Search/ I modeled this with keywords
associated with each item; for more rigid categories, have a list of
categories each with an ID, and point to a list of categories from the
item,e.g.  using IDREFS if you're using validation.

Then I only use one database collection.


Hmmm I hadn't thought of that but  alas an additional objective was to fine tune the locking granularity of a database request which was to be achieved via multiple collections.





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS