W3C home > Mailing lists > Public > public-swbp-wg@w3.org > May 2004

RE: Syntax Proposal [All] $swbp

From: Uschold, Michael F <michael.f.uschold@boeing.com>
Date: Mon, 3 May 2004 10:19:03 -0700
Message-ID: <823043AB1B52784D97754D186877B6CF04BA74F3@xch-nw-12.nw.nos.boeing.com>
To: "Pat Hayes" <phayes@ihmc.us>
Cc: <public-swbp-wg@listhub.w3.org>

Pat,

Can you give simple example with an A/B comparison that illustrates your
points?
I am not married to any particular variation, and am interested in
getting the one that best meets our requirements.  

Is there any tool support for the variation you propose? 

Mike


-----Original Message-----
From: Pat Hayes [mailto:phayes@ihmc.us] 
Sent: Friday, April 30, 2004 4:25 PM
To: Uschold, Michael F
Cc: public-swbp-wg@listhub.w3.org
Subject: Re: Syntax Proposal [All] $swbp


>Syntax Proposal:
>It has been moved that we adopt the following
>conventions for SWBPD syntax usage.
>1. In the main content sections of all formal 
>published notes, Turtle/N3 will be used.

I would prefer the 'abbreviated' version of 
Ntriples that was used in the RDF documentation 
(ie allowing qname forms for URIrefs). This is 
reasonably readable but has the merit that it 
shows exactly the triples in the graph, and 
requires one to be explicit about labelling 
bnodes.

Notations  (like RDF/XML and Turtle) which gather 
together triples with a common subject distort 
the logical form and lead to misunderstandings, 
and in fact seem to me to be less readable than 
'flat' notations which exhibit the graph 
structure more explicitly.

I therefore vote against this motion.

Pat

>This meets the requirements that the syntax be
>both human- and machine-readable.

Turtle is neither, seems to me.

>Exception: In some cases, the subject matter is
>best communicated using a different syntax (e.g. 
>the RDF/XML Task Force). This is deemed 
>acceptable on a case-by-case basis for the main 
>content sections of formal published notes.
>
>As appropriate, additional syntaxes may be
>presented in appendices to the notes.
>OPEN QUESTION:
>*	should we make it a requirement that, say 
>all notes at least have RDF/XML in an appendix? 
>-or-
>*	should this be entirely up to the author's discression? 
>
>2.	For regular email exchanges, use of 
>Turtle/N3 syntax remains the recommended
>convention, but is not required to the extent 
>that it causes undue inconvenience. For example:
>*	one's favorite tool may not export Turtle/N3.
>*	there are times when one may wish to dash 
>off a quick example and just type it in some ad 
>hoc informal notation.
>*	the subject matter may be best explained 
>using alternative syntaxes (as above).


-- 
---------------------------------------------------------------------
IHMC	(850)434 8903 or (650)494 3973   home
40 South Alcaniz St.	(850)202 4416   office
Pensacola			(850)202 4440   fax
FL 32501			(850)291 0667    cell
phayes@ihmc.us       http://www.ihmc.us/users/phayes
Received on Monday, 3 May 2004 13:19:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:09:38 UTC