Liddy wrote...
> > I see that in your version of the description at
> > http://dublincore.org/architecturewiki/MoreCarefullyThought
> you have
> > included
> >
> > Statement (
> > Property URI ( a4a:adaptability )
> > Value URI ( <"visual", "auditory", "keyboardOnly",
> > "structuredPresentation", "peerInteraction"> )
> > )
> >
> > which in reality would have to be split out into separate
> components
> > like this
> >
> > Statement (
> > Property URI ( a4a:adaptability )
> > Value String ( "visual" )
> > )
> > Statement (
> > Property URI ( a4a:adaptability )
> > Value String ( "auditory" )
> > )
> >
> > Can you give me a human sentence which says in words what you think
> > this metadata statement is saying.?
> The long statement, when these terms could not be taken from
> a thesaurus that would 'hold their meaning' would be:
>
> "This resource contains content that is perceived visually
> and auditorily. It can be controlled using only a keyboard or
> keyboard emulator, is structured so that it can be displayed
> using only headings, etc, and it contains a tool for peer
> interaction (such as a chat facility)."
> These are all characteristics of a resource that are known to
> be of concern to a user with limited facilities due to
> disabilities or device or context limitations.
I don't disagree with your final sentence. However, the problem here is
that we are looking at a fairly broad range of characteristics -
perceptionMode, controlMode, structuralFeatures, functionalFeatures (or
somesuch).
It is much better to separate out these characteristics using several
properties - not least because doing so will make the semantics of each
much clearer. Otherwise we get into what I tend to think of as the "DC
Format problem". Very different kinds of values lumped together in the
same property. This makes machine processing very difficult or
impossible.
Andy
--
Head of Development, Eduserv Foundation
http://www.eduserv.org.uk/foundation/
[log in to unmask]
+44 (0)1225 474319
|