From: Patrick B. <pat...@jo...> - 2010-07-30 16:25:33
|
So, it seems like we're fairly agreed that a new axis is not the way to go. I would tend to agree that is the right decision. So the only question left is whether to use key/value or xml fragments. I like Wolfgang's method of accessing metadata, it seems very consistent and intuitive. Unless I'm missing something, I'm still having a hard time seeing value in choosing key/value over xml fragment. Since under Wolfgang's suggestion anyone who wanted a key/value type metadata set could simply access them as metadata("/db/doc.xml")/keyOne metadata("/db/doc.xml")/keyTwo This may not allow us to store binary data natively in metadata fields. But I would contend that in 99% of cases metadata is being used to aid in searching for or classifying another resource in the database. As a side note. I'm planning to begin working on implementing this around the 2nd week in August. Cheers, Patrick On Fri, Jul 30, 2010 at 6:41 AM, Adam Retter <ad...@ex...> wrote: > > we need to keep in mind that when data is backed up / archived / > > extracted outside the system that metadata moves with it. > > Completely agree with you. But as was mentioned earlier in terms of > thinking of ntfs streams, when the backup is done as well as for > example doc1.xml being in the backup you could also have doc1.xmd > (containing the metadata) > > > J > > > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Patrick Bosek Jorsek Software Cell (585) 820 9634 Office (585) 239 6060 Jorsek.com |