- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Tue, 07 Feb 2012 14:17:20 +0000
- To: public-rdf-wg@w3.org
The obvious issue to me is SPARQL alignment SPARQL does not have /* ... */ comments. It did at one time - the feature was removed long time ago - DAWG then thought one style of comment was better than two styles. I mildly prefer long comment blocks to look like comments all the way down so that commented out triples are clearly commented out. A large block, that includes triples, can get confusing in that respect. See the common pattern: /* * Text */ On 07/02/12 13:41, Ivan Herman wrote: > The obvious issue is that this will break older turtle processors. That being said, we already have a backward incompatible feature, ie, @base... ?? @base is in the submission - what's changed? 8. is a break though. Andy > > Ivan > > On Feb 7, 2012, at 14:12 , William Waites wrote: > >> >>>> One use case for multi-line (block) comments is mixing text and >>>> data notes in the same document and being easily able to >>>> separate out the two later (see earlier posts in this >>>> thread). When quickly jotting notes the # is inconvenient/ugly >>>> and block comments make convenient chunks for extraction. >> >> I could see this being very useful for vocabulary authors, with >> comment and data/code conventions to make good quality documentation >> for humans. Considered at the surface syntax level, we can still have >> the author's intended ordering and such to make the resulting docs >> more readable. >> >> +1 to block comments. >> >> -w > > > ---- > Ivan Herman, W3C Semantic Web Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > FOAF: http://www.ivan-herman.net/foaf.rdf > > > > >
Received on Tuesday, 7 February 2012 14:20:31 UTC