Action WC: Try another stab at EARL abstract
Action DD: Send perl script for WART to list
Action WC: Look for Perl packages that generate RDF and MIME attachments.
Action WC: Talk with Ralph and Eric about saving/querying EARL with Annotea
Action WC: Implementation plan for WART.
Action SP: Send DD a list of possible places to meet for ER/PF F2F in Brighton (possibly end of 1st week of October or the week of the 15th of October).
CMN: Cross-over between transcoding an accessibility and CC/PP (this is what I can deal with), and EARL (if you've got that type of profile, you probably can't deal with this). Useful approaches to the same problem. CC/PP is about profiles, EARL is about conformance. This collection of checkpoints means conformance to a CC/PP profile. Then they want DAML-OIL stuff - our languages do the same stuff... I don't see EARL having a major role in there
/* WC rereads WL's reaction to initial abstract notes */
CMN: EARL is QA, if go down that road
SP: Wrote XSLT to save EARL in a linear form so could include in a linear data model.
CMN: Why not put RDF in HTML?
SP: No DTD for RDF, no way to validate.
Action WC: Try another stab at EARL abstract.
/* CMN gets DD on the phone to talk about WART */
DD: Join with PF beginning of October in Europe.
Action SP: Send DD a list of possible places to meet for ER/PF F2F in Brighton.
DD: Oxford?
SP: A bit far.
WC: 1 day PF, 1 day ER?
DD: 2 or 3 days, yes. Probably end of week of 1st or week of 15th.
DD: It's a perl script, series of CGI, that send an e-mail to the archive. There is a step where data is gathered and sends e-mail. Instead could generate EARL report. I can send perl script to list.
/* Action DD send perl script for WART to list */
WC: Where is it?
DD: There is a CGI bin directory on tux.
WC: The flow of the forms need to be changed.
DD: Right, comments from a while back that weren't implemented. wai/report/db it gets a dozen or less messages. Where would the EARL piece go? attachments? The mail is text.
CMN: Eric has an RDF database that we could pump into and query another alternative is post as an annotea annotation.
WC: First piece just to generate it.
DD: Would like to see pointer from archive message to eARL, either as an attachment or another URL - pointer. Somehow pointer between EARL and report. Attachment is easiest way. Hopefully perl package to generate MIME attachment easily. Or attach as n3, but harder to read. Perl package for RDF?
/* Action WC look for Perl packages that generate RDF and MIME attachments. */
CMN: Syntax for generating Annotea is simple. Worth working out with them. Eric and Ralph.
DD: Not sure worth it. It's independent. It's reusing it by different tools.
CMN: Annotea will give it a home URI where we can get it from. There will be an RDF document that will be linked. It would also give Jose a target to start looking at how to deal with them in Amaya and Giorgio with usablenet stuff. They have a place to put and get EARL from.
DD: The attachment will give it a URI.
CMN: Annotea will give a typed relationship. Can do an annotea query on a page.
/* Action WC Talk with Ralph and Eric about saving/querying EARL with Annotea */
CMN: Write up an implementation plan to see how reuse with ATAG.
/* Action WC implementation plan for WART. */
Monday, July 9th, 2001 @ the usual time. (20 hours UTC (+1-617-252-1038))
Last Updated: $Date: 2001/07/04 07:37:29 $
by: Katie Haritos-Shea@Work or
Katie Haritos-Shea@Home