- From: Tom Underhill <Tom.Underhill@microsoft.com>
- Date: Tue, 28 Sep 2010 03:21:05 +0000
- To: Dominique Hazael-Massieux <dom@w3.org>
- CC: "www-multimodal@w3.org" <www-multimodal@w3.org>, "smwatt@gmail.com" <smwatt@gmail.com>
- Message-ID: <4045AB4EE43EB94C9508DDC490FA9F7127C59C10@DF-M14-02.exchange.corp.microsoft.com>
Hello Dominique, Thank you for your responses. Regarding Comment #165 about the "DefaultCanvas" reserved id: I have added language to the spec to explicitly describe the id "DefaultCanvas" as being reserved and therefore unavailable to be used as the id of a user defined <canvas> element. The same applies to the "DefaultContext" reserved id, so I also added language for that id. The "DefaultTraceFormat" id already had language describing it as reserved. The last paragraph in section 4.5 changed to: The default context may be explicitly specified using the URI "#DefaultContext". The id "DefaultContext" is therefore reserved and may not be used as the id of a user defined <context> element. The last paragraph in section 5.3 changed to: The default canvas may be explicitly specified using the URI "#DefaultCanvas". The id "DefaultCanvas" is therefore reserved and may not be used as the id of a user defined <canvas> element. Regarding Comment #173 about the schema not allowing channel names to repeat within a file: my apologies, when I read the comment I didn't catch that it was a comment against the schema, not the spec. You are absolutely right, the schema is broken. I removed the key/keyref from the XSD. The latest XSD is attached. -----Original Message----- From: Dominique Hazael-Massieux [mailto:dom@w3.org] Sent: Monday, August 30, 2010 1:39 AM To: Tom Underhill Cc: www-multimodal@w3.org; smwatt@gmail.com Subject: Re: [ink] Responses to your comments on the W3C InkML Working Draft Le lundi 30 août 2010 à 00:14 +0000, Tom Underhill a écrit : > ============ > Comment #152: > ------------ > * the abstract says that InkML is for "in the W3C Multimodal > Interaction Framework as proposed by the W3C Multimodal Interaction > Activity"; it looks to me that it is not restricted to that usage, so > I would remove that phrase > ------------ > Resolution: accepted > ------------ > Changed to: > > This document describes the syntax and semantics for the Ink Markup > Language. The Ink Markup Language serves as the data format for > representing ink entered with an electronic pen or stylus. The markup > allows for the input and processing of handwriting, gestures, > sketches, music and other notational languages in applications. It > provides a common format for the exchange of ink data between > components such as handwriting and gesture recognizers, signature > verifiers, and other ink-aware modules. It may be used in the W3C > Multimodal Interaction Framework as proposed by the W3C Multimodal > Interaction Activity. It's an improvement, thanks; I think it's a bit long, but clearly this is up to your editorial discretion :) > Comment #165: > ------------ > * the existence of DefaultCanvas (5.3) means that this id cannot be > used anywhere else as id in an InkML document ; that should probably > highlighted much more visibly; wouldn't it make more sense to have > that URI a non-relative URI, but a well-known URI à la > http://www.w3.org/ns/inkml/canvas#default ? > ------------ > Resolution: rejected > ------------ > There are already implementations the use "#DefaultCanvas" How do they react when an element in an InkML file as an id of "DefaultCanvas"? In any case, even if the spec isn't changed (which seems sub-optimal to me), I strongly recommend calling out explicitly the restriction on the authorized ids. It probably ought to be added to the XML Schema as well if that's technically possible. > Comment #173: > ------------ > * the schema forbids having more than one <channel> element with the > name "X" (or "Y") - that seems like a bug (or the first example in 7.1 > is buggy) > ------------ > Resolution: rejected > ------------ > You may not have more than one <channel> with the same name within a <traceFormat>. That's not what the XML Schema enforces: <xsd:element name="ink" type="inkml:ink.type"> <xsd:key name="channelNameKey"> <xsd:selector xpath=".//inkml:channel"/> <xsd:field xpath="@name"/> </xsd:key> says that no channel can have the same name anywhere in an InkML document. HTH, Dom
Attachments
- text/xml attachment: inkml.xsd
Received on Tuesday, 28 September 2010 03:26:29 UTC