Hi, I have the following questions:
1. Does Jackrabbit guarantee unique IDs to nodes which are not in the same workspace? This could be something we definitely want down the road in order to be able to share resources? 2. We need to keep some structure for storing images/documents and other sorts of resources. This is because when a new ELO is created and its resources are passed to the CMS layer, we need to know where we're putting the resources. This is very trivial but we need to come up with a structure. Also this could become slightly tricky because the otml file needs to also know which version of the resource they're interested in. Project A can want the first version of an image and project B would want version 5. Also we need to take care of the deletion impacts on resources. What happens to the resource when project B is deleted? 3. Overall given all the involved parties are happy with the otml/otrunk infrastructure, I don't know if we need the new system YET. It's possible that the concord team needs this enhancement for some of their other projects but I don't know. Please let us know if that's the case Scott/Aaron/Stephen. ps. Turadg as to your questions below: METADATA and CONTENT are children of the ELO name node. Do they have any siblings or will they? >From what I know/remember METADATA and CONTENT do NOT have any siblings. That's my two cents. On Sat, May 24, 2008 at 6:38 PM, Turadg <[EMAIL PROTECTED]> wrote: > > Sounds like a reasonable approach. I have some clarification > questions. > > You say that "metadata is stored in the otmlMetadata node". I assume > that's just for OTML files? A JPEG would have a different node under > METADATA? > > METADATA and CONTENT are children of the ELO name node. Do they have > any siblings or will they? > > Why is there a contentFile node within CONTENT? Why not just put the > content on the CONTENT node. Am I missing something? > > > On May 22, 9:40 pm, "Carlos Celorrio" <[EMAIL PROTECTED]> wrote: > > 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 > > > -- Rokham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
