- From: <tmichel@w3.org>
- Date: Tue, 30 Oct 2007 19:03:55 +0000
- To: Simon Pieters <zcorpan@gmail.com >
- Cc: www-smil@w3.org
Dear Simon Pieters , The SYMM Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Synchronized Multimedia Integration Language (SMIL 3.0) published on 13 Jul 2007. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below. Please review it carefully and let us know by email at www-smil@w3.org if you agree with it or not before 02 nov 2007. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the SYMM Working Group, Thierry Michel W3C Staff Contact 1. http://www.w3.org/mid/op.txxlkdbp7a8kvn@hp-a0a83fcd39d2.palace.opera.no 2. http://www.w3.org/TR/2007/WD-SMIL3-20070713/ ===== Your comment on Synchronized Multimedia Integration Language (SMIL 3.0)...: > Prior SMIL specs have introduced many namespaces: > > http://annevankesteren.nl/2006/03/smil > > It seems that SMIL 3.0 adds at least 63 more to this list: > > > http://www.w3.org/TR/2007/WD-SMIL3-20070713/smil-modules.html#smilModulesNSSMIL21ModuleXMLNamespace > > It says that: > > The XML namespace identifier for the complete set of SMIL 3.0 > modules, > elements and attributes, are contained within the following > namespace: > > http://www.w3.org/2007/07/SMIL30/ > > ...but this is not correct. Namespaces in XML are opaque strings. [1] > The > following are all completely different elements: > > <smil xmlns="http://www.w3.org/2007/07/SMIL30/"/> > <smil xmlns="http://www.w3.org/2007/07/SMIL30/AccessKeyTiming"/> > > You are effectively forcing implementors to ignore the namespace > altogether or use some other means that to deal with the 174 different > > namespaces in SMIL. As I understand it, it's also effectively > impossible > to write a RELAX NG schema for SMIL 3.0 because it uses multiple > namespaces. > > It is not appropriate to have several namespaces for the same language. > > Even with a new version of a language, if it is intended to be > backwards > compatible (work in UAs that only support an older version of the > language) it should use the same namespace. XHTML has only one > namespace. > SVG has only one namespace. MathML has only one namespace. And so > forth. > > Given that there already are 111 different namespaces for SMIL prior to > > SMIL 3.0, I would suggest that SMIL 3.0 clears this up by introducing > one > new namespace that is to be used for all future revisions of SMIL: > > http://www.w3.org/ns/smil > > ...and use a separate attribute to deal with module identifiers (e.g. > > module="AccessKeyTiming") if necessary. > > [1] http://www.w3.org/TR/REC-xml-names/#NSNameComparison Working Group Resolution (LC-1826): We will be using a single namespace for SMIL 3.0 http://www.w3.org/ns/SMIL. The single SMIL 3.0 namespace string will be specified in each SMIL 3.0 profile chapter. http://www.w3.org/ns/SMIL. We will also remove the following statement- section (2.4.2 in the LC document). : "The XML namespace identifier for the complete set of SMIL 3.0 modules,elements and attributes, are contained within the following namespace: http://www.w3.org/2007/07/SMIL30/" ----
Received on Tuesday, 30 October 2007 19:04:04 UTC