Document collections

[nmueller]

JOMDoc should be able to manage collection of OMDoc documents referring to the discussion on how to retrieve a symbol from another document than the current one.

[clange]

You mean that JOMDoc should maintain a local cache of any OMDoc document from which content is retrieved? And probably with its own garbage collection? Nice idea!

More exactly, what is a collection? Any document that is requested by the program using JOMDoc, or something that the programmer has to initialize beforehand (e.g. "document A and document B and document C"), or something like "a document and all of its references, recursing down to a depth of n"? -- Any of these could make sense, depending on the use case…

[nmueller]

Replying to clange:

You mean that JOMDoc should maintain a local cache of any OMDoc document from which content is retrieved? And probably with its own garbage collection? Nice idea!

Yeah, I am thinking of using  http://hsqldb.org/

More exactly, what is a collection? Any document that is requested by the program using JOMDoc, or something that the programmer has to initialize beforehand (e.g. "document A and document B and document C"), or something like "a document and all of its references, recursing down to a depth of n"? -- Any of these could make sense, depending on the use case…

For me a document collection is the later one. The former one works as well, you just have three initial documents to traverse and if one only wants to use these three documents she could set n to 1.

[anonymous]

Milestone MX - JOMDoc misc deleted

[clange]

This needs to be synced with the TNTBase progress. Maybe it's possible to have a small, embedded TNTBase for this purpose?

[vzholudev]

What do you mean by embedded? It's possible to set up an svn repo which is on the same machine where JOMDoc is supposed to be used. Than you have to provide SVN or HTTP access to this repository (that's because SVNKit can't work with BDB repositories via lova protocol), then we can utilize my local library for accessing such a repository (that is xSVN repository). Usage of this library is quite straight forward and all oyu have to provide as an input is path to the repository in a local file system and SVN or HTTP url for accessing it via my internals which use SVNkit. Actually the latter is not necessary if you are not going to modify file via my library (but only use svn client interface) or retreive older revisions.

Also I have a nice RESTful interface which does a lot of things which one wants when wroking with XML files.

@Normen, if we want to benefit from XML structure of OMDoc document, probably we shouldn't use relational databases. But they claim to be very fast and who knows what eventually turns out to be faster

[cmueller]

see ticket:336 and the latest PoMDoc release.

[clange]

Replying to vzholudev:

What do you mean by embedded? It's possible to set up an svn repo which is on the same machine where JOMDoc is supposed to be used. Than you have to provide SVN or HTTP access to this repository (that's because SVNKit can't work with BDB repositories via lova protocol), then we can utilize my local library for accessing such a repository (that is xSVN repository). Usage of this library is quite straight forward and all oyu have to provide as an input is path to the repository in a local file system and SVN or HTTP url for accessing it via my internals which use SVNkit. Actually the latter is not necessary if you are not going to modify file via my library (but only use svn client interface) or retreive older revisions.

Yes, that's probably what I meant. However, it should be as effortless as possible for the JOMDoc user to create/manage this local repository. It may turn out to be a lot of work for you to make this possible, but from a pure usability point of view: If some advanced local JOMDoc service only works if a repository is available, and the user does not have access to any external repository, or if the files just happen to be available locally, then JOMDoc should create this local repository transparently, without the user noticing it.