See also: IRC log
Shadi: comments on the proposal?
<niq> example 4, you're in two minds
<niq> <earl:PersonUsingTool ...> ... </earl:Assertor>
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.
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
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
RESOUTION: Put the DC properties as optionals, as per proposal.
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!
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...