Re: Comments on Use Cases draft

On Thu, 21 Sep 2006, Fabien Gandon wrote:
>> 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?

I recently sent [1] a diagram for the XForms-based Webapps usecase that 
*might* be a bit more clear.

>> 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?

Yes, I had specific clarifications [2] for this part:

How about (right after .. being able to query both as XML and as RDF):

"The corresponding XML documents can be transformed into 'other' 
XML dialects, evaluated by XPath & XPointer expressions, cross-linked by XLink
or XInclude, and structurally validated by RELAX NG (or XML Schema)."

>> "...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"?

In the same email I also suggested syndicate as well as 'subscribe to':

'.. that he doesn't want to surf the net to find sites he might want
to subscribe to ..'? or 'he might want to syndicate'

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

How about service address?

>> 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... ;-)

I wonder if linking to their specifications is sufficient than to add them 
to the glossary (which I'd assume is specific to the topic of GRDDL).

[1] http://lists.w3.org/Archives/Public/public-grddl-wg/2006Sep/0148.html
[2] http://lists.w3.org/Archives/Public/public-grddl-wg/2006Sep/0147.html

Chimezie Ogbuji
Lead Systems Analyst
Thoracic and Cardiovascular Surgery
Cleveland Clinic Foundation
9500 Euclid Avenue/ W26
Cleveland, Ohio 44195
Office: (216)444-8593
ogbujic@ccf.org

Received on Thursday, 21 September 2006 16:56:11 UTC