See also: IRC log
RESOLUTION: approve 2009-01-08 telecon minutes at http://lists.w3.org/Archives/Public/public-sml/2009Jan/att-0011/20090108-sml-minutes.html
RESOLUTION: cancel SML F2F on Feb 23.
RESOLUTION: SML very unlikely to meet during Tech. Plenary.
Len: action 213 is done, see
But both notes still need some editorial changes.
... 215 not done yet. expect to finish next week.
... action 216 is done. http://lists.w3.org/Archives/Public/public-sml/2009Jan/0014.html. checked in the spreadsheet, but not the generated documents.
John: for now checking in the spreadsheet is sufficient.
Len: WG home page has links to .doc files. Suggest to change to html files, and remove .doc files from CVS.
<MSM> Actions 190, 211, 212 still open, no progress.
<MSM> Partial progress on action 210; please check
MSM: made progress on action 210. Please check the above 4 links for suggested changes to old namespace documents.
Len: in http://www.w3.org/2008/09/sml, the title says "Version 1.1 Namespaces". Should not be plural.
MSM: I will fix it.
Len: same is true for the latest namespace document http://www.w3.org/ns/sml
John: and in the second paragraph.
Len: IE7 reports an error when trying to load the xsd file linked from the old "sml" namespace document
<lencharest> IE7 cannot display sml-schema.xsd. Error is:
<lencharest> The XML page cannot be displayed
<lencharest> Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
<lencharest> Reference to undeclared namespace prefix: 'xsl'. Error processing resource 'http://www.w3.org/2008/09/xsd.xsl'. Line 1, Po...
<lencharest> Second try:
<lencharest> Reference to undeclared namespace prefix: 'xsl'. Error
<lencharest> processing resource 'http://www.w3.org/2008/09/xsd.xsl'. Line 1, Po...
Sandy: the error I see in IE7: The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML documen...
Len: Kirk mentioned he didn't plan to make any content changes to the EPR scheme document
<lencharest> EPR note is at http://dev.w3.org/cvsweb/2007/xml/sml/epr-note.html
<lencharest> XLink note is at http://dev.w3.org/cvsweb/2007/xml/sml/xlink-note.html
John: WG members should review
these two documents
... are Formulae fixed in the test documents?
Ginny: yes. checked into CVS.
<lencharest> Meeting Tuesday at 9am would be fine
John: to accommodate Henry in UK, Tue. 8:00PT OK for everyone?
Len: not for me.
Sandy: me neither.
John: Please post what time works
... Also likely to reduce the call to 1hr/wk.
John: Should update them since Len updated the documents.
MSM: will look at this again. expect to report back next week. continue to believe manually updating the html is worth doing.
John: walk through the proposal in the above PDF file
Len: question about usage and consistency of curly and square brackets.
John: curly are normally for schema component property names; square are for infoset properties. often happy to leave the consistency issue to the editors.
Len: toward the bottom of page 2. may want to replace "the following line" with "the following entry", to avoid line-wrapping issues.
MSM: suggest to change the second
sentence in the last paragraph on page 4, from "insufficient"
to "not necessarily sufficient".
... also "xsl:variable is one possible choice" to "xsl:variable and sch:let are possible choices"
RESOLUTION: adopt the proposal for 5680 in the PDF file, with above amendments. editors to incorporate it. mark it "editorial". no WG review needed.
John: for test case report, yellow column for "Eclipse COSMOS Result" will become "valid" or "invalid". and they all match the expected result.
Ginny: does that mean the two "no" answers in the feature report are not correct?
John: given how they are worded, COSMOS has to say no, because they are for when certain other features are not supported, but COSMOS does support them.
Ginny: seems appropriate to change the description of those features.
John: in test case report, orange cell on first row was artificial error. Should be required.
Ginny: can't answer some of the orange cells, without Kumar on the MS impl.
John: for base64 tests, where
"expected result" is either yellow or orange, expect them to
... for smlref test "MultipleNonRootXpointer", feature type inconsistency needs to be fixed.
Ginny: 2 lines down is caused by a blank line in the spreadsheet.
John: test "ValidNilRefPSVI" in
smlref, expected result should be "valid".
... "Feature rules, locid": because XSLT doesn't like 2 feature names. Seems the tests are really about "locid." "rules" is just the mechanism used to test "locid". Suggest to use "locid" as the feature name, and move "rules" out of "primary feature".
... similarly for "Feature rules, rule-binding", suggest to use "rule-binding" as primary, and move "rules" to secondary.
John: test "ValidSchematronRule"
in "rules". Expected result should be "valid".
... need to decide next week what should be the required pass rate. May also make the PR transition decision next week.
Last Scribe Date Member Name Regrets pending 2008-05-22 Lynn, James Until further notice 2008-10-29 Pandit, Kumar 2008-12-11 Wilson, Kirk 1/22 2008-12-18 Charest, Len 2009-01-08 Smith, Virginia 2009-01-15 Gao, Sandy Exempt Arwe, John Exempt MSM