DCO Comments

From UWA
Revision as of 13:23, 20 November 2009 by Jcantera (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Contents

Delivery Context Ontology Last Call Comments

This page records the comments received during the Last Call Period of http://www.w3.org/TR/2009/WD-dcontology-20090616/

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

usableDisplayPixelsX and usableDisplayPixelsY. 

Recommend the definition be changed 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.

Proposed Response

JMCF: Comment Accepted.

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Location

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

Proposed Response

Location properties in this version of the DCO are only intended to absolute location.

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


- 3.1.4 Location Method

Please provide a better definition than "thing." Is it the device?

Proposed Response

JMCF: I propose to change it to: "It represents an specific mechanism used to calculate a location"

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Location Method

Each method property of the location method has the same description: "The
name of a delivery context entity"

This seems unclear. Are you saying that there can only be one location
method and that you must describe one of the instances referred to - i.e.
WSP-CO?

Trying to see how this would be defined. It would be good to provide an
example. It would be helpful if you were to provide an example
representation of a delivery context for a given device based on the
Ontology andput it in a Best Practices Guide. The way this is presented we
may be limiting uptake.

Proposed Response

JMCF: The property common:name refers to the name of a location method, for example A-GPS. The class of the instance represents the kind of location method. For example A-GPS is at the same time an instance of "Assisted Location Method", "TerminalBased" and "Satellite".

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Location Provider

For  verticalAccuracy replace Stimate with Estimate. I assume this is what
you meant. Also replace metres with meters.


Proposed Response

JMCF: Comment accepted

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Location Provider Support

What are the restrictions on availableLocationProviders. Shouldn't some
cardinality rule be provided?

Proposed Response

LocationProviderSupport class is not in the Last Call Version of the DCO. What version are you looking at?

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Point

For Restrictions on GeoCoordinates did you mean to have Functional=1 vs.
=1?

To be clear, does that mean that for a Point you can have it addressed in 1
or more coordinate systems or just
one or both? The use of subproperties is unclear.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Bearer Type

alternativeNames has no restrictions listed. Is this intentional? If there
are no restrictions then we should state so.

Proposed Response

If there are no restrictions listed then it is assumed no restrictions applied. A comment will be added to the "Reading the Recommendation" section.

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Network Bearer Type Names

I looked at A.9. Should the names defined be normative? This is also a
general comment about the specifications. Names are defined in the
appendix. For matching one would think that the names should be normative.
If these names are not normative it will be very difficult for a host
system to match the delivery context. At the very least there should be
wording to state that if the types listed are used the names used SHOULD BE
consistent with those in the appendix.

Proposed Response

Are you referring to NetworkBearerTechnology? Maybe you are reading an old version and not the Last Call version. In this verison we have preferred not to list normatively NetworkBearerTechnology instances. Specific vocabularies based on the ontology may define in the future these instances.

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Pointing Input Type

For coordinates did you mean to have have Function = 1 vs. = 1 for
restrictions?

This should be more explicit. I would like to see added: "A pointing device
is any input device which allows requires the user to point to a physical
location on screen to direct navigation. This would include devices such as
mice, stylus, and touch screens. In these devices there is no touch
physical feedback to the user."

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Tactile Input Type

This needs to be KeyStroke Input. This is essential to integrate
personalization and be in line with W3C Web Content Accessibility
Guidelines.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

Battery

Regarding batteryLevel, does it matter if the computation is rounded up or
truncated. My guess is not but I thought I would ask.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

Orientation

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.

Also, the definition does not state which device this applies to.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

Orientation Support

The definition states the Orientation support for a device. Yet, you
provide only the current and default values for orientation which would
mean that this defines the current state of the device vs. what the device
supports. The name needs to change and/or the definition needs to change.

Proposed Response

The OrientationSupport class no longer exists in the DCO.

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

Character Set
For description you have the name of the delivery context entity. Is there
some standard set? Does case matter? This is too vague.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html

CPU

Processor speed. You say frequency. Is this in Hertz, megahertz, gigahertz?
Please be specific?

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


CPU

You refer to model and vendor but provide no specific characteristics of
the string. Is there case sensitivity? Do you have a standard set. I am
trying to figure out how a matching algorithm my process this given these
are just strings.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Page Markup

I 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?

Should we add the XHTML role attribute and Access element modules as well
as other components we were planning on for mobile device adaptation?

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Web Browser

You mention APIs supported. Are you referring to those that web content has
access to or are you referring to APIs that other applications should have
access to?


Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Web Browser

Is vendor enough for web browser. I vendor may support different web
browsers. For example Mozilla and Firefox are different brand names. Also,
should we have standard values that are cases sensitive?


Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Web Browser
I would like to have a two properties to be added:

supportsWAI-ARIA which would be a 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. I would like to see
the Accessibility API have version numbers as well.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Web Browser Features

This section mentions Java Applets but excludes the Flash Player. These are
plug-ins typically. Where do we specify these separate user agents?

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


6.10

Define what MMS stands for. The specification defines an acronym without a
definition.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Markup Module

This is vague. By module do you mean a module in XHTML modularization?
Please be more explicit - otherwise this may not be implemented with any
consistency.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Device

Under IMEI you have it pronounced as: pronounced /aɪˈmiË/
I have no idea what this means.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


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. That information could be used to represent the units.

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Bluetooth Profile

Are there definitions for the Values? For example, what does "Generic
Access" mean.
Should these be normative?
Should the values have spaces in them? This is also a generic comment.
Should values of strings have spaces?

Proposed Response

Comment

Author: Rich

Reference: http://lists.w3.org/Archives/Member/member-uwa/2009May/0013.html


Environment

You include speed. What units are they in - feet/second, kilometers per
hour? Should this depend on the device type? This is needs to be made
clearer.

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jun/0013.html


Characteristics about the notion of a Display seem to be scattered throughout the ontology, e.g., usablePixelsX and usablePixelsY
 have Delivery Context class as a domain while characterColumns and characterRows have Device class as a domain. Is there a reason 
why these properties do not have Display class (and only Display class) as their domain?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jun/0013.html

Bluetooth stuff is similarly spread across the ontology. My recollection of Bluetooth (from 10 yrs ago) is that it is a type of 
Personal Area Network (as is ZigBee, etc.). If there a reason why Bluetooth is considered part of the Hardware Aspect rather than 
part of the Network Aspect of the device?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jun/0013.html

Here's a nitpick...  Why does Device have a Width property, but not a Height property? Also, is this the width (and height) of the 
overall device or the width (and height) of the display on the device. If the latter, how do you handle devices with 2 displays, like
 my cell phone?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


  The idea of a location provider should be generalized, IMHO. For example, I can foresee other types of external (third party)
 network services emerging for mobile devices. For example, the function of smart cards could migrate into more universal mobile 
devices, and so the idea of a funds provider and/or authentication service may emerge.

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Why is estimatedPosition part of LocationProvider. How does it differ from currentLocation and LatsKnownLocation?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


  General comments on types. (I'm asking this because processing of information will - for some of us anyway - likely be in a 
strongly-typed language):

a.       Is there a reason you use floats and doubles? For example, the notions of Northing, Altitude, PixelAspectRation, etc at 
floats. The notions of a position's Course and Speed are doubles. Is there something about position that required the added precision
 of a double?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


 General comments on types. (I'm asking this because processing of information will - for some of us anyway - likely be in a 
strongly-typed language):

b.      Is there a reason you use both int and unsignedLong for countables? I.e., integer makes sense over unsignedLong when negative
 values needed. However, there is another issue here. If unsigned longs are being used for countables that can get really large, 
e.g., CPU Frequecy, the gain of unsigned long (which can count up to 4,294,967,295)  over integer (which can count up to 
2,147,483,647) is limited. Float may be better, with reasonable 2009 units. For example, assuming that the units of CPU Frequency are
 in units of Hz, even an unsigned long may not be enough. Also, memories of 8GB (with advent of 64 bit machines) are now coming out. 
Unsigned long is not enough. In addition, the use of int for bandwidth may be a problem. There are networks (e.g., OC192 at 9.6 Gbit/s) that already exist, according to Wikipedia.

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


6.       General comments on types. (I'm asking this because processing of information will - for some of us anyway - likely be in a 
strongly-typed language):

c.       Should typicalResponseTime have xs:duration as the type?


Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Why are LongitudeZone and LatitudeZone different types? This is counterintuitive to geo-novice.


Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


What are the assumed units of battery? Charge or energy? Is this obvious?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


From what I can see, an Aspect is something (specifically components) for which the ideas of "supported," "default," and "active" 
make sense. Why are DeliveryContext and Device Aspect subclasses? ... And Environment not? Also, why is Proxy listed directly, and 
indirectly via SoftwareAspect/Program?

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


  The existing property definitions seem to make the nuances of 'supports' explicit, ie. things can be supported, but not available
 (e.g., you might need to download and configure to make a supported item available), things can be available but not active. Of 
the things that are available, some may be part of a default configuration for the device, some may be a part of the preferred 
configuration of the device. However, there appears (to me) to be some inconsistency, re: sub-classing the notion of supports. 
Available is a sub class of supports (makes sense to me). Default is also a subclass of supports.  Seems like default should be a 
subclass of available. Also, there are components that have the notion of preferred. Shouldn't there be a subclass of available 
called preferred.


Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html

soundMode is an object property with device as a domain...  Why is this needed over and above the mute property provided for 
sound-oriented I/O devices (e.g. Microphone and Speaker).

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Are you assuming there can be only one operating system on a device, as suggested by the fact that there is no 
currentOperatingSystem property? PCs can now run multiple operating systems (both via dual boot and virtual machines). This feature
 could conceivably move "down" to mobile devices.

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


There are properties that do not have domains that seem like they should, e.g., height (which should have the same domain as width)
 and version (which, to me, should be a peer to name). Also, I would think that there should be properties that link things like 
PageMarkup, StyleLanguage, ScriptLanguage, and WebBrowserFeature to WebBrowser.  If there is - my apologies, I missed it.

Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Why is the domain for totalMemoryForJavaApps Device? Shouldn't it be JavaRuntimeEnvironment?

Proposed Response

No, because the same device can have different Java runtime Environments installed.

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Why is inputCharacterSets a peer to input device, in DeviceHardware? Couldn't the Char set be dependent on the input device? 
Ditto with outputCharacterSets.


Proposed Response

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html


Both Content Type and Format are provided for in the model.  Seems like these are redundant notions to me and there is an 
inconsistency that arises.  For example, MIME_TYPE_GIF is a ContentType individual while gif87, gif89a, jpeg, png, etc. are 
individuals for ImageFormat.  There is no appearance of content type in the individuals I looked at for specialized formats.

Proposed Response

There are two concepts: MIME Types and formats. They are related, a format can have an associated MIME type but this is not always true. Only well known formats can have a MIME type officially recognized by IANA. On the other hand the same MIME type can be associated to differenr formats, for example image/gif to GIF87 or GIF89A. Furthermore, a format sometimes have more than one MIME Type, for example XML, can have text/xml or application/xml as MIME type.

Comment

Author: Deborra J. Zukowsky

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Jul/0003.html

Things I can't yet figure out
I'm having problems with the whole modeling of networks, network bearers, and location providers. Right now, they seem to be 
modeled as a part of the device, with a special emphasis for currentNetworkBearer (as opposed to currentNetwork).  My model is that
 from the delivery context perspective, there are networks available in the physical environment that may have associated network 
bearers. The device can use these networks based, in part, on available hardware components and the internal configuration of those
 components and what the user wants/needs to do.

Proposed Response

Yes you are right. The presentNetworks property holds the list of networks present in the environment. A device will be able to connect to such networks provided it has the hardware and credentials necessary to do so. On the other hand, the NetworkSupport class contains a set of properties which represent the network support of the device. Particularly, the properties supportedNetworkBearers and supportedNetworkModes convey this information. In addition the connectedNetworks property represents the set of networks to which the device is currently connected.

Comment

Author: Gottfried Zimmermann

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Sep/0001.html


(1) Section 2.2 Normative Language for Conformance Requirements

It is not clear what it means if a class, property or instance is "not
normative".  Suggest saying something like "not normative concepts may be
implemented. If not implemented, these URIs must not be otherwise used."


Proposed Response

Non normative terms in the ontology are included for (a) to help up in the automatic documentation generation process, see for instance, common:disjointClass, (b) to help other communities to identify properties of their interest, see for example, the annotation property relatedUAProfEntity, or (c) to illustrate other possible terms that might be applicable in other contexts, for instance, loc:UTMCoordinates which illustrates how other geolocation reference systems can be seamlessly introduced.

As these terms are non normative, their suggested CURIEs are non-normative, even in the case that a user of the ontology decides to use a custom term with exactly the same semantics as the original non-normative term present in the ontology.

As suggested by the commenter a sentence clarifying this question will be provided.

Comment

Author: Gottfried Zimmermann

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Sep/0001.html


(2) Class MmsClient

The abbreviation “MMS” is not explained in the whole document.


Proposed Response

JMCF: Comment Accepted A definition of the acronym will be provided.

Comment

Author: Gottfried Zimmermann

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Sep/0001.html


(3) Property id

There is a long list of subproperties of common:id?  Why are these
subproperties necessary?  Why not use common:id for all occurrences?


Proposed Response

such subproperties are introduced due to two reasons:

(a) clarity as concreteness allow users of the ontology to refer to terms in a more specific way. (b) to provide a normative reference for certain identifiers. For example, consider the class CharacterSet and the property common:charsetName which it is a subproperty of common:id. This subproperty is affected by a normative reference from IANA which establishes clearly what are the normative values that such a property may have. If we hadn't defined the property charsetName it wouldn't have been feasible to establish such a normative restriction, thus making the specification weak and incomplete.

Comment

Author: Robin Berjon

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Oct/0000.html


I found a small typo at:

   http://www.w3.org/TR/dcontology/common.html#UriScheme

It says "URI Schema" instead of "URI Scheme".


Proposed Response

JMCF: Change is accepted

Comment

Author: Simon Reinhard

Reference: http://lists.w3.org/Archives/Public/public-uwa/2009Oct/0001.html


The OWL file for the delivery context ontology is served at http://www.w3.org/2007/uwa/context/deliveryContext.owl 
and when accessing http://www.w3.org/2007/uwa/context/deliverycontext.owl instead you get redirected to that as well. 
However in the file the base URI is defined as http://www.w3.org/2007/uwa/context/deliverycontext.owl. 
This is a bit misleading. Which of the two is supposed to be the correct namespace? Either the file name + redirect or the 
base URI in the file should be adjusted to that.

Proposed Response

Sent e-mail to the commenter in order to understand the issue better.