Re: Comments on Use Cases draft

Danny,

Thank you very much for this professional review.
Below are my reactions to some of the points you raised.
Other points have been addressed in version 1.33 of the document.
http://www.w3.org/2001/sw/grddl-wg/doc43/scenario-gallery.htm


Danny Ayers a écrit :
> Ready to publish? I do think a little more work could make a lot of
> difference.
Ok so we must add to the agenda of the next meeting that we had a first 
objection to publication and that changes to the documents must be 
validated before going to the next stage.

>
> Overall pretty good, IMHO the problem if anything is that there's too
> much material, the core use case descriptions could be tighter. It
> might be worth trying a one-sentence summary of each use case (which
> could be used in the contents), then trimming the descriptions of
> anything a long way from that summary.
>
> Having said that, the Introduction is thin...
>
We have had requests in the past to extend the details of the use cases 
and I also remember hearing concerns about use cases becoming too long.
So to accommodate everyone, here is what I did: I removed the 
introduction and merged its content with the abstract; I left the use 
cases detailed and I added a summary for each one of them in the 
abstract. So if readers want the short story they can read the abstract 
and if they want details on a use case they can jump to it.


> I think it's good to include the diagrams (ditto for Primer), though 2
> of them I found not-so helpful (Wikis and e-learning; XForms-based
> Webapps).
Could you give us hints as to what could be done to improve them?

> Pointing to a profile doesn't
> really seem like decoration to me - and is the namespace doc mechanism
> still in the spec? - Invisible decoration?

While I agree that pointing to a profile is not a decoration what is 
said here is that microformat, Embedded RDF or RDFa statements decorate 
the GRDDL source as in the following examples:

Microformat hCard [1]
<span class="tel">
 <span class="type">home</span>:
 <span class="value">+1.415.555.1212</span>
</span>

Embedded RDF with FOAF schema [2]
Hi, I'm <span class="foaf-name"><span class="foaf-firstName">Anna</span> 
<span class="foaf-surname">Wilder</span></span>.
<img style="float: right" src="pic.jpg" class="foaf-depiction" alt="A 
picture of me"/>

RDFa with DC and FOAF schemata [3]

<div about="photo1.jpg">
  This photo, entitled
  <span property="dc:title">Portrait of Mark</span>
  was taken by
  <a rel="dc:creator" rev="foaf:img"
     href="http://www.blogger.com/profile/1109404">Mark himself</a>.
</div>

[1] http://microformats.org/wiki/hcard
[2] http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml
[3] http://www.w3.org/2001/sw/BestPractices/HTML/2005-rdfa-syntax


>
> There's good justification in the paragraphs that follow for throwing
> out their XML representation altogether and just using RDF. The
> primary justification (offered by 4Suite) seems to be getting the
> utility of RDF and XML tools. Perhaps the benefits of the XML side
> could be reiterated?
Chimezie: do you have a suggestion here?


> "...every site he should federate with." - better word than "federate"
> (it's not clear what's intended until a few lines down).
I am probably not the best person to suggest a word but what about 
"syndicate"?

> I've heard reservations of the use of "endpoint" - ok here?
I am not qualified to answer this. Anyone has an opinion?

> There are a few other terms that should probably go in the glossary :
> microformats, RDFa, SPARQL...(I'll see if I have time ;-)
Well, the document includes links linking to specs or docs for all these 
terms but if you insist... ;-)

-- 
"The poet is like this monarch of the clouds riding
 the storm above the marksman's range; exiled on the
 ground, hooted and jeered, he cannot walk because
 of his great wings."   -- Charles Baudelaire.
 ____________
|__ _ |_  http://www-sop.inria.fr/acacia/personnel/Fabien.Gandon/
|  (_||_) INRIA Sophia Antipolis - ph# (33)(0)4 92 38 77 88

Received on Thursday, 21 September 2006 16:36:48 UTC