[Sugar-devel] Object Bundles review and inclusion to 0.86/Feature_List request

[Samuel Klein]

Interop is important. It would be useful to be interoperable with the
default OCW format as well : an imsmanifest xml file in the root
directory.

I'd recommend eventually moving to a manifest format that supports
including a number of other files -- so whatever location Sugar / the
Journal looks for this info, it could include a link to other partial
manifests.  Then converting these other formats to .xo would be a
matter of creating a top-level metadata file - .info or otherwise -
which could be automatically generated by a script looking in a dozen
canonical spots for similar sets of data.

SJ


On Wed, Jul 29, 2009 at 8:34 AM, Martin
Langhoff<martin.langhoff at gmail.com> wrote:
> On Wed, Jul 29, 2009 at 9:12 AM, Aleksey Lim<alsroot at member.fsf.org> wrote:
>> ..and in my mind the purpose of OB was keeping metadata while tranfering
>> Journal objects between sugar-nonsugar-sugar not broader meaning
>
> well, file/content exchange! :-) If we are going to write the code for
> a format, and we can write our own, vs use a popular existing standard
> that opens doors to interop...
>
>
>
> m
> --
>  martin.langhoff at gmail.com
>  martin at laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>