30 Aug 2005


See also: IRC log


Shadi, Sandor, Chris, CarlosI, Nick, Charles, Johannes


Assertor Class

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2005Aug/0047

Shadi: comments on the proposal?

<niq> http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20050825

<niq> example 4, you're in two minds

<niq> <earl:PersonUsingTool ...> ... </earl:Assertor>

<niq> chaals?

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2005Aug/0047

chaals: seems like a lot of verbiage. Not sure that we need it all, but I don't see anything wrong with it.

niq: At first glance I like it.

<niq> not me guv

shadi: this is meant to be clearer than having an Assertor represent a single Assertor.

s/single assertor/either a single person, tool, or compound assertor

<niq> I like a compound assertor that'll deal with complex cases like

<niq> - tool highlights X on every page

<niq> - webmaster determines that's a sitewide policy that isn't a problem

<niq> - assessor makes individual comments on particular pages

<niq> for different levels of assertor

RESOLUTION: we will go with this proposal for now.

Report Class

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2005Aug/0049

Shadi: If there is a class that can be used already maybe we shuld do that. But the idea is to have a wrapper for a collection of assertions that belong together.
... you might also want to define assertins that go together for a collection in a large store.

chaals: I don't think this is particularly useful, it mimics the results of a query for some given query. I think creating a class for that is just bloat.
... I can't imagine we would bother implementing this.

shadi: yes it is miimcking a query. This can be put into a repository, and reports generated can be queried

johannes: I think I don't need it now, but may be useful later

Shadi: A file is not really a report - sometimes a report will be drawn from bits of several different files.

RESOLUTION: We will drop this for now

Additional Properties

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2005Aug/0048

shadi: includes some properties that need to be understood in this part of a graph - for example if people are using XML parsers not RDF parsers.
... and then there is the hash proposal, for a checksum or similar.
... this one seems like a can of worms. Maybe we should leave it for a later draft.

chaals: should leave hash for later draft.


RESOLUTION: Hash / checksum / etc is an issue for after this draft.

Shadi: What about the DC properties that can be used

chaals: don't care either way.
... think it is bloat, but no problem

johannes: OK

<niq> nevermind

RESOUTION: Put the DC properties as optionals, as per proposal.

F2F Registration

shadi: Face to face agenda is out, registration is open, please sign up.
... Map of the area?

johannes: There are online map tools - will post a link.

<niq> I've found the area, but there isn't a street address for it!

Location Class

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2005Aug/0056.html

chaals: something looks not quite right, but I can't figure it out here and now.

shadi: let's leave it out for now and work out how to publish a draft...

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2005/08/30 16:59:54 $