PFWG review of Delivery Context Ontology

Below are comments from the PFWG on Delivery Context Ontology,
http://www.w3.org/TR/2009/WD-dcontology-20090616/. Our resolution to
send these as Working Group comments is recorded at
http://www.w3.org/2009/08/12-pf-minutes.html#item09.


    (1) Property usablePixelsX

Suggest changing definition from:

·         The typical number of pixels in the X direction of the display
which can be used within a delivery context. This may be less than the
total number available due to the presence of additional items on the
display.

to:

·         The typical number of pixels in the X direction of the display
which can be used within a delivery context. This may be less than the
total number available due to the presence of additional items on the
display *or through the application of a clipping region defined by the
windowing system on the device.*

The same applies for property usablePixelsY.


    (2) Class Location

Do you plan on having relative information at anytime? ... Like optional
information that indicates the location relative to another device.


    (3) Property currentOrientation

This definition needs to be more explicit. For example, the values you
provide appear to be in degrees yet you do not specify this in your
definition. Are these degrees running counter clockwise from zero
degrees such as found on a protractor.


    (4) Class PageMarkup

We would like to see WAI-ARIA as an extended page markup. Do we need to
wait until it goes to recommendation or may we add it now?


    (5) Class WebBrowser

We would like to have two properties added with WebBrowser as domain:

·         supportsWAI-ARIA: DatatypeProperty of type Boolean

·         supportedAccessibilityAPI which would then refer to an
AccessibilityAPI class that would include name constant (MSAA,
UIAutomation, IAccessible2, ATK, etc.) These would have a cardinality of
0 or more. We would like to see the Accessibility API have version
numbers as well.


    (6) Class WebBrowserFeatures

Where would we specify supported plug-ins, e.g. Flash?


    (7) Class Environment

Are you planning to add lighting conditions or background noise? This
can be very valuable in determining when automatically adjust the
contrast of content delivered or activating closed captioning in noisy
conditions. Background noise could be defined as the Signal to Noise
Ratio within the frequency band of hearing for a human being. As for
lighting conditions, photographers are able to measure lighting
conditions to adjust the light of a room.


    (8) Class OutputModality

Instances refer to aural and tactile output only.  What about text
output or graphical output?


    (9) Class SoundMode

Instances refer to normal and silence mode only.  How does vibration
alarm fit in here?


    (10) Instance InputModality_TYPING

Suggest to replace:

·         An input modality in whoch the user enters information by
typing using a keyboard or similar

with:

·         An input modality in *which* the user enters information by
typing using a keyboard or *a keyboard-emulating device or method*.

-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>