See also: IRC log
<scribe> Scribe: Jordan
<scribe> ScribeNick: jboucher
check
http://lists.w3.org/Archives/Public/public-sml/2008Jan/att-0010/2008-01-03-minutes.htm
Resolution: minutes approved
only 1 for Pratul and Pratul is not present
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5368
Kumar: mark editorial
Resolution: so marked (by Ginny)
Valentina: point 2 & 3 are fixed by webmaster, only 1 is editorial now
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5379
John: needs agreement?
Resolution: so marked, target LC
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5380
Sandy: believes it is editorial
Resolution: so marked, answer to Sandy's final question is no
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5382
Kirk: mark editorial
Resolution: so marked
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5383
Kirk: mark editorial, perhaps revisit for EPR note
Sandy: perhaps open a separate issue?
Kirk: will open an issue for the EPR note component
<johnarwe> Syntactically, the content of a locator can be a documentURI element defined by SML-IF or anything else understood by the consumer. Typically it is a URI, an XLink [XLink], or a Web Services Addressing endpoint reference [WS-Addressing Core].
Resolution: mark 5383 editorial,
open new issue for EPR note
... remove the sentence starting with "Typically ..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5384
Resolution: mark editorial, remove use of equivalent (and variants thereof)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5386
Resolution: mark editorial
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5387
Kirk: addressed by content sent by Sandy earlier today
<johnarwe> The SML URI Scheme can be used in an SML-IF [SML-IF 1.1] document to reference documents from the interchange set.
Ginny: fixed right after the
release of 3rd draft
... mark won't fix
Sandy: suggests duplicate instead
Resolution: make it so
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5388
Kirk: oh boy!
... mark needs review
... feels reference is overloaded and should be defined more
clearly
John: check use of reference used
on its own and qualify them
... define SML reference and SML reference scheme
Kirk: distinguish use of scheme carefully as well, wrt. xpointer scheme
John: search and qualify use of scheme, in addition to reference
<ginny> Resolution:
<ginny> Define 2 terms - SML Reference (currently "Reference" in the terminology section) and SML Reference scheme (definition should indicate that it is different from xpointer schemes)
<ginny> Review all uses of unqualified "reference" and fix if necessary. Also review uses of "scheme".
Resolution: mark needs review, proposal is as discussed above
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5389
Valentina: mark editorial
Resolution: so marked
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4687
John: has everyone had time? any objections to marking fixed?
Resolution: so marked
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4774
John: has everyone had time to review? any objections to marking fixed?
Resolution: so marked
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4992
Ginny: reviewed Sandy's suggestions and agrees
John: Kirk to add a link to
comments in email
... has everyone had time to review? any objections to marking
editorial?
Resolution: mark as editorial
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5298
Sandy: target is CR, so skip
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5306
<johnarwe> Kirk, Kumar: discussion of possibly reducing scope down to schema complete and version
<johnarwe> MSM: usefulness of version as a data-stamp, for debug, etc, but not for constraining consumers
<johnarwe> ...i.e. consumers must be required to proceed in the face of unknown versions, if (in a practical sense) you want to be able to deploy future versions.
<johnarwe> ...MSM strongly recommends using version numbers. eg a 1.0 consumer, receiving a 2.0 document, still must attempt to process the 2.0 document (as a 1.0 document with some unknown extensions). Since 1.0 consumers are not allowed to just fail based on the version number, a disincentive to deploying 2.0 producers is absent.
<johnarwe> ... If the 2.0 format also happens to be 1.0-compliant, works fine.
John: Kirk to rev proposal per scope discussed above
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5341
Sandy: also a CR target
... skip it
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5379
MSM: my analysis has not progressed since last week, some by F2F next week
Kumar: some idea of where you are going?
MSM: yes, leaning towards all constraints on types and elements (and lots more summary stated on phone)
Kumar: what is the value of allowing constraints on both types and elements?
MSM: a reason is to allow acyclic
and target* to defined in the same places
... a 2nd reason is wrt language design choices/patterns
Ginny: I totally agree with
MSM
... 1) prefer working in types, 2) require good reasons for
restrictions, 3) support consistency
Sandy: certain constraints make sense on elements but not types, XML schema examples support this pattern
John: points out design
perspectives may have varied on decision points
... why do it this way? vs. why not do it this way?
... what use case supports the decision? or, contradicts
it?
Ginny: acyclic was discussed for weeks and determined to be needed on types
<Jim> have to leave now.
Kumar: suggests impact to existing models is too great to allow target* on types
MSM: suggests taking some further discussion into an email thread
Last Scribe Date Member Name Regrets pending 2007-08-30 Lipton, Paul until mid-January 2007 2007-11-15 Lynn, James 2007-11-29 Gao, Sandy 2007-12-06 Eckert, Zulah 2007-12-10 Smith, Virginia 2007-12-13 Wilson, Kirk 2008-01-03 Pandit, Kumar 2008-01-10 Popescu, Valentina 2008-01-17 Boucher, Jordan Exempt Arwe, John Exempt Dublish, Pratul Exempt MSM Exempt PH[End of minutes]