From: Laurian G. <la...@gm...> - 2004-12-15 12:06:01
|
Hello, > Considering only metadata. > For simplicity we have to select the "master copy" of metadata. > In my opinion if we use a "RDF Repository" (Sesame or others) it's not > useful to mantain a file system repository. > We can generate on the fly the metadata organized as the current file > system using querys. > > We can have an "export-import" tool that generate the "namespace-zip" > including metadata taken by querys and contents (or only URLs to > contents) and vice versa. perfect. > >- any other ideas for triple editing (the super pull-down menus) such > >that we don't load an entire namespace into the client UI? > > > We have to think ... how ... > One solution is to use a approach similar to the "simile logwell" using > collapsable boxes, server side, for each namespaces/resources during > the selection... a lot of work todo ... I would like to have it like the auto completion you have in Gmail. Anyway won't be feasible to load all the namespace(s) into the client for this feature, and doing it by server round trips is subject to latency... > I'm studying to design a "RDF repository independent" java interface ... > Stefano We'll need also a plugin architecture, that will allow also parallel development and experimentation with the underlying (future) repository framework. Cheers, -- Laurian Gridinoc Chief Developer GRAPEFRUIT www.grapefruit.ro |