Liddy Nevile wrote:
<blockquote>
instead of a report that claims to define how accessible or otherwise a resource
is, this element is
used to define the characteristics of the resource that are relevant to
accessibility.
</blockquote>
OK, now I understand. So your current scope for the data model is that outlined
under "IMS AccessForAll Meta-data Information Model"
<http://www.imsglobal.org/accessibility/accmdv1p0/imsaccmd_infov1p0.html>, correct?
Presenting this data is great - I can search for media with subtitles, etc., a
big step forward. However I feel that we are left adrift a bit when it comes to
[WCAG] compliance. Is there not scope here to add to the data model some sort
of pointer to a compliance statement, or would this be part of a remit of
another Dublin Core subgroup? I see something that sits at the same level as
the class [has_visual|has_audio|...] under the parent "accessibility" class. If
we've got that top level class, surely we have room...
Whilst the IMS stuff could be of direct use to a client, metadata relating to
compliance can be of indirect benefit. Compliant material is more likely to be
machine-readable and thus useable by software agents that may be aggragating
data for a client.
Cheers
M
--
Matthew Smith
Kadina Business Consultancy
South Australia
Outside temperature: 12.2 degrees Celcius.
Wind due SW, 10.6km/hr gusting to 14.5km/hr
Temperatures today (avg/max/min): 19.1/ 32.9/ 12.2 degrees Celcius.
Max wind speed today 24.8km/hr at 14:40
Precipitation today: 0.508mm
|