JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-ACCESSIBILITY Archives


DC-ACCESSIBILITY Archives

DC-ACCESSIBILITY Archives


DC-ACCESSIBILITY@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-ACCESSIBILITY Home

DC-ACCESSIBILITY Home

DC-ACCESSIBILITY  February 2006

DC-ACCESSIBILITY February 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Problems with the proposed adaptability property

From:

Andy Powell <[log in to unmask]>

Reply-To:

DCMI Accessibility Group <[log in to unmask]>

Date:

Sun, 26 Feb 2006 22:51:37 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (63 lines)

In the revised version of my example description based on the proposed
adaptability application profile at
http://dublincore.org/architecturewiki/MoreCarefullyThought the new
a4a:adaptability property is used to carry the following value strings:

"visual"
"auditory"
"keyboardOnly"
"structuredPresentation"
"peerInteraction"
"Textual"
"Replaces Visual"

The proposed label and definition of the adaptability property are as
follows:

Label: Adaptability Statement
Definition:	Characteristics of the resource that affect how it can
be modified for users or agents.

The following thoughts strike me...

If the property value is supposed to be a 'statement' (as the label
suggests, and as 2 of the 4 example values in the proposal show) then it
might be more consistent for the definition to start "A statement of the
characteristics of the resource ..."?  

If the anticipated values are intended to simply be characteristics (as
all but the last value above are), then it might be better if the
proposed label is changed to 'Adaptability characteristics'?

In general, if a property is defined to be 'a statement' but all or most
of the anticipated value strings are single words (or short phrases),
then I think there is a problem.

The proposed comment suggests that an "adaptability statement might be
used to match ..." (implying, I guess, a level of automated matching?) -
I'm struggling to see how free text statements can be used in this way.

Even if the anticipated values are just characteristics (preferably
terms taken from a fixed vocabulary of characteristics) then I fail to
see how one or more such characteristics "might be used to match a
(digital or physical) resource to a description of user or user agent
needs and preferences".  I understand that knowing that a resource has
the characteristic of being 'keyboardOnlyControl' may allow my
user-agent to match that resource against my requirements (because I
don't have a keyboard) but I don't see that as having anything to do
with "how [the resource] can be modified for users or agents" (which is
what the definition says it should be).

Overall, I think there is something potentially useful going on here,
but I don't think the currently proposed term is helpful in moving us
forward - either because it isn't clearly enough defined to be used
consistently or because it is not going to meet the requirements it has
set itself.

Andy
--
Head of Development, Eduserv Foundation
http://www.eduserv.org.uk/foundation/
[log in to unmask]
+44 (0)1225 474319

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

June 2021
May 2021
March 2021
February 2021
September 2020
April 2020
November 2019
September 2019
February 2019
January 2019
May 2018
October 2017
June 2017
May 2017
April 2017
February 2017
June 2016
April 2016
December 2015
October 2015
September 2015
August 2015
July 2015
April 2015
October 2014
September 2014
January 2014
August 2013
July 2013
June 2013
April 2013
February 2013
August 2012
June 2012
May 2012
April 2012
October 2011
May 2011
March 2011
September 2010
November 2009
October 2009
April 2009
February 2009
November 2008
July 2008
May 2008
April 2008
September 2007
August 2007
June 2007
March 2007
February 2007
December 2006
October 2006
September 2006
June 2006
May 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
January 2005
December 2004
October 2004
September 2004
June 2004
May 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager