W3C home > Mailing lists > Public > public-swd-wg@w3.org > January 2007

[RDFa] Review Use Cases

From: Alistair Miles <a.j.miles@rl.ac.uk>
Date: Tue, 23 Jan 2007 09:43:46 -0500
Message-ID: <45B61F22.2080906@rl.ac.uk>
To: SWD Working Group <public-swd-wg@w3.org>

Hi all, below is a few comments on the RDFa Use cases document [1].

  - General Comments

1. What is the intended function of this document? Is it intended to 
give people a general idea of why and when RDFa might be useful? Or is 
it intended to provide the input to a design process?

Normally a use cases document provides the backdrop to the design of a 
solution. However, because the use cases in this document present a 
fragment of HTML containing RDFa (as currently specified), the 
document presumes a solution.

I suggest that, for each use case, a fragment of HTML be presented 
without any RDFa, and the set of RDF statements that you want to be 
embedded in the fragment be presented separately.

This would give you the beginnings of a set of test cases.

Also, note that because the document contains examples that use RDFa, 
if you change the design of RDFa at all you will have to go back and 
change your use cases document as well.

2. Use case 5 doesn't seem to be an RDFa use case. It is a use case 
for transferring fragments of (any) HTML between applications. The 
only new information it provides is that any RDF statements expressed 
as RDFa in such an HTML fragment should be properly preserved when the 
fragment is transferred.

3. Use case 6 doesn't seem to be an RDFa use case either, because it 
doesn't introduce any new requirements for RDFa. It just says, RDFa 
might be used in semantic wikis.

  - Specific Comments

"chock-full" - is very culture specific language, suggest use 
something more neutral.

"The expressed structure is closely tied to the data" - I don't know 
what this means.

"copied and pasted" - copying and pasting is maybe too specific to UI 
style or user environment, should probably talk about transferring 
data between applications, where "copying and pasting" is a particular 
euphemism for doing this.

"HTML chunks" - "chunks" is very informal terminology. Also title is 
not particularly informative.

End review.

[1] http://www.w3.org/2006/07/SWD/RDFa/scenarios/20070109/
-- 
Alistair Miles
Research Associate
CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Chilton
Didcot
Oxfordshire OX11 0QX
United Kingdom
Web: http://purl.org/net/aliman
Email: a.j.miles@rl.ac.uk
Tel: +44 (0)1235 445440
Received on Tuesday, 23 January 2007 14:44:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:17:27 GMT