W3C

- DRAFT -

SML Teleconference 2008-01-17

17 Jan 2008

See also: IRC log

Attendees

Present
Regrets
Pratul, Zulah_(partial)
Chair
John
Scribe
Jordan Boucher

Contents


 

 

<scribe> Scribe: Jordan Boucher

<scribe> ScribeNick: jboucher

<johnarwe> 06zakim, who's on the phone?01

roll call

approval of minutes

http://lists.w3.org/Archives/Public/public-sml/2008Jan/att-0010/2008-01-03-minutes.htm

Resolution: minutes approved

overdue actions

only 1 and Pratul is not present

Bugs

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

Valentia: mark editorial

Resolution: so marked

Needs Review Bugs

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

Needs Agreement Bugs

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=5396

scratch 5396, it does not exist

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5306

<johnarwe> Kirk, Kumar: discussion of possibly reducing scope down to schema complete and versoin

<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

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.130 (CVS log)
$Date: 2008/01/17 21:01:38 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.130  of Date: 2008/01/16 19:30:10  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/xpath/xpointer/
Succeeded: s/fixed/editorial/
Found Scribe: Jordan Boucher
Found ScribeNick: jboucher

WARNING: No "Present: ... " found!
Possibly Present: Jim John Kirk Kumar MSM Microsoft P14 Sandy ScribeNick Valentia Valentina aaee aaff ginny jboucher johnarwe joined pratul sml trackbot-ng zulah
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Regrets: Pratul Zulah_(partial)
Got date from IRC log name: 17 Jan 2008
Guessing minutes URL: http://www.w3.org/2008/01/17-sml-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]