[DDI-SRG] FW: Issue-DDI3_0-ExternalAidMultimediaRefs_00_00.doc (fwd)

[arofan.gregory]

Wendy:

This contains everything we need. The problem is that, for example,
different video and audio segments take different data types for their
parameters. I suggest we adopt an approach similar to what QDeX uses for
these segment types, since anyone dealing with these things will know what
the proper parameters are for their specific media type.

Cheers,

Aroifan

-----Original Message-----
From: ddi-srg-bounces at icpsr.umich.edu
[mailto:ddi-srg-bounces at icpsr.umich.edu] On Behalf Of Wendy Thomas
Sent: Friday, March 13, 2009 2:22 PM
To: TIC list
Subject: [DDI-SRG] FW: Issue-DDI3_0-ExternalAidMultimediaRefs_00_00.doc
(fwd)

Here is the document Herve sent. The first question I see is how deeply we 
want/need to cover this.

Jeremy...any thought on this in terms of survey instruments?

wendy

Wendy L. Thomas                          Phone: +1 612.624.4389
Data Access Core Director		 Fax:   +1 612.626.8375
Minnesota Population Center              Email: wlt at pop.umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455

---------- Forwarded message ----------
Date: Fri, 13 Mar 2009 20:18:33 -0000
From: "LHours, Herve" <herve at essex.ac.uk>
To: Wendy Thomas <wlt at pop.umn.edu>
Subject: FW: Issue-DDI3_0-ExternalAidMultimediaRefs_00_00.doc

Hi Wendy,



Good to hear from you. Sorry about the late reply.



You'll find a document attached which covers most of the issues we've
considered around this subject to date. Might be overkill for your
purposes but thought it would be better to try and provide as full an
explanation as possible.



In addition to the references to the current METS and QUDEX versions in
the document the two items below outline a couple of open issues around
this subject.  Feel free to come back to  me with any questions and, as
ever, criticisms are particularly welcome



Would like to get an update about your thoughts on DDI & PREMIS at some
point if possible



hmmm, methinks it's time for a beverage, have a good weekend



H




1.     Management of Coordinates


The current structure is based on the METS method, which is in turn
based on html 4 handling of coordinates.  In the next release of QuDEx
we are likely to include an option to define an @ coordinateType in the
area tag permitting the use of pixels, inches, cms etc (preferably
through an explicit list of enumerated types with an 'other' option).
In addition, would it be advisable to split coordinates out into
individual elements to make them more flexible?






2.     Byte Parameter


It would be possible to permit segmenting of text files at the byte
level. This would mirror the application of byte parameters in audio and
video files. Would this be useful or desirable?


<byteParam>


Sub-elements:  none

Attributes:                          id, startByteOffset, endByteOffset



@ startByteOffset: number of bits from the start of the file

@ endByteOffset:



A byteParam defines segments using the byte offsets from the start of
the file