Hi Liddy,
 
Judy Ryan is on long term leave. Would you please remove her from the DCMI email list. Thanks.
 
Ken Ryan

________________________________

From: DCMI Accessibility Group on behalf of Liddy Nevile
Sent: Tue 28/02/2006 12:34 AM
To: [log in to unmask]
Subject: Re: Relations between versions and adaptations



Andy, the difference between a version and an adaptation is that a 
version is the same content in another format or form whereas an 
adaptation is something that adapts the content but is not suitable 
as a complete substitute for it.

The second question in here is whether to use adaptation and then 
specify what kind or to roll that into one by saying textAdaptation 
or visualAdaptation ...that is a different issue ...

For adaptability, we want to know the difference between a complete 
alternative version and an adaptation...

Liddy


On 26/02/2006, at 8:36 PM, Andy Powell wrote:

> Liddy,
> looking at your modified version of my example at
> http://dublincore.org/architecturewiki/MoreCarefullyThought I'm 
> confused
> by some of the relationships you indicate.  To simplify your 
> example, it
> says
>
> bar.html --hasVersion--> bar.txt --hasAdaptation--> bar.mp3
>
> Can you explain the difference here between hasVersion and
> hasAdaptation?
>
> In my example I proposed using
>
> bar.html --hasTextualAdaptation--> bar.txt --hasAuditoryReplacement-->
> bar.mp3
>
> which (to my understanding at least) captures the fact that bar.txt 
> is a
> textual adaptation of bar.html and that bar.mp3 is an auditory
> replacement for bar.txt.  This information isn't captured in your
> example as far as I can tell.  Your example does say that bar.txt
> 'replaces visual' but it doesn't say what visual resource is being
> replaced.  Furthermore, your example says that bar.mp3 is an 
> adaptation
> of bar.txt, but it doesn't say anything about what kind of 
> adaptation it
> is (though this can be infered from the value of dc:format I guess).
>
> Looking at it now, I think that my example is wrong because my use of
> hasTextualAdaptation mixes up aspects of dc:type and dc:relation 
> into a
> single property.
>
> I'm confused... but I think I'm confused because it is not clear to me
> what we are trying to capture here - nor what funtional 
> requirements are
> intended to be met by this information.  Can you give me an example of
> what end-user (or software agent) actions are supposed to be supported
> by these relationships?
>
> Andy
> --
> Head of Development, Eduserv Foundation
> http://www.eduserv.org.uk/foundation/
> [log in to unmask]
> +44 (0)1225 474319


**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************