See also: IRC log
Date: 3 February 2011
<scribe> Meeting: 188
<scribe> Scribe: Norm
<scribe> ScribeNick: Norm
<ht> With you in 5, sorry
no worries
<ht> How do I feep with exiga (SIP client)?????
Uh.
You twiddle the frobnitz until the perclunk changes pitch
*Then* you twist the big red knob to 11
Hope that helps
<ht> Sigh
<ht> I can dial, but I can't feep
<ht> Will switch to paying for Skype (last time, I hope)
Get out your cereal box whistle?
-> http://www.w3.org/XML/XProc/2011/01/27-agenda.html
Accepted.
-> http://www.w3.org/XML/XProc/2011/01/06-minutes.html
Accepted.
Henry gives regrets; Norm is at risk
Henry: If we leave it as I've
written it, it's just a hint to remind folks that the XML spec
doesn't require much.
... If you wanted to do better, you'd have to enumerate the
infoset items that are required.
... But I can imagine that people will be frustrated if they
have to *both* point to this profile document *and* enumerate
the items.
Vojtech: I wonder if this small sentence opens new freedom in how to interpret this spec.
Norm: I don't think so, it's just more explicit about what isn't being said.
Henry: The question is, should we
put the additional detail in this spec.
... We'd have to make section 3 normative in a way that it
isn't now.
Vojtech: It reduces the number of interpretations.
Henry: I'm not sure it's reasonable.
Norm: Why not?
Henry: Here's an example: the infoset spec has three different properties having to do with prefix bindings, any two of which will do
Norm: So we could say in that case that you have to provide two of the following three properties.
Henry: Does any one know if the widely used processors support the namespace attributes property?
Norm: The Java processors based on JAXP don't.
Henry: Some of the Python one's do. Whether they should or not is an another question.
Norm: I think it would be nice to
do it.
... Henry, would you try to draft it?
Henry: Yes, but it'll take a
little while. I won't know if it's going to be straightforward
or not until I've worked my way further into it.
... I can imagine that it might wind up being a two-dimensional
structure depending on what parts of what specs you
support.
... And what about characters, most specs don't return
individual character information items.
... As you can see, it's going to take a little while to work
it out.
Norm: Ok. I think it's good that we're going to look at this.
-> http://www.w3.org/XML/XProc/docs/xproc-proposed-errata.html
-> http://www.w3.org/XML/XProc/docs/xproc-proposed-template-errata.html
General agreement that the editor got all of them right.
None heard.
Norm: Should I cancel 10 Feb?
Henry: yes.
Norm: Ok. Next meeting is 17 Feb.
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: Norm Inferring ScribeNick: Norm Found ScribeNick: Norm Default Present: Norm, vojtech, [IPcaller], ht Present: Norm Henry Vojtech Regrets: Paul Mohamed Alex Agenda: http://www.w3.org/XML/XProc/2011/02/03-agenda Found Date: 03 Feb 2011 Guessing minutes URL: http://www.w3.org/2011/02/03-xproc-minutes.html People with action items:[End of scribe.perl diagnostic output]