- From: Dan Connolly <connolly@w3.org>
- Date: Mon, 26 Mar 2001 08:36:59 -0600
- To: www-mobile@w3.org
In the cc/pp spec, http://www.w3.org/TR/2001/WD-CCPP-struct-vocab-20010315/ I see three namespaces: <!ENTITY ns-ccpp 'http://www.w3.org/2000/07/04-ccpp#'> <!ENTITY ns-ccpp-proxy 'http://www.w3.org/2000/07/04-ccpp-proxy#'> <!ENTITY ns-ccpp-client 'http://www.w3.org/2000/07/04-ccpp-client#'> and I see that there are schemas available at those addresses, if I dig around. If I visit them with my browser, I get an HTML document that links to the spec, but not to the schema(!). I can get the schemas by doing: wget --header="Accept:text/xml" http://www.w3.org/2000/07/04-ccpp-client but there are no clues to that effect anywhere in the spec. Please inform users what accept headers they need to use to get the schema. (Unfortunately, the RDF specs don't yet specify things like format negotiation and MIME types for RDF; we plan to address that soon: http://www.w3.org/2000/03/rdf-tracking/#mime-types-for-rdf-docs ) Please make it easier for developers to grab the schemas; link to them using <a href="...">...</a> links. Also, let them know the name of the RDF version of the schemas, e.g. http://www.w3.org/2000/07/04-ccpp-client.rdf But hmm... using that address defines different terms; e.g. rdf:ID='device-identifier' becomes http://www.w3.org/2000/07/04-ccpp-client.rdf#device-identifier so you might change the schema to say rdf:about="04ccpp-client#device-identifier" in stead. Some folks in www-rdf-interest have suggested that best practice is to use all absolute references: rdf:about="http://www.w3.org/2000/07/04ccpp-client#device-identifier" If at all possible, make the examples available via HTTP and link to them, ala the SVG spec: http://www.w3.org/TR/SVG/struct.html -> http://www.w3.org/TR/SVG/images/struct/StandAlone01.svg -- Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 26 March 2001 09:37:02 UTC