W3C home > Mailing lists > Public > public-sweo-ig@w3.org > November 2007

need editing help on the cool URI document

From: Leo Sauermann <leo.sauermann@dfki.de>
Date: Wed, 28 Nov 2007 11:15:39 +0100
Message-ID: <474D3FCB.8030407@dfki.de>
To: W3C SWEO IG <public-sweo-ig@w3.org>, Max Völkel <voelkel@fzi.de>, Richard Cyganiak <richard@cyganiak.de>
Hi SWEO

We need a little help on the "cool-uris for the semantic web" document.
You can see the status of the work here (things should turn blue, red 
things say I decided not to integrate some feedback)
https://gnowsis.opendfki.de/repos/gnowsis/papers/2006_11_concepturi/feedback/index.htm

Please look at the draft at this URI:
https://gnowsis.opendfki.de/repos/gnowsis/papers/2006_11_concepturi/html/cooluris_sweo_note.html

I would need help with the following issues.
Most important and easy to do for a volantary SWEO member:

    * Review by Native Speaker, (recommended by SWD): Though the overall
      language quality of the document is quite high, it would be good
      to do some spell-checking and language clean-up by a native
      speaker. Just to mention few things noticed at the first sight
      even by a reviewing non-native speaker - the fourth paragraph of
      Section 1 is inconsistent in the tense used (from the sentence "In
      the remainder of this paper..." on - future and present tense are
      mixed); the third paragraph of Section 6.1 contains a typo
      ("resourcse"). 

For this issue, a discussion would be good,

    * issue-non-informationresource web document VS information
      resource. We stand alone (with friendly smiles from timbl) on the
      term "web document", both the SWD and Noah do not like "web
      document". As this is W3C note, we should think about dropping the
      term "web document" from the document and instead only mention it
      at the beginning and then use "information resource" and
      "non-information resource". We should phrase a new introduction
      sentence on the difference, but its tricky to use non-information
      resource for "concept uris" and "information resource" for
      webdocument/ document uris. At the end, everything is information,
      also a document and a concept.

For this, I would ask TAG or SWD for help:

    * example rules of thumb how to distinguish between document
      identifiers and concept identifiers (information and
      non-information resources). Write some wget examples that do that?
      Leo thinks we did not cover the crucial point yet: what is the
      definitive test to get a URI for a non-information resource?
      Range-14 says: "If an "http" resource responds to a GET request
      with a 303 (See Other) response, then the resource identified by
      that URI could be any resource;" Or is this such a problem at all?
      At the end the RDF:Type says what is what.
      I would put that into the 4.6. implementation section.


best
Leo

-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 

Deutsches Forschungszentrum fuer 
Kuenstliche Intelligenz DFKI GmbH
Trippstadter Strasse 122
P.O. Box 2080           Fon:   +49 631 20575-116
D-67663 Kaiserslautern  Fax:   +49 631 20575-102
Germany                 Mail:  leo.sauermann@dfki.de

Geschaeftsfuehrung:
Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
____________________________________________________
Received on Wednesday, 28 November 2007 10:16:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:58 UTC