12:16:56 <RRSAgent> RRSAgent has joined #er
12:16:56 <RRSAgent> logging to http://www.w3.org/2009/05/13-er-irc
12:16:58 <trackbot> RRSAgent, make logs public
12:16:58 <Zakim> Zakim has joined #er
12:17:00 <trackbot> Zakim, this will be 3794
12:17:00 <Zakim> ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start in 13 minutes
12:17:01 <trackbot> Meeting: Evaluation and Repair Tools Working Group Teleconference
12:17:01 <trackbot> Date: 13 May 2009
12:18:12 <MikeS> Agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2009May/0006.html
12:18:25 <MikeS> Chair: Mike
12:19:15 <MikeS> zakim, agenda+ Publication timeline
12:19:15 <Zakim> agendum 1 added
12:19:58 <MikeS> zakim, agenda+ Pointers in RDF
12:19:58 <Zakim> agendum 2 added
12:20:24 <MikeS> zakim, agenda+ Aggregation
12:20:24 <Zakim> agendum 3 added
12:20:51 <MikeS> zakim, agenda+ EARL 1.0 Requirements
12:20:51 <Zakim> agendum 4 added
12:21:01 <MikeS> zakim, agenda+ Next and future meetings
12:21:01 <Zakim> agendum 5 added
12:25:31 <Zakim> WAI_ERTWG()8:30AM has now started
12:25:38 <Zakim> +MikeS
12:25:53 <MikeS> zakim, +1.512 is MikeS
12:25:53 <Zakim> sorry, MikeS, I do not recognize a party named '+1.512'
12:30:25 <MikeS> zakim, who is on the phone?
12:30:25 <Zakim> On the phone I see MikeS
12:31:33 <shadi> z6akim, call shadi-617
12:31:39 <shadi> zakim, call shadi-617
12:31:39 <Zakim> ok, shadi; the call is being made
12:31:40 <Zakim> -MikeS
12:31:40 <Zakim> +MikeS
12:31:41 <Zakim> +Shadi
12:31:43 <carlosI> carlosI has joined #er
12:32:26 <MikeS> Regrets: CarlosV
12:33:16 <Zakim> +Carlos_Iglesias
12:36:08 <shadi> scribe: Shadi
12:36:21 <shadi> zakim, take up agendum 1
12:36:21 <Zakim> agendum 1. "Publication timeline" taken up [from MikeS]
12:36:27 <shadi> http://www.w3.org/WAI/ER/timeline
12:37:58 <shadi> MS: want to do a full Last Call publication
12:38:13 <shadi> ...need to confirm timeline and plan
12:38:28 <shadi> CI: think we can do it
12:38:41 <shadi> ...maybe the Guide is a little behind
12:38:51 <shadi> ...but otherwise seems reasonable
12:39:58 <shadi> SAZ: same concern about the Guide
12:40:06 <shadi> ...need to confirm with CarlosV
12:40:46 <shadi> zakim, take up next
12:40:46 <Zakim> agendum 2. "Pointers in RDF" taken up [from MikeS]
12:41:03 <shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2009May/0007.html
12:42:26 <shadi> MS: do we need "XML"? isn't it clear from the conext that ptr:Namespace is for XML content?
12:42:30 <JohannesK> JohannesK has joined #er
12:42:34 <Zakim> +JohannesK
12:43:47 <shadi> CI: property could be reused in other contexts
12:44:11 <shadi> ...then it becomes ambiguous
12:44:43 <shadi> MS: even if we flip the order, we may be running against conventions
12:45:06 <shadi> CI: prefer "NamespaceInXML" because it is clearer
12:45:26 <shadi> ...the second option "NamespaceXML" runs into the issue MS raised
12:46:34 <shadi> SAZ: we have same issue in Content-in-RDF
12:46:36 <shadi> ...http://www.w3.org/TR/Content-in-RDF/#xmlContentClass
12:47:11 <shadi> ...need more generic solution
12:47:25 <shadi> MS: don't object to "NamespaceInXML"
12:49:08 <shadi> JK: for Content we could use "WellFormedContent"
12:50:01 <shadi> CI: not sure if this is accurate
12:50:09 <shadi> JK: it has to be well formed
12:54:39 <shadi> SAZ: are there other definitions of namespaces?
12:54:46 <shadi> CI: yes, think so
12:54:55 <shadi> http://en.wikipedia.org/wiki/Namespace
12:57:47 <shadi> SAZ: only used in XPathPointer
12:58:04 <shadi> CI: and XPointerPointer because it is a subclass
12:59:48 <shadi> JK: wonders if this is not a namespace mapping
13:00:32 <shadi> CI: brings the same problem, because we are only focusing on XML
13:01:03 <shadi> MS: but in the context we are in it is restricted by XPointer
13:01:52 <shadi> JK: then we define it to be an XML namespace mapping
13:02:12 <shadi> MS: can also add an editor's note
13:03:43 <MikeS> +1 for NamespaceMapping
13:03:55 <JohannesK> +1
13:03:59 <shadi> Resolution: reame the class to "NamespaceMapping" and add an editor's note in the document for feedback
13:04:10 <shadi> s/reame/rename
13:05:36 <shadi> CI: next issue is about usage of pointers
13:06:14 <shadi> ...propose to add a paragraph explaining that different pointers are more appropriate to different types of content
13:07:32 <shadi> ...don't recommend that we define restrictions
13:08:29 <shadi> SAZ: agree with this proposal
13:08:32 <shadi> MS: me too
13:09:00 <shadi> Resolution: accept proposal to add a new paragraph explaining the usage of pointers
13:10:34 <shadi> CI: removed examples using abstract classes, as per previous discussions
13:12:41 <shadi> CI: next issue is about reusing examples
13:13:06 <shadi> MS: maybe just say something like "referring to example X.Y.Z"
13:13:14 <shadi> http://www.w3.org/TR/EARL10-Schema/#example-6
13:14:02 <shadi> SAZ: Schema doc uses that approach
13:16:20 <shadi> MS: think we had already resolved the XPointerPointer issue
13:16:43 <shadi> CI: don't suggest we should rename
13:16:50 <shadi> ...we'll respond politely
13:16:59 <shadi> Resolution: keep current naming of XPointerPointer because of naming convention
13:17:25 <shadi> MS: any other issues for this document?
13:18:13 <shadi> CI: will provide an editor's draft before the next meeting
13:19:58 <shadi> ...once draft is up, will send responses to commentors
13:20:05 <shadi> zakim, take up next
13:20:20 <Zakim> agendum 3. "Aggregation" taken up [from MikeS]
13:20:52 <shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2009Apr/0032
13:21:58 <shadi> MS: distinguishing three types of "aggregation"
13:22:29 <shadi> CI: "combination" is already provided by RDF
13:23:28 <shadi> ...the other two relate to definition of rules
13:23:43 <shadi> ...which we decided is out of scope for EARL
13:23:46 <shadi> JK: agree
13:24:30 <shadi> MS: don't get "combination" entirely for free
13:26:14 <shadi> ...some tools may provide parts of test results
13:28:28 <shadi> SAZ: there is combination on a level of test results, then on the parts of test results
13:28:49 <shadi> MS: if we only mean combination, do we need a requirement for aggregation?
13:30:14 <shadi> CI: can keep the requirement, but don't think we need to address it any further
13:32:01 <shadi> MS: so tweak wording towards combination?
13:32:26 <shadi> SAZ: it supports aggregation given other parts
13:32:47 <shadi> CI: think should only talk about EARL, so tweak towards combination
13:33:06 <shadi> ...and explain aggregation in the Guide
13:33:21 <shadi> MS: will send one or two wording suggestions
13:34:20 <shadi> Resolution: eliminate aggregation from requirements but mention it as part of combination, and to describe it further in the Guide
13:34:52 <shadi> zakim, take up next
13:34:52 <Zakim> agendum 4. "EARL 1.0 Requirements" taken up [from MikeS]
13:35:09 <shadi> MS: please have a look at that and provide feedback
13:35:22 <shadi> zakim, take up agendum 5
13:35:26 <Zakim> agendum 5. "Next and future meetings" taken up [from MikeS]
13:36:26 <shadi> JK: will be out next two weeks, will prepare something on HTTP-in-RDF and Content-in-RDF
13:36:55 <shadi> trackbot, end meeting
13:36:55 <trackbot> Zakim, list attendees
13:36:55 <Zakim> As of this point the attendees have been MikeS, Shadi, Carlos_Iglesias, JohannesK
13:36:56 <trackbot> RRSAgent, please draft minutes
13:36:56 <RRSAgent> I have made the request to generate http://www.w3.org/2009/05/13-er-minutes.html trackbot
13:36:57 <trackbot> RRSAgent, bye
13:36:57 <RRSAgent> I see no action items
13:36:59 <Zakim> -JohannesK