Ian,

I agree with what you are saying, but I don't think Lucas is
advocating strict adherence to the IMS packaging structure. I think
the IMS package approach is very sound and there is a great deal we
can build upon there.

You mentioned:
> I think we should be looking at more flexible approaches for XIPF -
> for example, a rich XML 'description' or 'declaration' schema with
> the ability to create a randomly accessable package of the whole
> but also the ability to have some content remaining referential and
> unpackaged.

I think this is very sound reasoning. Especially, since we need to
look at where these packages will be played: personal computer, media
centre, mobile devices.
Each package needs to be customized to the device requesting it. Also
"XIPF" - whatever technologies it includes - should be a 'Living
Document' meaning content should be able to be added and removed from
a package throughout time.

For example.
Fan art.
Merchandise coupons/discounts.
Remixes.
etc...

These are the things I would like to see in addition to what we
normally think of as standard Liner Notes.

I'm not sure how this is going to work, but my gut tells me that both
MPEG 21 and IMS Packaging have a roll to play in the eventual
solution. Perhaps, an MPEG 21-ish file is the file sitting on the
users device once they acquire a song. The custom package is served
up from a server depending on what device is requesting the media.






On Jul 6, 2006, at 9:21 PM, Ian Burnett wrote:

> Lucas, all,
>
> IMS is along with SCORM a longstanding packaging approach for learning
> objects. The approach is IMHO an 'early' usage of XML - the XML
> manifest
> file is included in a zip archive. This is not unlike the new
> approach being
> touted by Microsoft (the Open Packaging format) for documents and
> XML paper
> packages and the competing Open Document Formats. These take similar
> approaches of creating zip archives but have advanced the XML
> considerably.
> However, it is interesting to consider whether such approaches work
> for
> multimedia content such as we would see in music releases -
> unpackaging a
> large set of music files is painful and the issue of random access
> to the
> compressed files is important. Also, streamed content is a natural
> part of
> music delivery. Given this, I think we should be looking at more
> flexible
> approaches for XIPF - for example, a rich XML 'description' or
> 'declaration'
> schema with the ability to create a randomly accessable package of
> the whole
> but also the ability to have some content remaining referential and
> unpackaged. These are the features and requirements that, for
> example, MPEG
> has worked towards in MPEG-21 with Digital Items. The spec for
> these is also
> an open standard and is available at
> http://standards.iso.org/ittf/PubliclyAvailableStandards/
> c041112_ISO_IEC_210
> 00-2_2005(E).zip with the schema files for all of MPEG-21 at
> http://standards.iso.org/ittf/PubliclyAvailableStandards/
> MPEG-21_schema_file
> s/. Reference software is also available:
> http://standards.iso.org/ittf/PubliclyAvailableStandards/
> ISO_IEC_21000-8_200
> 6_Reference_Software/21000-2_DID/ .
>
> Regards
>
> Ian
> ________________________________________________________________
> Dr Ian S Burnett
> CTO enikos pty ltd &
> Associate Professor
> School of Electrical, Computer Tel: +61 2 42 213399 / 213065
> and Telecommunications Engineering Fax: +61 2 42 213236
> University of Wollongong
> Wollongong
> NSW email: i.burnett@...
> AUSTRALIA WWW: http://www.whisper.elec.uow.edu.au
> <http://www.whisper.elec.uow.edu.au/>
> __________________________________________________________________
>
>
>
> ________________________________
>
> From: xipf-talk@yahoogroups.com [mailto:xipf-talk@yahoogroups.com]
> On Behalf
> Of Lucas Gonze
> Sent: Thursday, 6 July 2006 10:58 AM
> To: xipf-talk@yahoogroups.com
> Subject: [xipf-talk] prior art: IMS
>
>
>
> http://www.imsproject.org/content/packaging/cpinfo10.html
> <http://www.imsproject.org/content/packaging/cpinfo10.html>
> "The version 1.0 scope of the IMS Content Packaging specification is
> focused on defining interoperability between systems that wish to
> import , export, aggregate, and dis-aggregate packages of content"
>
> "The IMS Package depicted in Figure 2.1 consists of two major
> elements: a special XML file describing the content organization and
> resources in a package, and the physical files being described by the
> XML. The special XML file is called the IMS Manifest file, because
> course content and organization is described in the context of
> 'manifests'. Once a package has been incorporated into a single file
> for transportation, it is called a Package Interchange File"
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor --------------------
> ~-->
> Great things are happening at Yahoo! Groups. See the new email
> design.
> http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/1U_rlB/TM
> --------------------------------------------------------------------
> ~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
>