See also: IRC log
k.
<DanC> Scribe: EliasT
<DanC> Welcome Souri of Oracle
http://www.w3.org/2005/07/12-dawg-minutes.html
Next meeting, July 26th.
Scribe for next meeting, EricP.
<DanC> due to KC's regrets, I'm not adding Andy's protocol stuff today
<DaveB> http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0067.html
<DanC> 2 points remaining
<DanC> +1 just a bool
DaveB: We don't need to keep index="number", indicate that results are indexed via a boolean and to indicate distinctness.
<DanC> (hmm... what would it be like to record all the solution modifier stuff? maybe that should get postponed along with XMLAbstractSyntax)
ericP, Andy, Jeen in favor of boolean indicating ordered results.
attribute name is "ordered=true"
DaveB: what should the default be?
ericP: should default to false.
<scribe> unknown: ordered attribute should be mandatory.
<ericP> ericP now in favor of mandatory
<ericP> +1
LeeF: should be an error to have an ORDER BY query without ordered="true" in the results.
<patH> unknown was Pat Hayes
<SteveH> +1 to mandatory
patH: ordered attribute should be mandatory.
ericP: the reason for DISTINCT when someone is consuming a results via a stream.
AndyS: we need to find a principle for adding distinct to the results.
DanC: wonders why is adding ordered different than adding distinct.
AndyS: ordered useful for XSLT presentation of results, can't see the same for distinct
<Zakim> DanC, you wanted to suggest optinal distinct="true" attribute
ericP: in favor of both ordered and distinct being parallel.
DanC: any real scenarios for using ordered/distinct.
AndyS: He has a use for ordered.
<Zakim> Yoshio, you wanted to ask if the result receiver knows something about query
<ericP> Yoshio: if you user knows about the orginal query...
DanC: as per Andy, sometimes yes, sometimes no
Yoshio: in the results format we have the variables used, but not their relationship in the query.
DaveB: the results should not further describe the query.
<patH> Yoshio, I think it is up to the querying agent to keep track of such relationships, if it wishes to do so.
Souri: What are the negatives having also distinct?
DaveB: it makes it inconsistent to have ordered mandatory and distinct optional.
<ericP> Yoshio, patH, a generic XML Results Set to HTML converter would care about @ordered and @distinct but not the query
<Yoshio> my concern is if a query receiver will be happy if he/she just get part of the information of the original query
DanC: DaveB, did you take care of the xsi:type issue.
DaveB: yes, I did so via email.
<DaveB> yeah, gone see http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0058.html
<LeeF> http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0058.html
<DanC> ACTION: DaveB integrate advice on ordered and distinct and propose last call candidate for results set spect [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action01]
<SteveH> I can review it
<scribe> ACTION: LeeF, SteveH and Jeen to review XML results set format. [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action02]
<DanC> Note Well: possible last call decision next week.
DanC: saw recent discussion on regex language.
AndyS: Reg Exp language in XML Schema is not quite the same as XQuery - differences have to do with anchoring
ericP: acknowledges Andy. Thanks.
<DanC> ACTION: EricP clarify which regex lang [continues] [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action03]
DanC: proposes to withdraw CVS logs emailed to mailing list.
ericP: in favor of withdrawing CVS logs action.
<DanC> DONE: PatH to review new optionals definitions, if any.
<DanC> ACTION: DanC to write SOTD; work with EricP to publish [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action04]
<DanC> http://www.w3.org/2001/sw/DataAccess/lc43
<patH> The echo is charming, charming.
<ericP> re removing xsi:type, some relevent lessons in the XML Schema 1.0 User Experiences Workshop report [[
<ericP> Constructs mentioned as falling outside the sweet spot for some or many data binding tools included mixed content, choice, substitution groups, and even simple-type restriction.
<ericP> ]]
<ericP> XML Schema 1.0 User Experiences
<DanC> http://www.w3.org/2001/sw/DataAccess/issues
<ericP> i'll pass the word to C. M. Sperberg-McQueen anyways
DanC: Need to start thinking
about how to justify going to candidate recommendation despite
existing objections such as Network Inference's
... we seems to be all systems go for publication.
Andy, what was your last statement?
<AndyS> I have some mods to make before LC
Thanks.
DanC: Everyone is welcome to review the LC, but we are obliged to get it reviews by certain people, such as W3C chairs.
<DanC> optionals changes pending
LeeF: there's a type in bNodeRef issue.
<SteveH> I can build the tests page again now too
<scribe> DONE: ericP and SteveH can build the tests page in HTML.
DanC: Anybody wants to know how generate the HTML test results page?
<SteveH> no
<scribe> ACTION: DanC to check after August on SteveH regarding test preparation for publication as WG Note [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action05]
AndyS: no progress on AndyS to add the above graph test cases.
DanC: We have to be able to tell
to the world that all of the feature of the spec have been
implemented. I think that until we have tests with documented
results, I won't feel comfortable saying so.
... the other option is to claim that some vendor X has done
so, but in our WG's case it should be better to do it
ourselves.
<scribe> ACTION: DanC to follow up re optional test based on op:dateTime triple [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action06]
<scribe> ACTION: DaveB to to propose source test to approve [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action07]
<scribe> ACTION: EricP to finish extendedType-eq-pass-result.n3 test [recorded in http://www.w3.org/2005/07/19-dawg-minutes.html#action08]
Jeen: finished eating his cookie. (Reason for unmmuting himself)
<DanC> ADJOURN.