hi and use cases for applications

[Jakob Praher <jpraher yahoo de>]

hi all,

I am very exciting with new storage metaphors, as I also think that the
hierarchical storage we use today doesn't meet the users needs.

I already have successfully compiled storage on my debian box, and ran
the sample "images" stuff.

Now my questions:
* given a storage "aware" app, how does the user interact with storage?
* how does storing, creating new documents, deleting documents work?

After thinking about, for instance creating documents, I came to the
conclusion that given documents explicit names is rather useles ... 
E.g. wouldn't it be much better, to give the document some kind of
relation to other documents? 

What are your ideas about dealing with different represenstation. For
instance, nowadays its the case, that you have some source file, in xml
format, and you would like to view it using pdf. Could such a thing be
implemented given the current design?

What are your ideas about refereing documents, should there be some kind
of xpath like way to refere to a document? - Or is that just done
internally by a unique id....

I know lots of questions, I would look forward to discssing some of
these points with you ...

-- Jakbob