12:16:00 RRSAgent has joined #sml 12:16:00 logging to http://www.w3.org/2007/08/30-sml-irc 12:16:11 Zakim has joined #sml 12:16:22 rrsagent, make log public 12:16:32 zakim, this will be sml 12:16:32 ok, Sandy; I see XML_SMLWG(IBM f2f)8:00AM scheduled to start 16 minutes ago 12:16:34 http://www.w3.org/XML/2007/08/xml1011.html 12:17:21 rrsagent, generate minutes 12:17:21 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Kirk 12:17:47 Link above is for XML 1.0 and XML 1.1 Presentation by MSM 12:18:22 Scribe: Paul Lipton 12:19:02 Meeting: SML F2F Day 3 12:19:29 bug 4630 12:19:55 Discussion/Presentation by MSM on general problems on referring to other specs will also be discussed. 12:20:43 Marv has joined #sml 12:21:55 MSM: Generally thinks people are too worried about things like new chars 12:23:47 Kirk has joined #sml 12:23:52 MSM: Parsers may have to be changed, but why worry about downstream apps? 12:33:02 MSM: Has not heard reports of problems, but there is a fear of 1.1. 12:33:36 Pratul: What are the things that may need to be fixed with a possible XML 1.2, mentioned in slides? 12:34:44 Valentina has joined #sml 12:35:21 MSM: XML 1.2 is very preliminary. Basic idea is to minimize potential problems like some 1.0 problems are not legal 1.1. Don't have more info at this time. 12:37:06 MSM: XML 1.0 processors can quite if they want (don't have to) in the face of later versions. Errata later on said 1.0 processor MUST fail. This is a problem for processing 1.1. 12:37:36 ... some thought that errata is itself a problem. 12:39:25 Kumar: How many of the people who were not enfranchised due to limitations in 1.0 are now using 1.1? 12:39:34 MSM: Not sure 12:40:36 John: Difference between producers and consumers (cites Xerces as supporting both) 12:41:54 Kumar: Any idea of number of vendor? 12:41:57 MSM: no 12:42:05 Paul: When was it recommended? 12:42:14 MSM: 2003ish, not exactly sure 12:43:47 rrsagent, draft minutes 12:43:47 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Paul 12:43:50 It was published on 4 Feb 2004 13:02:19 Kumar: What provision for breaking existing 1.1 processor? 13:02:32 MSM: Committment for additive changes only 13:04:05 s /breaking/breaking change/ 13:05:21 MSM: Loose-coupling means certain aspects of data of interest will be in other specs. 13:07:10 s/existing/in existing/ 13:10:13 Kumar: if we decide to base on xml 1.1, then some xml 1.0 apps may break. Specs that are depended upon can break dependent specs. Expressed concern about customer viewpoint and being realistic. 13:12:08 MSM: Separation of concerns is strong justification. The guys in the other spec knew what they were doing. 13:17:04 Kumar:What do other people think of relying on latest version of XML? To me, it sounds precarious. 13:18:30 Jim: To me, if we take path of last bullet item in pres (slide 20) this might address your concerns because XML 1.0 is still the base and safe, but leaves freedom for vendors/customers to use XML 1.1. 13:21:24 Kumar has joined #sml 13:22:06 i/What do other/Topic: Discussion of applying these principles from MSM to SML 13:22:59 John: One complication we may have is when there is multple documents and there is a mix of XML 1.0 and 1.1 involved. We have to decide to not deal with it or perhaps something else. 13:23:39 John: What if your flags are "1.0 strict," for example, how do you deal with this? 13:23:55 MSM: A conforming xml 1.1 processor must support 1.0 13:26:31 MSM: The implementation will have to note incompatibility with runtime options independent of SML 13:26:47 MSM: Separate from violation of SML spec, of course. 13:27:09 Pratul: How 1.0/1.1 supported should be up to my implementation to decide. 13:28:35 MSM: One issue might be (related to yesterday's issue about target type constraint) is one of the possible solutions (not chosen) was you have to use same schema for both documents. If we did choose that option, then it would be possible to construct cases where the validity of a doc may vary. 13:29:25 s/vary./vary according to NC name type./ 13:30:07 John: If producer created sml-if of 1.0 and 1.1 documents how much do we want to constrain that? 13:30:59 Kumar: If consumer is 1.0 only, it can reject it. 13:31:55 John: Question is what does our spec need to say to constrain possiblities. We can say no in mixed mode. Pratul said for stuff later than 1.0, say nothing is outside scope of spec. 13:35:41 John: Any problem with Pratul's suggestion of fixed floor to specify interoperability and allowing later versions of related spec freely (implementation defined). Suggest words from Schema that put a should on it (the very bottom bullet on slide 20). 13:37:55 MSM: Schema does not have a signal about version 13:38:16 MSM: You can tell if it is valid against a 1.0 or 1.1, of course. 13:39:56 s/slide 20/wording from slide 16 and bullet from bottom from slide 20)/ 13:40:26 Resolution: No objections to John's assertion above. 13:40:57 johnarwe has joined #sml 13:41:13 MSM: Consensus on general principle here. 13:41:39 John: What about specific XML 1.1 question? General principle - is that OK? 13:42:20 Pratul: General principle includes relying on other specs. We specify a base, but not a ceiling. 13:42:33 s/base/floor/ 13:44:10 John: For each specific case, we will choose a specific spec that will serve as a floor. Is anybody uncomfortable with this? 13:44:31 Resolution: Above resolved as per John. 13:44:36 And conforming implementations must support the selected floor 13:45:57 John: XML 1.0 / 1.1 decision. Are we satisfied with applying the general principle here? 13:46:23 Kirk: We have to keep in mind future versions. 13:47:29 Jim: I propose that we adopt XML 1.0 as the floor as a general principle unless there are specific issues later. 13:47:39 Resolution: XML 1.0 is the fixed floor. 13:48:20 Marv: Propose we want to add the boiler plate encouraging implementors. 13:48:43 MSM: W3C has specific rules. Regarding references there is not a strict rule. 13:49:03 s/rules/rules in general/ 13:49:30 Marv: This is ISO boilerplate that we saw on slide 16. 13:49:53 Marv: That wording or something analogous. 13:50:51 Sandy: We should wait until we agree on all references. 13:50:55 s/rules in general/rules for IP 13:51:22 MSM: We can adjust it as necessary if we end up with a special case. 13:51:48 s/it /it later/ 13:52:17 Sandy: ok with adjusting it later, giving editors latitude to impart the correct spirit 13:52:35 http://www.w3.org/XML/2007/08/xml1011.html 13:53:18 The ISO wording being discussed is: 13:53:19 The following normative documents contain provisions which, through reference in this text, constitute provisions of this [spec]. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this [spec] are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative 13:53:21 s /slide 16/slide 17/ 13:54:00 slide 17 in the current (revised) slides, although it may have been 16 in the slides I presented from 13:57:39 s/slide 16/slide 17/g 13:57:46 rrsagent, draft minutes 13:57:46 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Paul 13:58:24 rrsagent, draft minutes 13:58:24 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Paul 14:01:45 SG presents slides on XML Schema 1.1 14:02:18 topic: XML Schema 1.1 overview 14:02:21 Paul has joined #sml 14:02:49 scribe: Paul 14:02:59 ScribeNick: Paul 14:03:03 http://lists.w3.org/Archives/Public/public-sml/2007Aug/att-0085/20070829_-_Schema_1.1_for_SML.ppt 14:03:12 http://lists.w3.org/Archives/Public/public-sml/2007Aug/att-0085/20070829_-_Schema_1.1_for_SML.pdf 14:03:30 TOPIC: Sandy presentation of XML Schema 1.1 14:04:35 Sandy: There are 1.0 schemas that are no longer valid under 1.1. But people should not have using the breaking structures. 14:05:00 s/have/have been/ 14:06:03 Sandy: There are 1.0 schemas that are no longer valid under 1.1. But people should not have using the breaking structures. 14:06:44 PCL has joined #sml 14:08:00 MSM: Schema wg (I think) will not go to req pointing to something still changing 14:08:11 scribenick: PCL 14:08:36 Pratul: Are these new types required. 14:08:45 Sandy: These types are always there and must be supported. 14:09:08 Sandy: In the new versions of these specs. 14:09:20 Slide 4 14:12:41 Kumar: (referring to slide 5) so today you have to respecify. 14:12:45 Sandy: Yes. 14:13:10 Pratul: Can you do assertions on any global declarations? 14:13:16 Sandy: Only complex types 14:19:30 Zakim has left #sml 14:22:26 Zakim has joined #sml 14:22:37 zakim, this is sml 14:22:37 MSM, I see XML_SMLWG(IBM f2f)8:00AM in the schedule but not yet started. Perhaps you mean "this will be sml". 14:22:49 zakim, this will be sml 14:22:49 ok, MSM; I see XML_SMLWG(IBM f2f)8:00AM scheduled to start 142 minutes ago 14:23:56 Valentina: (slide 5) is messageType a string? 14:24:16 Sandy: is a type and the alternative elements have the derived types. 14:24:31 Paul: Can be default 14:24:34 Sandy: yes 14:38:55 rrsagent, draft minutes 14:38:55 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html PCL 14:44:20 John: Sandy, what is your proposal? 14:44:35 Sandy: Requiring 1.0 and allowing 1.1 probably makes sense. 14:45:12 s/1.1/1.1 and beyond/ 14:45:28 Jim: What do we think of chosing only Schema 1.1? 14:46:16 Pratul: There is a possibility that 1.1 won't go through. 14:46:31 Pratul: May have to changes some terms, etc. in spec. 14:47:17 if 1.1 does not go to Rec "soon enough" sounds analogous to the situation we heard about already with schema 1.1's relationship to IEEE754r 14:47:25 MSM: I don't think we would have to change SML schema examples. 14:47:42 Pratul: I was worried about sections that define semantics. 14:48:17 Jim: Correction. I was really saying you must support 1.0 or 1.1. 14:48:34 Jim: You could support 1.1 (if you want) instead of 1.0. 14:49:08 John: How do we get deterministic interop if there is more than one floor? 14:49:51 Jim: Answer may be that Schema 1.1 support still means you can handle 1.0 docs. 14:51:17 Jim: If we don't require schema 1.0, are we killing interop? 14:51:27 Sandy: yes and benefit unclear. 14:52:50 John: Fixed floor schema 1.0 and anything else allowed. Any discomfort? 14:52:59 John: This is a proposal by Sandy 14:53:12 Resolution: Agreed 14:53:33 s/Fixed/Proposal for fixed/ 14:54:09 rrsagent, draft minutes 14:54:09 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html PCL 14:57:07 rrsagent, draft minutes 14:57:07 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html PCL 14:57:53 rrsagent, generate minutes 14:57:53 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html PCL 14:59:25 rrsagent, generate minutes 14:59:25 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Kirk 15:02:01 ginny has joined #sml 15:02:16 Topic: MSM on XPATH 2.0 15:02:28 XML_SMLWG(IBM f2f)8:00AM has now started 15:02:35 +Ginny 15:03:40 Paul: 15:03:51 +??P38 15:04:17 Paul: Current minutes only being generated by rrsagent in pieces. MSM will help address this. 15:04:40 zakim, ++P38 is Ginny 15:04:40 sorry, Kirk, I do not recognize a party named '++P38' 15:04:58 P38 is not /me 15:05:00 zakin, ??P38 is Ginny 15:05:21 zakim, ??P38 is Ginny 15:05:21 +Ginny; got it 15:05:34 zakim, who is on the phone 15:05:34 I don't understand 'who is on the phone', ginny 15:05:37 zakim, who's on the phone? 15:05:37 On the phone I see Ginny, Ginny.a 15:05:55 zakim, Ginny is SMLF2F 15:05:55 +SMLF2F; got it 15:06:03 zakim, Ginny.a is Ginny 15:06:03 +Ginny; got it 15:10:27 MSM: 2.0 is superset (largely compatible) with 1.0, but if we mandate 2.0 it will mean more work for implementors. 15:10:42 ... Lots of extra power in 2.0, though (bigger language) 15:11:09 http://www.w3.org/XML/2007/08/xpath1020.html 15:13:04 John: Any xpath 2.0 proposals? 15:13:20 Kumar: Floor would be 1.0 and open ceiling. 15:14:16 s/Floor/Proposal to make floor/ 15:14:33 John: Any objections on Kumar's proposal? 15:14:41 MSM has joined #sml 15:14:44 Resolution: Floor is 1.0 and open ceiling 15:16:32 Jim: Can we address the URI/IRI issue? 15:16:59 Pratul: Phillip said IRI should be mandatory (I seem to remember) 15:17:39 MSM: Phillip is not on IRC, would prefer to not represent him without being able to chat with him 15:19:01 Sandy: 3 bugs open related to xpath/schema/xml - what should we do? 15:19:18 John: Any objections to updating bugs and changing state to editorial? 15:19:34 John: No decisions yet on schematron, btw. 15:19:39 bugs 4628, 4629, and 4630 appear to be movable now from needsAgreement to needsDrafting 15:19:59 sl/needsDrafting/editorial/ 15:20:44 John: Schema reviewers would certainly care about xml and schema revisions 15:21:42 John: we have all the editors here or on phone 15:22:01 John: Any risk, editors, with moving these 3 issues to second draft? 15:22:06 Ginny: OK 15:22:09 Jim: OK 15:22:43 Ginny: what does note on schematron mean? 15:22:53 John: 4629 - look at that 15:24:43 John: To deal with schematron portion of 4629, do we know what to do or do we need proposal? 15:24:57 Pratul: somebody should read normative appendix 15:26:16 Pratul: Schematron spec leads one to believe default binding is 1.0. We need to decide in sml what is query binding in context of schematron rules. 15:26:57 ... We could say, for example binding is xpath 1.0 (for query) 15:27:47 Ginny: you can decide binding on your own, Schematron says 15:28:31 The Schematron spec at http://www.schematron.com/iso/P16.html reads in part (in annexe C): 15:28:39 A Schematron schema with no language binding or a language attribute with the value xslt, in any mix of upper and lower case letters, shall use the following binding: 15:28:43 — The query language used is the extended version of XPath specified in XSLT. Consequently, the data model used is the data model of those specifications. 15:30:16 John: Is there discomfort with us saying fixed floor with current ISO version of schematron and allowing future versions if they come to pass? 15:30:20 Pratul: agree 15:30:38 Resolution: Yes to John's proposal. Add decision to 4629 15:31:09 The queryBinding bug is 4977. 15:31:45 rrsagent, generate minutes 15:31:45 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html Kirk 15:35:02 scribe: Kumar 15:41:06 Kumar has joined #sml 15:41:16 scribe: Kumar 15:43:18 msm: having document based cycles is easier implementation wise. 15:43:53 msm: in real world scenarios we are not likely to see cycles because the types involved in a ref relationship are usually different 15:44:00 trackbot-ng has joined #sml 15:44:06 Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/sml/ 15:49:22 kumar: there are perf problems with element based cycles. with document based cycles and a sql server based store, it is much easier to index on document identity columnl. if we have element based cycles, we need to use xpath (unlimited length string) as the element identity. this makes it very hard to have a performant solution because we cannot directly index on such a column. 15:50:02 john: we can alleviate the problem to some extent by checking constraints at predermined time (low load) rather than at each insert. 15:50:10 kumar: yes, that is an option. 15:51:03 jim: if we do not adopt element based cycles, would we harm sml's adoption? 15:51:10 john: not likely. 15:55:05 john: should we fix 4639 for second draft? 15:55:14 ginny: why not postpone it to LC? 15:55:34 john: it is better to not postpone a lot of bugs to LC 15:57:32 john: we need someone who cares about having element based cycles to own the bug and drive it. do we have someone for that? 15:58:00 trackbot-ng has joined #sml 15:58:06 Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/sml/ 15:59:45 15:59:45 ... 15:59:45 15:59:45 15:59:45 15:59:46 15:59:48 15:59:50 16:02:15 action: Jim to make a proposal for the definition of an element based cycle. 16:02:15 Sorry, couldn't find user - Jim 16:02:49 action: James to make a proposal for the definition of an element based cycle. 16:02:49 Created ACTION-121 - Make a proposal for the definition of an element based cycle. [on James Lynn - due 2007-09-06]. 16:04:21 ginny: would like to keep the bug open and would like to have element based cycles mandatory. 16:04:45 ADJOURNED. 16:04:53 RRSAgent, please draft minutes 16:04:53 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html MSM 16:05:03 -Ginny 16:05:04 XML_SMLWG(IBM f2f)8:00AM has ended 16:05:05 Attendees were SMLF2F, Ginny 16:06:08 present: Kumar, Pratul, John, Jim, Ginny, Sandy, Valentina, Paul, Marv, Kirk 16:06:12 RRSAgent, please draft minutes 16:06:12 I have made the request to generate http://www.w3.org/2007/08/30-sml-minutes.html MSM 16:19:00 trackbot-ng has joined #sml 16:19:06 Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/sml/ 16:26:28 MSM has joined #sml 17:23:17 Zakim has left #sml 18:56:22 MSM has joined #sml