Comments: Nov 8 2002 CC/PP LC WD

Below are my comments regarding the November 8, 2002 CC/PP LC 
WD [1].

If addressing any of these comments would result in a delay 
in the promotion of this spec to Candidate Recommendation
then please do NOT address the comment but rather catalog
the comment as input for any subsequent release of the spec.

Summary - CC/PP should be a very thin spec - it should define its
framework: the structure (i.e. component-attribute hierarchy 
and defaults) and a schema but that's it.  Everything else
(e.g. vocabulary, datatypes, proxy handling, etc.) should be 
out of scope.

Regards,

Art Barstow
---


* 1. - first par, first sentence - a frequent point of confusion
 is that "profile" is frequently used to denote a subset of a
 specification (i.e. CSS Mobile "Profile").  The spec should
 explicitly state that "profile", in the context of this document,
 is not the same as the more common usage of the word.

* 1.3.2 - remove the RDF tutorial info and instead refer to the
 relevant RDF specs/docs (e.g. RDF Primer [2]).
 
* Get CC/PP added to the [2]'s list of RDF Applications.

* The use of casing for RFC2119 is inconsistent.  In 1.1
 upper case is used whereas in other sections (e.g. 2.1.4
 "optional", lower case is used.

* Should explicitly state whether Appendices are Normative
 or Informative.

* 2. - there is too much redundancy with the info in this section
 and section 3.  In the spirit of "less is more" and simplicity
 is good:

  * 2.1.1 - move everything in this section to 3.1.1

  * 2.1.2 - move everything in this section to 3.1.2

  * 2.1.3 - move everything in this section to 3.1.3

  * 2.1.4 - move everything in this section to a new
   INFORMATIVE chapter on Proxies.  [I'd be OK if all of
   the proxy stuff was completely removed and perhaps
   put in a W3C Note.]

* 2.2 - define "CC/PP expression"

* 2.2 - add [RDFSCHEMA] to the RDF Schema reference to clarify
 the reference is to the Mar 2000 CR (and not any of the WDs
 in progress).

* 2.3 - remove all of the RDF tutorial info in this section (and
 subsections); alternatively, add references to the relevant RDF 
 specs/docs.

* 3.2 - move all of this stuff to a new chapter on Proxies
 (include any info from 2.1.4 that is not redundant).

* 4. - CC/PP is going beyond its scope to define specific 
 datatypes.  It should only define a framework (e.g. the 
 structure) and leave vocabulary and datatype definitions
 to applications or instances of the CC/PP framework.  
 
 Given there are no instances of CC/PP profiles (AFAIK)
 and no community has adopted the Attribute Vocabulary (AFAIK)
 remove this section and explain that defining Attribute 
 Vocabulary is application-specific (and perhaps add references to
 applications that have defined such vocabularies).
 
* 6.1 - RDFSCHEMA - add this doc is a Candidate Recommendation

* 6.2 - there appears to be a formatting bug in the UAPROF ref

* Appendices - clearly mark each of these as Informative
 or Normative

* B.3 - remove the datatype definitions from the core schema.
 I would not define these datatypes anywhere but if they must 
 be defined, put them in a separate schema.

* B.3 - why are there two definitions of the anyURI Class?
 Which definition is resolved when an application refers to
 ccpp:anyURI?  

* C. - instead of using "mandatory", use RFC2119 language.

* D.1 - add a definition of "CC/PP parser" 

[1] http://www.w3.org/TR/2002/WD-CCPP-struct-vocab-20021108/
[2] http://www.w3.org/TR/2002/WD-rdf-primer-20021111/

Received on Tuesday, 26 November 2002 10:29:39 UTC