W3C

List of comments on “Device Description Repository Simple API” (dated 4 April 2008)

Quick access to

There are 29 comments (sorted by their types, and the section they are about).

1-20 21-29

editorial comments

Comment LC-1972: Section 4.2.1 Evidence Interface : clarification needed
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: 4.2.1 Evidence Interface
assigned to Rotan Hanrahan
Resolution status:

+ Section 4.2.1 Evidence Interface

Is the Evidence interface a generic interface or an specific interface for representing Evidence in the form of HTTP headers?
If it is a generic interface, as I see it, then 4.2.1.1 1. Add Evidence should be repharased to:

AddEvidence(key,value)
Query Evidence (key)
Retrieve Evidence (key)
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1973: Data types supported
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: 4.2.4 PropertyValue Interface
assigned to Rotan Hanrahan
Resolution status:

Regarding section 3 Vocabularies it is said,

"Vocabularies also define the data types of values associated with their Properties. The data types supported are boolean, int, long, float, double, String and String[]"

It should said clearly that String[] is used to represent enumerations ...
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1963: 4.3.1.1 Making text more clear (section titles)
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: 4.3.1.1 Create Evidence
assigned to Rotan Hanrahan
Resolution status:

This is an editorial comment on Section 4.3.1.1

The title of the sections and the descriptions of method should be changed to:

"Create HTTP Evidence", "Create Empty HTTP Evidence", "Create HTTP Evidence fromMap" respectively
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1957: newHttpEvidence(Map<String,String>)
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: Create Evidence from Map public Evidence newHTTPEvidence(...
assigned to Rotan Hanrahan
Resolution status:

Regarding the method

Service.newHttpEvidence(Map<String,String>)

this method will force implementations of the DDR Simple API to execute on Java 1.5 and above.
This fact will avoid existing solutions deployed on Java 1.4 to migrate to the DDR Simple API. As sometimes in production environments it is difficult to do a migration due to dependencies with legacy applications, sys admin policies, etc, etc, this seems to be a critical issue. That's because we are requesting to change it to newHttpEvidence(Map)

Proposed Amendment

+ Change Service.newHttpEvidence(Map<String,String>) to Service.newHttpEvidence(Map)

In the description of the method it should be said that implementations must iterate over the keys of the map calling the toString method to obtain the header names, and must iterate over the values of the map calling the toString method to obtain the header values.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1961: 4.3.2.2 empty value
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: 4.3.2.2 Return the Values of a Specific List
assigned to Jo Rabin
Resolution status:

In 4.3.2.2 it is said

"Return values for all the supplied Properties, returning empty values for those that are not known."

¿What is an empty value? It is needed to clarify.

If a PropertyValue has the value "" is it also an empty value?

If a PropertyValue which is in an enumeration has no elements in the enumeration is it also an empty value?
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1948: Interpretation of getAPIVersion()
Commenter: Rotan Hanrahan <rotan.hanrahan@mobileaware.com> on behalf of MobileAware (archived message)
Context: Get Implementation Version public String getAPIVersion();...
assigned to Matt Womer
Resolution status:

Regarding the getAPIVersion() method, described here:

http://www.w3.org/TR/2008/WD-DDR-Simple-API-20080404/#sec-Service-getAPI
Version

The definition says:

"Returns information about the implementation of the API including the
current version."

Our development team wish to know if this information is intended to be
machine readable. In the absence of a statement to this effect, the only
valid interpretation is that the returned String is intended to be read
by a human, presumably for diagnostics purposes.

Proposed amendment:

The team also notes that in addition to getting diagnostic information
about the API implemented by an instance, it may also be of benefit to
get a machine-readable indication of the API to which the implementation
claims conformance. The proposal is to add a method:

Public String getAPINamespace();

In the case of this API, the returned value would be:

"http://www.w3.org/TR/DDR-Simple-API/"

On behalf of MobileAware Ltd, Development Team,

Dr Rotan Hanrahan
Chief Innovations Architect
MobileAware
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1960: Section 4.3.3.2 : Making a more clear text
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: 4.3.3.2 List Available Properties
assigned to Rotan Hanrahan
Resolution status:

This is an editorial comment

Original text:

----
"Lists all known Properties and Aspects in all Vocabularies that may be used without causing a NameException to be thrown. The order in which Properties are listed is not significant."
-----

Proposed Amendment:

"Lists the combination of all known Properties and Aspects in all Vocabularies that can be used without causing a NameException to be thrown. The order in which Properties are listed is not significant"
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1950: Link to core vocabulary
Commenter: Rotan Hanrahan <rotan.hanrahan@mobileaware.com> on behalf of MobileAware (archived message)
Context: B Normative References
assigned to Kevin Smith
Resolution status:

The DDR Simple API requires that Vocabularies indicate the default
Aspect to be used for properties therein (presumably only applicable
when a Property can have more than one Aspect). The document contains a
link to:

http://www.w3.org/TR/ddr-core-vocabulary/

It is observed that this referenced document does not, at present,
adhere to the requirement specified in the DDR Simple API and is
therefore an invalid reference.

The development team request information from the DDWG as to its
intentions to update the published vocabulary to be in compliance with
the DDR Simple API, or if the DDR Simple API intends to reference
another document.

Proposed remedy:

The DDWG should publish an update of the Core Vocabulary, and the DDR
Simple API should link to it via a dated URL.

On behalf of MobileAware Ltd, Development Team,

Dr Rotan Hanrahan
Chief Innovations Architect
MobileAware
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1975: Obsolete URL in references
Commenter: José Manuel Cantera <jmcf@tid.es> on behalf of Telefónica I+D (archived message)
Context: B Normative References
assigned to Rotan Hanrahan
Resolution status:

This is an editorial comment,

The reference to the XML Namespaces spec is obsolete

It points to http://www.w3.org/TR/1999/REC-xml-names-19990114/

However it should point to:

http://www.w3.org/TR/REC-xml-names

The same occurs when the NC-Name syntax is referenced on section 3 (http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName)
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

1-20 21-29

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org