Hi everybody,

We've been thinking of ways of integrating Scott's code and ideas for the OT
representation   (
http://confluence.concord.org/display/CSP/OTrunk+Jackrabbit) in Roolo.

Currently, the structure for the ELOs in Roolo inside Jackrabbit is

a-b-c
|-METADATA
|   |-otmlMetadata
|-CONTENT
    |-contentFile

a-b-c is an ELO with content and metadata. The metadata is stored in the
otmlMetadata node.

Scott's idea is about having scattered ids inside the otml file so that can
act as anchors for referencing them from inside the otmlFile or externally.
We think that's something very powerful, but we also want to provide a
general way in roolo for other contents (Images, PDFs, Word files,
whatever...) that do not have an xml structure. We have come up with a new
jackrabbit internal representation for the objects that admit a structured
content (xml file) as well as raw data (images...).

|-Photo *
|
|-Document  **
|
|-AirbagProject ***
|  |-root
|  |-bundles
|  |    |- ...
|  |-Children
...

* is an Image file ELO, ** is a PDF file ELO, *** AirbagProject is an OTML
file ELO
Metadata is stored in *, ** and *** nodes, but as AirbagProject is an
structured ELO, it has structure and possibly ids and more metadata inside
to be able to reference its parts.

Thoughts about it?

Geoff, Tony and Carlos

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to