19:00:23 RRSAgent has joined #sml 19:00:23 logging to http://www.w3.org/2007/12/13-sml-irc 19:00:28 zakim, who's here? 19:00:30 Zakim has joined #sml 19:00:32 Valentina has joined #sml 19:00:39 zakim, who's here? 19:00:39 sorry, johnarwe, I don't know what conference this is 19:00:40 On IRC I see Valentina, Zakim, RRSAgent, pratul, ginny, Kirk, johnarwe, Jim, MSM, trackbot-ng 19:00:44 zakim, this is sml 19:00:44 ok, johnarwe; that matches XML_SMLWG()2:00PM 19:00:46 +Kirk 19:00:59 zakim, who's here? 19:00:59 On the phone I see Jim, [Microsoft], ??P6, Kirk 19:01:00 On IRC I see Valentina, Zakim, RRSAgent, pratul, ginny, Kirk, johnarwe, Jim, MSM, trackbot-ng 19:01:01 Jordan has joined #sml 19:01:01 zakim, please call MSM-Office 19:01:02 ok, MSM; the call is being made 19:01:04 +Valentina 19:01:06 +MSM 19:01:07 zakim, ??P6 is me 19:01:10 +johnarwe; got it 19:01:19 zakim, please call MSM-Office 19:01:19 ok, MSM; the call is being made 19:01:21 +MSM.a 19:01:35 zakim, drop MSM 19:01:35 MSM is being disconnected 19:01:37 -MSM 19:01:37 + +1.408.228.aaaa 19:01:39 zakim, drop MSM.a 19:01:39 MSM.a is being disconnected 19:01:41 -MSM.a 19:01:46 +ginny 19:01:48 zakim, please call MSM-Office 19:01:48 ok, MSM; the call is being made 19:01:50 +MSM 19:01:54 +Jordan 19:02:10 meeting: SML WG Call December 13, 2007 19:02:22 Zakim, Microsoft is me 19:02:22 +pratul; got it 19:02:33 Sandy has joined #sml 19:02:34 +Sandy 19:02:45 agenda at http://lists.w3.org/Archives/Public/public-sml/2007Dec/0107.html 19:03:06 scribe: Kirk Wilson 19:03:22 scribeNick: Kirk 19:04:02 Chair: John Arwe & Pratul Dublish 19:05:19 Regrets: MSM 24th & 31st. 19:05:36 Valentina regrets: 24-31 19:06:04 Ginny: regrets 17 and 24-31 19:07:04 +[Microsoft] 19:07:13 John: Raises question of whether we should have calls next week. Pratul to look at minutes 19:07:36 Minutes not yet distributed or people did not have time to review. 19:07:56 No new action ideas or bugs. 19:09:29 Topic: 4772: Localization 19:09:40 http://www.w3.org/Bugs/Public/show_bug.cgi?id=4772 19:11:04 Kumar has joined #sml 19:11:06 John: Any objection through comment #6? 19:11:52 zakim, who is making noise? 19:12:02 MSM, listening for 10 seconds I heard sound from the following: johnarwe (65%), pratul (5%), +1.408.228.aaaa (85%), [Microsoft] (48%) 19:12:09 zakim, mute aaa 19:12:09 sorry, MSM, I do not know which phone connection belongs to aaa 19:12:13 zakim, mute aaaa 19:12:13 +1.408.228.aaaa should now be muted 19:12:32 zakim, who's on the phone? 19:12:32 On the phone I see Jim, pratul, johnarwe, Kirk, Valentina, MSM, +1.408.228.aaaa (muted), ginny, Jordan, Sandy, [Microsoft] 19:13:08 zakim, aaaa is probably Zulah 19:13:08 +Zulah?; got it 19:13:15 zakim, unmute Zulah 19:13:15 Zulah? should no longer be muted 19:13:37 No objection. 19:13:59 MSM has submitted editorial clarifications, comment #9. 19:14:12 zulah has joined #sml 19:14:29 ...Any objection ot moving these changes to editorial. Editors should look at comment #9. 19:14:47 s/Any/No 19:15:25 http://www.w3.org/Bugs/Public/show_bug.cgi?id=4992 19:15:39 Topic: 4992: Object Identity http://www.w3.org/Bugs/Public/show_bug.cgi?id=4992 19:16:23 (MSM: I'll catch up eventually--response time is a little slow for me right now.) 19:17:19 Ginny: Sandy has comments in Comment #20. Mostly editorial changes. 19:17:54 John: Any objection to accepting comment #20 as editorial 19:18:34 ...Accept comments in #19 and #20. 19:19:27 Resolution: Move 4992 to Editorial and accept changes in #19 & 20. 19:20:22 Topic: 5291 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5291 19:21:01 Ginny: Recommends not backing out any of the changes and notes that Kirk recommended a rephrasing of a sentence. 19:21:52 John: Proposal is to accept comment #10 and moved to editorial 19:22:04 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5294 19:22:19 Resolution: This is editorial and not needsReview and make change in comment #10. 19:22:53 resolution above is re: 5291. now beginning to discuss 5294 19:23:25 Topic: 5294: explanation of smilif:dataType as skip 19:23:47 Resolution: 5294 is Resolved, Closed 19:23:52 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5301 19:24:27 TOpic: 5301: 19:24:36 Resolution: Resolved 19:24:52 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5318 19:25:00 Topic: 5318 19:25:36 Resolution: Resolved. Fixed. 19:26:04 Topic: 4644: Allows assertion on local elements and types 19:26:42 http://www.w3.org/Bugs/Public/show_bug.cgi?id=4644 19:27:37 Sandy's and Kumar's comments. Kumar advises that there are a long number of changes. 19:28:01 Ginny: Did review but did not go into it deeply. 19:28:36 Resolution: Up through comment #5, we will accept. If new issues, there should be new issue opened. 19:28:57 John: Any objection to making comment #6 editorial. 19:29:25 Kumar: is Ok with making it editorial but will discuss with Sandy. 19:29:54 Resolution: 4644 is editorial. 19:31:11 5247 19:31:17 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5247 19:31:19 Topic: 5247: 19:32:16 Kumar put in text several days ago. 19:33:52 MSM: Ambiguity in the phrase "not part of interchange set". 19:34:20 Sandy: either it is there or it is not. 19:35:53 MSM: Simpler to require data to have a child and base64 data be non-empty. 19:37:00 John: We need to allow for tombstone documents. If change prevents this, then it will undo other issue resolutions. 19:37:48 MSM: Agrees 19:38:31 Resolution: 5247 is Fixed. 19:38:47 Topic: 4636 Fragment Idenyifiers. 19:39:21 s/Idenyifers/Identifiers 19:39:46 Kumar: This is just editing some of the words. 19:39:58 Resolution: Fixed. 19:40:42 Topic: 4774: 19:41:01 http://www.w3.org/Bugs/Public/show_bug.cgi?id=4774 19:41:19 MSM: Will read (starting at comment #14) 19:41:57 Ginny: Suggesting we can step through Sandy's comments in #17. 19:43:05 John: inside 17, subcomment 9: rewording regarding schemaComplete ambiguity. 19:44:04 q+ to ask whether there is an algorithm for determining whether a schema document is or is not 'required' 19:44:28 Ginny: Confusing 19:45:47 Kirk: the name may help to resolve ambiguity. 19:46:04 John: we can resolve after LC. 19:46:34 ...the part in comment 12 where a rename of the syntax is suggested, not the whole thing 19:46:42 Ginny: name is OK, if we define precisely. We should change definition to reflect Sandy's intention. 19:46:51 q- 19:49:12 [I wonder if the description could be "The SML-IF document is not known to be schema-complete". 19:49:13 Resolution: rewording of 9 in 17 is editorial 19:49:46 Resolution: point 3 in comment 9 in 17 is editorial 19:50:13 point 12 in comment 9 in 17 19:50:51 Any objecdtion to adding wildcard spec to namespace binding type. 19:51:12 Resolution: No objection. 19:51:20 point 15 in comment 9 in 17 19:51:41 Proposal: have a default="false" 19:52:42 Pratul: Most common case will be schemaComplete="true". 19:53:23 Sandy: explains rationale behind default for schemaComplete="false" 19:53:42 Pratul: Agrees 19:54:54 MSM: Status quo treats it as false; but it doesn't address Pratul's suggestion that this is behavior we want to promote. 19:55:23 Pratul: Withdraws objection. 19:56:22 MSM: Thinks it is better if there were default="true" or make attribute required. 19:57:03 Ginny: Support required attribute 19:57:44 MSM: if default is true, then any incompleteness will be flagged during validation. 19:57:58 s/required/required an no default 19:58:10 I prefer default="true" 19:58:16 Kumar; Supports required an no default. 19:59:06 Proposal: adding default and making value 'False" 19:59:21 ...Objections from MSM and Zulah 20:00:03 Proposal: add default and making value "false" 20:00:19 Ginny and Kirk object 20:00:35 s/false/true/ 20:00:52 Kumar does not object but prefers third proposal 20:01:13 Proposal: make schemaComplete required and no default value 20:01:37 Resolution: 17.9.15: Make attribute Required with no default value. 20:03:54 proposed change: steps 6 and 7 are applied in current draft only if schemabindings element is used. should also apply if no such element is present or if the consumer does not support schema bindings 20:04:03 Comment 17.14.1: Schema location--if look at schema binding uses alias. Proposal: same logic is to be used when there is no schema binding or the user chooses not to use it. 20:04:45 6 and 7 describe the processing for schemaLocation on include, redefine, xsi:, import 20:06:50 current draft is somewhat different from proposal. restructuring probably required to be clear when each rule applies. 20:07:58 Kunar: It seems that everyone agrees to the principle; need to be considered by editors. 20:08:00 Jim has joined #sml 20:09:06 Resolution: Accept 17.14.1 for section 5.5 20:09:53 Kumar: Processing of redefines/include will be the same. 20:10:05 so that "no schema bindings" handling of schemalocation agrees with case when schema bindings are there 20:10:15 ...and the consumer supports them 20:10:46 MSM: Agreement seems to conflict with 3.d and 3.c in current editor's draft. 20:10:58 John: this should be a separate question. 20:12:13 John: instruction to editors- Kumar is pointing out that nesting is incorrect is 5.5. 20:12:36 [I apologize; I think I led us into a rat-hole. I overlooked the condition in 2.c/d and 3.b/c on whether the IF document is schema-complete or not. 20:12:53 ] 20:14:11 17.14.3 for Kumar 20:15:19 John, see comment 16. This says what you want. 20:15:38 ...Editorial restructuring is required. 20:16:41 Proposal 17.14.3 go to Editors to resolve. (Editorial) 20:17:35 John: need structural change so as to make sure the case is covered 20:18:14 Zulah: and MSM want review of any proposal 20:18:47 comments 15 and 16 of 4774 suggest some ways to fix 20:18:54 Resolution: 17.14.3 give to Editorials. Editors will propose solution for review. 20:19:59 Topic: 4687 Handling DTDs 20:20:03 http://www.w3.org/Bugs/Public/show_bug.cgi?id=4687 20:20:43 Proposal: Allow based64 for all documents, require for those containing DTDs 20:21:50 current text: There 20:21:51 can be at most one document embedded 20:21:53 s/can be/MUST be/ (twice) 20:22:02 MSM: bottom at point 1:recommends changed to statement: There MUST be at most one. 20:22:08 msm proposes: There MUST be at most one document embedded 20:22:13 also for point 2 20:22:41 Zulah: MSM's comments apply to both points 1 and 2 20:23:06 Resolution: 4687 is Editorial as amended by MSM above. 20:23:14 ginny_ has joined #sml 20:23:56 Topic: 5091: Distinguish normative vs. non-mornative 20:24:11 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5091 20:25:06 Ginny: These changes assume normative unless explicitly marked non-normative. 20:25:33 ...We need to reference the example appendices in text. 20:26:13 Valentina: Original text did not this necessary. 20:27:04 Valentina: Original text did not make this necessary 20:27:43 Resolution: We accept proposed 5091 as wholly fixed. Open new bugs for changes. 20:28:17 Topic: 5303: Recognize SML URI scheme without schema assessment 20:28:58 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5303 20:30:26 Ginny: Question regarding how to process 2 URIs. 20:30:52 Sandy: the SML URI does not flag an error because it might be some other scheme. 20:31:22 MSM: Have we created a situation in which some erroraneous schemes will not be identified. 20:31:47 zakim, mute me 20:31:47 Sandy should now be muted 20:31:52 John: This is a situation because of schemes with overlapping content. 20:32:42 John: two editorial comments in comment #1 and comments 4 and 5 20:33:44 Resolution: No objection to making 5303 editorial. 20:34:28 Topic: 5063: Inheritance of SML Constraints 20:34:39 http://www.w3.org/Bugs/Public/show_bug.cgi?id=5063 20:34:58 John: Discussion on last call. 20:35:11 zakim, who's on the phone? 20:35:11 On the phone I see Jim, pratul, johnarwe, Kirk, Valentina, MSM, Zulah?, ginny, Jordan, Sandy, [Microsoft] 20:35:27 zakim, who's on the phone? 20:35:27 On the phone I see Jim, pratul, johnarwe, Kirk, Valentina, MSM, Zulah?, ginny, Jordan, Sandy (muted), [Microsoft] 20:36:10 MSM: Continue to fear complexity to write to enforce this. There is a question of alignment, but it is a question of alignment in a design pattern rather than technical matter. 20:37:26 MSM: Only Type assignment needs to be preserved across restriction. Not a contradiction for us to state that target constraints across restriction, but rules will be hard to write. 20:37:59 I can't understand Sandy 20:38:35 SG: i feared the complexity, too, but now I support the proposal. 20:38:54 I'm also having trouble following Sandy's discussion. 20:39:45 Sandy: Rules will be hard to read, problem only for implementers. 20:40:47 Kumar: Agrees to with Sandy that implementers could keep alignment with schema. 20:41:34 Ginny: Ok with Kumar's proposal. 20:42:15 The issues that SML has with inheritance and assertions are applicable to all Schema users and should be fed into Schema 1.1 20:42:32 Zulah: Issues are general issues with schema inheritance. 20:42:38 Much of the design for SML's inheritance is better factored into Schema 1.1 20:42:51 This should be sent to the Schema 1.1 group which should address this issue. Not SML 20:43:40 Zulah: This issue should remain open at this point. 20:44:42 Zulah: Thinks that it will be difficult for SML to get this correct. Resolution belongs in SML WG. 20:45:22 Zulah: Clarifies that this concerns pertains only to this issue. 20:45:28 Kirk, Zulah said that "Resolution belongs in XML Schema 1.1 WG" 20:46:12 Zulah: Inheritance issues belongs to Schema WG 1.1 20:47:13 Zulah: Issues exist for all schema issues and the work be handed off to Schema WG. 20:47:25 [The problem we have labeled 'alignment with XML Schema' is precisely the fact that in XML Schema, constraints on elements contained in complex types are not guaranteed to be preserved across complex type restriction. If XML Schema had a clearer story on that topic, then the task of SML in describing this constraint on the target* constraints would be far simpler.] 20:48:15 Zulah: Objects to closing this particular bug and have more discussion. 20:48:35 s/and have/and would like to have/ 20:48:47 Pratul: We don't have a dependence on Schema 1.1. 20:49:10 Kumar: This will keep our group hanging for a long time. 20:49:44 John: Strawpoll. Who would object closing this bug as Kumar proposed per sandy's comment in #7? 20:50:28 MSM: there is an architectural issue here. It is premature to close this bug at this time. 20:52:20 Jim: No problem with statement in comment #6. We need to come up with a schedule for closing this and plan. 20:53:02 I suggest we not close it without entertaining the possibility that another option be taken. 20:53:06 Ginny: We need to support the request not to resolve this issue due to objection from Zulah and MSM. 20:53:43 Jim: HP does not have issues as laid out by Kumar. 20:54:12 Kumar: It doesn't make sense to have issues addressed by Schema. 1.1 WG 20:54:22 Kumar: What is technical issue? 20:54:55 Zulah: Technical issue is that we need to consider architectural issue. These are larger than SML WG. 20:55:40 Kumar: What IS the architectural issue here? 20:56:02 We believe that going to LC with will slow the progress of SML 20:56:09 Zulah: the technical issue is the one identified in 5063: inheritance of constraints on element declarations across complex type restriction 20:56:34 Kumar: We are not changing XML Schema constraints, this is an issue of SML constraints that are not handled by Schema 1.1 WG. 20:57:25 Zulah: BEA's contention, if Schema 1.1 addressed these issues, then SML wouldn't have to. 20:57:57 ...BEA does not yet have a proposal at this point. It needs more discussion. 20:58:21 Kumar: This is not an Schema 1.1 architectural issue. 20:59:39 MSM: Complex type restriction propagate across restriction, but contraints on child element declarations do not propagate. 21:00:08 MSM: In 5063, we want our constraints to behave different. 21:00:31 ...Therefore, Schema has gotten it wrong. 21:00:34 -Kirk 21:01:06 I have lost telephone connection. Can someone continue recording this the discussion? 21:01:20 will do 21:01:29 time to end anyway 21:02:12 I can't get back on because the "conference is restricted" 21:02:17 MSM: note that when doing derivation by restriction in schema, constraints on types are automatically inherited and constraints on elements are not automatically inherited. 21:02:50 Let me know when I can generate the minutes. 21:04:53 -Sandy 21:06:19 Is the discussion still going on? 21:08:04 next meeting Jan 3 21:08:49 request to BEA to email some details on their issue, including a proposal, while people are out next 3 weeks. 21:09:21 -Jordan 21:10:25 Zulah notes BEA has forced closure next several weeks, so may need to wait several weeks into Jan for a thorough proposal. 21:10:27 -pratul 21:10:28 -[Microsoft] 21:10:30 -ginny 21:10:32 -Valentina 21:10:34 -Zulah? 21:10:36 Jim has left #sml 21:10:38 -MSM 21:10:41 -Jim 21:10:51 -johnarwe 21:10:53 XML_SMLWG()2:00PM has ended 21:10:54 Attendees were Jim, Kirk, Valentina, MSM, johnarwe, MSM.a, +1.408.228.aaaa, ginny, Jordan, pratul, Sandy, [Microsoft], Zulah? 21:11:07 rssagent, generate minutes 21:12:08 rssagent, make log public 21:20:29 see my email that I just sent. The issue ended immediate after you hung up. 21:20:57 I meant "session" rather than "issue". Have "issue on my mind. 21:23:23 rrsagent, generate minutes 21:23:23 I have made the request to generate http://www.w3.org/2007/12/13-sml-minutes.html johnarwe 21:23:33 rrsagent, make log public 21:24:54 Ok Now it's working. 21:25:21 And I was able to access the minutes--WHEW!! That really scared me. 21:29:40 I don't think the rrsagent likes me :-) 21:32:06 johnarwe has left #sml 21:37:30 RRSAgent, please make minutes 21:37:30 I have made the request to generate http://www.w3.org/2007/12/13-sml-minutes.html MSM 21:38:02 sorry about that; didn't mean to overlay anything. 23:05:36 Zakim has left #sml