Laurian Gridinoc wrote:
>Hello,
>
>
Hi Laurian,
>And thank you all for everything :)
>
>I'll try to list here things we discussed, please add what I missed here...
>
>Paolo, I wait for the scans ;)
>
>On platypus core, we discussed the triple repository (which adds query
>and inference support) versus file based system (which is easy to
>manipulate: zip, rename, etc), I believe that the next step in this
>direction will have to use both systems (and by this will be backward
>compatible):
>
>I mean that we keep the file based stuff, and on each operation as it
>works now, we do that onto the repository too, but all the queries are
>made against the repository.
>
>And we'll have to add 2 synchronization tools: to refresh the
>repository with the data in the file system (ie. I get a zip with
>another wiki namespace from a different platypus), and one that may
>overwrite the filesys metadate within the repository (writing the
>concise boundary description to the page metadata)
>
>
>This imply also removing "incoming" arcs to a page, since we display
>that from the repository. And this eases the use of the filesystem.
>
>What do you think?
>
>
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.
>
>On platypus UI:
>1. Viewing
>- we have to see how can we have the user modify the templates with
>ease, XSL which I like is too much for end-users, Velocity (Paolo
>proposed) is pretty ok; but a solution in which the user can do
>everything at CSS level only would be great (plus some includes of
>header/footer)
>- I'll study the collapsing of sidebars and sidebar boxes (as in simile)
>- I'll see how can we display expandable trees in sidebar (for blank nodes)
>
>
Ok.
>2. Editing
>- FCKEditor must be fully implemented into (with image upload, etc)
>plus link types and transclusion.
>
>
ok.
>- 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 ...
>Stefano, we were talking of Waterken (http://www.waterken.com/) and
>Pico container (http://www.picocontainer.org/), and on web
>continuations in java: https://rife.dev.java.net/
>
>
Thanks..
>
>
>More as I remember... I'm still dizzy after the trip.
>
>Cheers,
>
>
I'm studying to design a "RDF repository independent" java interface ...
Bye Bye
Stefano
|
