cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agsoftware.dnsalias.com>
Subject Re: [RT] Moving towards a new documentation system
Date Sat, 11 Oct 2003 15:33:15 GMT
Stefano Mazzocchi dijo:
> a repository is just like a database: editing a database by direct SQL
> injection is silly. Today it doesn't look silly because repositories
> are *much* less functional than a database, but when you have a
> *serious* repository (for example, one that can extract properties from
> an image and provide an RDF representation for it), editing it *by
> hand* would be silly.

Is a good idea to use some a XML database to store the content? I guess we
are taking about an application outside the cvs, right? If this is correct
a good candidate can be Xindice: http://xml.apache.org/xindice/ :)


>> I agree that a pure ID for naming pieces  of content might be better,
>> provided lookup is super-easy and doesn't get in the way of editing,
>> keeping track of changes etc., and the ID's stay readable and
>> "communicable".
>
> +1 to these goals.
>
> --
> Stefano.




Mime
View raw message