See also: IRC log
john: any objections to the minutes?
no objections heard. Minutes approved.
john: schema working group will
not meet in March/April. This gives us opportunity to move our
meeting days if we want.
... does anyone object to keeping the current meeting
dates?
no objections heard. We will keep the same meeting dates.
Pratul: the June meeting may not be held in Zurich because of availability of hotels is unclear.
john: we can decide about June meeting over email. To jump-start that process, folks need to look at (a) whether or not they are likely to get travel approval for Europe (b) which weeks, from mid-June through end of July inclusive, people CANNOT attend. Ideally, send that via email so we do not spend group time getting it straight.
<MSM> [For the record, the address given for a previous meeting at (what I believe is) the same Oracle site is: Conference Center, 350 Oracle Parkway, Redwood Shores, CA.]
<Jim> Suggest someone points out what advantages there might be to meeting in conjunction with the rest of W3C. Also, speculate on where we will be in our process.
john: Date for Pratul's and Kumar's action items that SML is not urgently dependent upon to be updated. The two items in question are informational communication items to other groups, who themselves are not dependent upon receiving our input.
john: when a bug is not marked, we have 3 options: 1) editors can work on such bugs if they think the bug is editorial 2) same as 1 but force such bugs to be marked needsReview 3) editors must not touch such bugs.
jim: proposes #2
john: any objection to Jim's proposal?
no objections heard. Proposal #2 accepted.
john: I believe this is
editorial.
... discussion on the second part of this bug. Empty content
v/s no child elements.
msm: I prefer empty content for both. This reduces confusion.
sandy: does this preclude comments ?
<MSM> E.g. what happens with <sml:data><!--* the actual document should have been here, but is not *--></sml:data>
<MSM> ?
sandy: if comment is present, we cannot call it empty content.
<MSM> [If we retain the current rule, then effectively <base64Data/> must be treated as if the document is not part of the interchange set, but <base64Data><!--* nothing here *--></base64Data> is NOT covered by the rule.
sandy: no child element =>
allows comments/PIs, empty content => does not allow
comments/PIs. we need to fix that inconsistency.
... prefers defining the end result. that is, no document
present after extracting. this should be worded carefully by
the editors.
<Sandy> instruct editors to draft wording to use phrases like "if no document is present" for both "data" and "base64data"; failing that, fall back to use different conditions: no child element for "data" and 0-length base64 for "base64data".
<MSM> [A concrete sketch: something like:
<MSM> If the <data> element has no child element, it is said to contain a
<MSM> 'vacuous document'. If the <base64Data> has a zero-length sequence of
<MSM> octets as its value, it similarly contains a 'vacuous document'
<MSM> If the model/*/document element contains only a vacuous document, then
<MSM> the SML-IF consumer MUST treat the document as if it is not part of
<MSM> the interchange set.
<MSM> ]
msm: xpath2 does not have
node-set. only node-sequences.
... deref() input is node-set, output is node-set. I pass in 7
ref elts. each ref resolves to 1 elt. how many elts are in the
output set? I believe I heard some WG members saying they
expect that there would be 7 elts in the output node-set.
... if the above returns less than 7 then that would surprise
some users.
john: proposal: in the case
above, anywhere between 1 and 7 elts are returned.
... the above requires removing dup nodes from the output
nodeset.
... any objection to the above proposal?
no objections heard. mark the bug editorial.
kumar: I propose that we add explicit version numbers to section 7
john: proposal: use explicit version numbers in section 7 bullet 2 in the first bulleted list.
<johnarwe> proposal: mark 5407 editorial, add spec version numbers to section 7 first item 2, editors to consider whether to remove section 3 paragraph 2 in light of previous change
msm: agree with John's proposal.
john: mark as editorial
john: I believe this should be
editorial.
... mark as editorial. it does not need to be reviewed after
editorial changes.
sandy: this looks like dup of 5400
john: mark as dup of 5400
discussion similar to the one in Orlando f2f meeting...
<MSM> One possibility: keep 'satisfied' in row 1, and add to each instance validation rule the sentence "Intances of E that are not SML references satisfy the
<MSM> constraint vacuously."
<MSM> Another possibility: Add to each instance validation rule the sentence "The N.N. constraint does not apply to instances of E that are not SML references." and change row 1 to 'does not apply'
jim: proposal: leave the table where it is and apply Kirk's comment# 2 of the bug.
<MSM> Third possibility: Note: the target required, target element, and target type constraints
<MSM> do not apply to element instances that are not SML references.
<MSM> Fourth: Note: the target required, target element, and target type constraints
<MSM> are trivially satisfied for element instances which are not SML
<MSM> references.
Jim: need to consider whether or not we need to change the acyclic section since it is written quite differently. It might have a similar issue with how non-references are covered, and we simply haven't discovered that since we have been concentrating on the target* constraints in this discussion.
john: mark 5416 as editorial. no change to table (i.e. leave in 1st row "non-ref"), add Kirk's new paragraph (comment 2, paragraph 3), editors to clarify content of Kirk's paragraph, and editors to consider whether or not we need to change the acyclic section since it is written quite differently.
<scribe> ACTION: Sandy to suggest wording for bug# 5417 [recorded in http://www.w3.org/2008/01/31-sml-minutes.html#action01]
<trackbot-ng> Created ACTION-168 - Suggest wording for bug# 5417 [on Sandy Gao - due 2008-02-07].
<scribe> ACTION: Michael to suggest wording for bug# 5417 [recorded in http://www.w3.org/2008/01/31-sml-minutes.html#action02]
<trackbot-ng> Created ACTION-169 - Suggest wording for bug# 5417 [on Michael Sperberg-McQueen - due 2008-02-07].
john: mark 5417 as needsAgreement
<Sandy> w.r.t. diff between acyclic and target*: their pre-conditions are different for good reasons. (even targetrequired is different from targetelement/type.)
john: mark editorial
john: mark editorial
john: mark editorial
john: mark editorial
john: mark editorial (except one change: the second suggested change, about rule binding, should be handled as separate bug as Kumar requests)
john: mark editorial
john: mark editorial, needsReview after changes
john: mark needsAgreement
john: mark editorial
john: mark editorial
Last Scribe Date Member Name Regrets pending 2007-08-30 Lipton, Paul until mid-January 2007 2008-01-10 Valentina Popescu 2008-01-17 Boucher, Jordan 2008-01-21 Lynn, James 2008-01-21 Gao, Sandy 2008-01-22 Wilson, Kirk 2008-01-22 Eckert, Zulah 2008-01-23 Smith, Virginia 2008-01-31 Kumar, Pandit Exempt Arwe, John Exempt Dublish, Pratul Exempt MSM Exempt PHMinutes formatted by David Booth's scribe.perl version 1.133 (CVS log)