W3C home > Mailing lists > Public > public-grddl-wg@w3.org > September 2006

Re: Use Cases Version 1.28 - Including terminological changes and Glossary section

From: Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>
Date: Thu, 7 Sep 2006 09:54:35 -0400 (EDT)
To: public-grddl-wg@w3.org
Message-ID: <Pine.GSO.4.60.0609070917490.19950@joplin.bio.ri.ccf.org>

Thanks Fabien,

I have one last round of minor edits for the Healthcare usecase and 
suggestions for the  Glossary section:

## Usecase Edits ##

1) "Kayode, a developer for a clinical research data management system, 
uses XML as their "
             ^^^^^
to

"Kayode, a developer for a clinical research data management system, uses 
XML as the "

2) "submits the XML document to a unique URI for each such record using the HTTP PUT method."
                                                                   ^^^^^^^^^^^^^^
to

"submits the XML document to a unique URI for each such record over HTTP"

3) "Kayode designs a web-based user interface that works with a GRDDL Processor and picks"
                                                                                 ^^^
to

"Kayode designs a web-based user interface that works with a GRDDL Processor which picks"

## Glossary Edits ##

GRDDL Processor
     a GRDDL processor is a software able to identify the GRDDL transformations specified in a GRDDL source document
     and run them to extract RDF.

I prefer to refer to a GRDDL processor as a software agent (or a 
distributed agent more specifically), since the term suggests something 
specific [1]: software that acts for a user or a program.  One of the 
subtle things I like about GRDDL is that it essentially provides a framework for 
distributed software agents.

GRDDL Transformation
     a GRDDL transformation is a code that which, when applied to a
     compliant GRDDL source document, allows a GRDDL Processor to extract RDF from this document.

I'd suggest 'is an algorithm which' since we seem to be consistent in 
refering to the transformations as algorithms (at least in the current authors draft of the spec)

On a different note, Fabien, I've been curious about which tool you use to 
create the diagrams in that use case document.  I'm a big fan of using 
diagrams to communicate things that aren't neccessarily obvious and I 
really like the diagrams in that document.  My favorite tool for that kind 
of thing is Inkscape, but unfortunately it doesn't have a gallery of 
common shapes such as the ones you have in your diagrams.

[1] http://en.wikipedia.org/wiki/Software_agent

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, 7 September 2006 13:54:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:39:08 UTC