15:02:13 RRSAgent has joined #databinding 15:02:13 logging to http://www.w3.org/2008/03/11-databinding-irc 15:02:15 RRSAgent, make logs public 15:02:15 Zakim has joined #databinding 15:02:17 Zakim, this will be DBWG 15:02:17 ok, trackbot-ng, I see WS_DBWG()10:00AM already started 15:02:18 Meeting: XML Schema Patterns for Databinding Working Group Teleconference 15:02:18 Date: 11 March 2008 15:02:38 +Yves 15:03:23 zakim, code? 15:03:31 zakim, code? 15:03:38 the conference code is 3294 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), pauld 15:03:50 the conference code is 3294 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), pauld 15:04:47 yves, getting "conference is restricted" 15:05:25 hum, try to wait for an operator, then 15:05:30 i seem to be on conference ok, but only me! 15:05:40 telcon ended (as we are one hour late) 15:05:46 + +0791888aaaa 15:06:03 zakim, aaaa is me 15:06:03 +pauld; got it 15:08:13 scribe: pauld 15:08:42 chair: pauld 15:08:58 pauld: we need to renew the charter, runs out end of this month 15:09:30 yves: we need to have a document published, that'll help 15:10:43 JonC has joined #databinding 15:11:07 Hi 15:11:30 Cannot join conference call... 15:11:59 pauld: we need to list the changes from the previous Last Call publication 15:16:13 Agenda: http://lists.w3.org/Archives/Public/public-xsd-databinding/2008Mar/0001.html 15:16:24 Topic: Publication of Basic Patterns 15:18:50 gcowe: "elementfinal" isn't valid, and is "Basic", should be removed 15:18:52 http://lists.w3.org/Archives/Public/public-xsd-databinding/2008Feb/0008.html 15:19:07 pauld: testing worked? 15:19:16 gcowe: example was missing 15:19:26 pauld: doubly sure we should remove it 15:20:00 pauld: OK so "ElementFinal" is removed as a pattern 15:20:24 http://lists.w3.org/Archives/Public/public-xsd-databinding/2008Feb/0013.html 15:20:40 elementfixed was a new advanced pattern added 15:20:50 + +0800328aabb 15:21:13 zakim, aabb is Jonc 15:21:13 +Jonc; got it 15:22:34 pauld: elementfixed accepted as an advaced 15:25:53 pauld: I'll produce a list of differences 15:26:49 XML Schema WG send comments: http://lists.w3.org/Archives/Public/public-xsd-databinding-comments/2008Feb/0000.html 15:27:02 pauld: most look reasonable 15:29:48 pauld: most look like they apply to spec as it stands 15:32:15 pauld: suggest I raise these as LC issues, publish this week on the list and we OK at a meeting next tuesday 15:32:50 Topic: Collection and Schema Annotation 15:39:31 http://www.w3.org/TR/2006/WD-xmlschema-patterns-20061122/ 15:40:39 pauld: have a technique for annotation schema, should have it tonight 15:40:41 ls 15:40:45 s/ls// 15:41:32 $ cvs co -r1.67 patterns.xml 15:43:13 last call patterns: http://www.w3.org/2002/ws/databinding/edcopy/patterns/patterns-lc1.xml 15:43:20 http://www.w3.org/2002/ws/databinding/edcopy/patterns/patterns.xml 15:44:11 need to record list of patterns added and removed since our last, last call 15:44:49 gcowe: will look at the differences 15:45:44 Topic: lc-xsd-1 15:45:57 """ 15:45:58 * References to concepts and terminology from XSD need to be made more 15:46:00 precise. For example, section 1.3 says "A document claiming conformance 15:46:01 to this specification ... MUST conform to the [XML Schema 1.0 15:46:03 Recommendation]", but XSD provides no conformance requirements for 15:46:04 "documents" in general. It would be more appropriate to say that "A 15:46:06 document claiming conformance to this specification ... MUST be a 'schema 15:46:07 document' [2], as defined in [XML Schema 1.0 Recommendation], and MUST 15:46:10 therefore meet the "Constraints on the representation of schema components 15:46:10 in XML" [3] provided therein." Actually, there's a further mismatch on 15:46:12 infosets vs. serialization; see next point. 15:46:13 """ 15:47:38 http://www.w3.org/TR/2007/WD-xmlschema-patterns-20071031/#document-conformance 15:48:15 RESOLUTION: Accepted suggested text for lc-xsd-1 15:48:24 Topic: lc-xsd-2 15:48:42 """ 15:48:44 * 1.3 also says that a document conforming to the databinding 15:48:45 specification must be a well formed XML 1.0 document; XSD defines a 15:48:47 schema document as an Infoset with as the root element. You 15:48:48 should make clear whether the mismatch is intentional, and if so rewrite 15:48:50 the text suggested above accordingly. Otherwise, you should change to 15:48:51 indicate that a conforming document is infact an Infoset, consistent with 15:48:53 XSD. That will mean changing the many references to XML 1.0 documents 15:48:54 that appear throughout your draft. 15:48:56 """ 15:51:41 pauld: we discussed this early on, I should find evidence of our discussion, but we agreed to work at the XML level, and this is an addition constraint over the XML Schema spec, and this is a part of our relationship to the WS-I BP 15:52:32 RESOLUTION: Rejected lc-xsd-2 15:52:42 Topic: lc-xsd-3 15:53:20 """ 15:53:21 * Section 1.4 suggests that a conforming application "SHOULD be able to 15:53:23 process any valid [XML Schema 1.0] document.". First of all, there's some 15:53:24 question as to whether a SHOULD is appropriate in a conformance section. 15:53:26 Notwithstanding that, the reference to [XML Schema 1.0] documents is 15:53:27 again not strictly clear, since XSD talks about instances to be validated 15:53:29 as well as schema documents. We suggest a formal reference to 'schema 15:53:30 documents' [2] as in the first point above. 15:53:32 """ 15:55:53 pauld: whole point of our spec is that not all implementations can swallow any documents 15:56:29 http://www.w3.org/TR/2007/WD-xmlschema-patterns-20071031/#implementation-conformance 15:58:03 pauld: what would be the advantage of removing this? 15:58:21 yves: wouldn't impact people's reading of the document 15:59:20 pauld: anyone want to argue against removing: http://www.w3.org/TR/2007/WD-xmlschema-patterns-20071031/#assert-AnySchema 15:59:46 RESOLUTION: Accept lx-xsd-3 and remove assert-AnySchema 16:00:01 s/lx-xsd/lc-xsd/ 16:00:44 Topic: lc-xsd-4 16:00:50 """ 16:00:52 * Section 1.4 says that conformance requires that an implementation: " 16:00:53 MUST produce a data model exposing all of the [XML 1.0] element node and 16:00:55 attribute node content described by the originating [XML Schema 1.0] 16:00:56 document.", but "described by" is not a formal relation or operation 16:00:58 provided for in XSD. Especially in a conformance requirement, this seems 16:00:59 too informal. 16:01:01 """ 16:02:49 pauld: no alternative terminology suggested. "described by" is pretty OK by me, but then I'm no spec lawyer 16:03:21 .. any suggestions for better suggestion? 16:03:31 yves: "per" 16:03:43 pauld: or we could define "described by" 16:04:08 gcowe: "constrained by" 16:05:32 pauld: "constrained" is used throughout the XML Schema spec 16:06:08 RESOLUTION: Accpet lc-xsd-4 replacing "described" with "constrained" 16:08:05 s/Accpet/Accept/ 16:08:51 -Jonc 16:08:53 -pauld 16:08:54 -Yves 16:08:58 -George_Cowe 16:09:00 WS_DBWG()10:00AM has ended 16:09:00 rrsagent, generate minutes 16:09:00 I have made the request to generate http://www.w3.org/2008/03/11-databinding-minutes.html pauld 16:09:02 Attendees were George_Cowe, Yves, +0791888aaaa, pauld, +0800328aabb, Jonc 16:09:10 rrsagent, make logs public 16:33:26 pauld has joined #databinding 17:31:06 Zakim has left #databinding 18:57:47 pauld has joined #databinding