W3C home > Mailing lists > Public > public-swbp-wg@w3.org > January 2006

RE: [VM]

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Tue, 10 Jan 2006 18:23:58 -0500
Message-ID: <A5EEF5A4F0F0FD4DBA33093A0B075590097B6758@tayexc18.americas.cpqcorp.net>
To: "Miles, AJ (Alistair)" <A.J.Miles@rl.ac.uk>, <public-swbp-wg@w3.org>

Alistair,

I think the diagrams are helpful!  They are not quite what I intended in
my E2[1] though, so my E2 comment may still be relevant.  My intent was
to suggest saying something (very brief) at the *beginning* of the
recipe, as a way to help the reader select the appropriate recipe.  For
example, in recipe 4 you might say something like:
[[
	http://isegserv.itd.rl.ac.uk/VM/http-examples/example4/classA
is 303-redirected to
	
http://isegserv.itd.rl.ac.uk/VM/http-examples/example4-content/2005-10-3
1.html#classA
or to 
	
http://isegserv.itd.rl.ac.uk/VM/http-examples/example4-content/2005-10-3
1.rdf
depending on the content type requested.
]]

I do have one minor suggestion regarding client/server diagramming
conventions.  In client-server diagrams, I personally think it is better
to standardize on having the client on the left and server on the right.
The reason for this is that most interactions are intiated by the
client.  Thus, having the client on the left yields more of a
left-to-right flow than if the server is always on the left.  (If you
number the actions you will see what I mean.)  Obviously, this is a very
minor issue, and to a large extent it may simply reflect a matter of
personal taste, but I offer this rationale in case it resonates.  Feel
free to ignore it.

Thanks!
David Booth



> -----Original Message-----
> From: Miles, AJ (Alistair) [mailto:A.J.Miles@rl.ac.uk] 
> Sent: Tuesday, January 10, 2006 12:47 PM
> To: public-swbp-wg@w3.org; Booth, David (HP Software - Boston)
> Subject: [VM] 
> 
> 
> Hi all,
> 
> David Booth suggests in point E2 [1] that for each recipe we 
> should describe what the URIs actually return. I'd been 
> wanting to find some way of illustrating that graphically 
> anyway, so I added some images to recipes 1-5 illustrating 
> the results of each configuration (see rev. 1.13 of [2]). 
> What do you think?
> 
> Responding to point E1 [1] - how could we make the URIs 
> shorter, given that they should actually work as described 
> and therefore need a supporting server appropriately 
> configured?  I'd rather leave them as is at least for the 
> first WD publication, because the isegserv.itd.rl.ac.uk 
> server is already configured to support them.  
> 
> Cheers,
> 
> Al.
> 
> [1] 
> http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0124.html
> [2] 
> http://www.w3.org/2001/sw/BestPractices/VM/http-examples/2005-11-18/
> 
> 
> ---
> Alistair Miles
> Research Associate
> CCLRC - Rutherford Appleton Laboratory
> Building R1 Room 1.60
> Fermi Avenue
> Chilton
> Didcot
> Oxfordshire OX11 0QX
> United Kingdom
> Email:        a.j.miles@rl.ac.uk
> Tel: +44 (0)1235 445440
> 
> 
Received on Tuesday, 10 January 2006 23:24:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:16 UTC