Re: Requirements Document (pubrules stuff)

On Thu, 2002-02-07 at 10:46, Jeff Heflin wrote:
> The draft requirements document is now available for your review at:
> 
> http://km.aifb.uni-karlsruhe.de/owl/

Jeff, 

Regarding formal tech report publication constraints...
I agreed to take a look and either send changes for
you to make or figure out how to edit it myself;
I think it's going to be pretty easy for you to
make the fixes.


We have a tool that checks most of our publishing
requirements; it's really cool:

  http://www.w3.org/2001/07/pubrules-form

e.g. checking the above document gives

http://www.w3.org/2000/06/webdata/xslt?xslfile=http://www.w3.org/2001/07/pubrules-checker&doc_uri=http://km.aifb.uni-karlsruhe.de/owl/&auth=proxy&xmlfile=http://cgi.w3.org/cgi-bin/tidy?docAddr=http://km.aifb.uni-karlsruhe.de/owl/


These look pretty easy to fix; don't worry
about the this-version/latest-version stuff yet:


Document checked: Web Ontology Requirements

    * Is the last stylesheet used the W3C one?yes
    * Is there a <div class="head"> section?:yes
    * Is the W3C Logo correct?no : The errors are:
          * Attribute alt in has the incorrect value (should be W3C
          * Attribute src in has the incorrect
valuehttp://km.aifb.uni-karlsruhe.de/owl/w3c_logo (should be
http://www.w3.org/Icons/w3c_home
    * Are the title in <title> and <h1> the same?yes
    * Is the dated status subtitle correct?yes (Working Draft Feb 7,)
    * Are there errors in the copyright:
          * No mention of the year of the document (pm20) in the
copyright ( Copyright ©2002 W3C® (MIT, INRIA, Keio), All Rights
Reserved. W3C liability, trademark, document use and software licensing
rules apply.)[check they match]
          * No other errors found
    * Is there a <hr/> after the copyright?yes
    * "Latest version" link not found
    * "This version" link not found
    * "Previous version" link not found Something seems wrong, exists.
    * Is there an Editor or Author section in the head of the
document?yes (Jonathan Dale, Jeff Heflin, Raphael Volz, )
    * If there is an abstract, is it marked up by <h2>?yes
    * Is there a status of the document and is it correctly marked
up?yes
    * Does the status section contains a link to the TR page?yes
    * Does the status section contains a email feedback link?no (no
mailto: link found)
    * List of heading without ids (note that the title, the subtitle,
the Status of the document and the abstract are not required to have an
id):
          * heading without id found:Web Ontology Requirements
          * heading without id found:W3C Working Draft Feb 7, 2002 1:30
pm
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * heading without id found:Supported Tasks:
          * heading without id found:Justification:
          * heading without id found:RDF Support:
          * No other heading without ids found
    * Is the document HTML valid?no
    * Is the document CSS valid?yes
    * Is there no relative link using "../"?yes

Hmm... HTML validation problems... 
http://validator.w3.org/check?uri=http://km.aifb.uni-karlsruhe.de/owl/

those look pretty trivial too.

I strongly suggest using XHTML.
Use
	tidy -asxml -n -i -ascii
to take pretty much any sort of HTML and produce
spiffy-clean XHTML.

  http://www.w3.org/People/Raggett/tidy/



-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Wednesday, 13 February 2002 17:25:03 UTC