- From: Christine Golbreich <cgolbrei@gmail.com>
- Date: Wed, 11 Mar 2009 23:25:41 +0100
- To: Sandro Hawke <sandro@w3.org>
- Cc: public-owl-wg@w3.org
- Message-ID: <b0ed1d660903111525xb330e70ma83310e0fdb9011a@mail.gmail.com>
I'm not sure of the order of the references, does it correspond to the order of occurence in the text ? This isn't crucial either, but what about bringing NFR (whatever its abbreviation) closer to his OWL 2 friends rather than leaving it alone as the last (but not the least ... ) ref after OWL 1 ref ? About the Roadmap placement, I perfectly understand the focus of Overview, but we also need to provide an "How to read the documentS?" with an easy and obvious access to it. I'll survive if it remains at the end, but to answer those who say that we already have a TOC: the TOC at the beginning of the Overview is the TOC of the Overview chapter, *not* of the whole book. I remind that we have got explicit LC comments (2 or more) asking for a Reading Guide. those who asked it may prefer to directly find the Roadmap (plus a friendly text), without having to dig until the end of the Overview to discover it. Christine 2009/3/11 Sandro Hawke <sandro@w3.org> > > This isn't critical path for this publication round, but one of the > things about our documents that still bugs me a lot as a reader is how > bibliographic references are done in the text. I already complained > about "[OWL 2 Structural Specification]", but let me quote a few bits: > > ... is defined in the OWL 2 Structural Specification document [OWL 2 > Structural Specification]. .. > > ... The OWL 2 New Features and Rationale document [OWL 2 New > Features and Rationale] describes all the new features of OWL 2 ... > > ... (see Section 2.1 of the OWL 2 Conformance document [OWL 2 > Conformance] ... > > In that last case, you have to click on the link to the bibliography, > click on the link to Conformance, then scroll down to find Section 2.1. > That's crazy. > > How about this: > > 1. Let's avoid "the OWL 2 <something> document"; just give the > title, and make it a hyperlink directly to the document (which > helps make it clear it's a title). For sections, link to the > section. > > 2. Pick short (necessarily cryptic) names for each document, for use > in linking to the bibliography. My suggestions: > > OWL2SS Structural Specification and Functional-Style Syntax > (or OWL2STRUC) > OWL2DS Direct Semantics > OWL2RS RDF-Based Semantics > OWL2CONF Conformance > OWL2MAP Mapping to RDF Graphs (or OWL2RDF) > OWL2XML XML Serialization > OWL2PROF Profiles > OWL2QRG Quick Reference Guide > OWL2NFR New Features and Rationale (or OWL2NEWF) > OWL2MANC Manchester Syntax (or OWL2MS) > > So the above bits would look like this (where I've used "_" to try to > show where parts are links): > > ... is defined in _OWL 2 Structural Specification_ [OWL2SS] .. > > ... _OWL 2 New Features and Rationale_ [OWL2NFR] describes all the > new features of OWL 2 ... > > ... (see _OWL 2 Conformance, Section 2.1_ [OWL2CONF]) ... > > Okay? Can we do something like this? > > -- Sandro > > -- Christine
Received on Wednesday, 11 March 2009 22:26:23 UTC