> > Williams, Timothy W. wrote: > > >>Nope, not with the XML:DB API (though this information is actually > >>stored in Xindice, or at lease I've been told it is). I'm > supposed to > >>come up with a generic metadata support, but I don't have a precide > >>timeframe for it. I could use some help... :-) > >> > > > > Have you settled on an approach to storing and accessing > metadata yet? > > --tim > > > While I was still at Sun, I wrote a metadata wrapper for Xindice > called "XNode" which has been submitted to the project. It's very > similar to a lightweight SOAP, ie., it's got an envelope, header > and body. The Java Web Services Pack has a demo application called > "Indri" that implements the XNode API. I'm using XNode (and of > course Xindice) as the means of storing content and metadata in my > current project. The delivered API has three metadata attributes: > node ID, creation and modification dates.
In my admittedly ignorant understanding, it seems that if the wrapper had it's own schema and the payload (body|resource|document?) had it's own schema things would break. So if you were simply wrapping the metadata around a whole resource that had a schema reference in it, it would generate a parse error, no? Is there general agreement that simple key/value pairs like creation/mod dates is enough or is there a requirement for nested heirarchical metadata? Is there general agreement that metadata will only be at the document/resource level and that more granular metadata would need to be in the document itself? I notice the project planning notes (#13) has "Node level meta data". what's an example of "node level meta data"? sorry for the simple questions, metadata is a fairly big topic with varying definitions, so I wanted to make sure I'm talking about the same thing... --tim
