[SVGMobile12] Comments: 10 August 2006 Candidate Recommendation of SVG Tiny 1.2

Hi,

          I have the following comments to make with reference to SVG Tiny
1.2 - 20060810. I request that these be considered.

 

1.	Consistency check:
Location: A.3.2
<http://www.w3.org/TR/SVGMobile12/svgudom.html#Text_Node_Access>  Text
Content Access
"Text access via the TraitAccess interface is available on all SVGElements."
and
"Text access via the #text mechanism must be supported on Text Content,
'desc', 'title' and 'metadata' elements. Text access to other elements
defined within this specification (see list of elements) is not supported
and an implementation should ignore any text on these elements."
seem conflicting - "available but may not be supported".
2.	Completeness check:
Location: A.3.2
<http://www.w3.org/TR/SVGMobile12/svgudom.html#Text_Node_Access>  Text
Content Access
"Text access via the #text mechanism must be supported on Text Content,
'desc', 'title' and 'metadata' elements."
Have the <script>, <switch> and <handler> elements been omitted on purpose?
3.	Feature request:
An interface representing simple Text nodes (Ref: A.4.2 Node
<http://www.w3.org/TR/SVGMobile12/svgudom.html#dom__Node> ) for full
[clarity and] functionality via uDOM API for SVG based text-editors and
scripts.
4.	Change request:
With handheld devices in mind, consider a revision of current DOMString
<http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#DOMString
>  to a sequence of 8-bit units i.e., UTF-8 encoding for SVG Tiny 1.2.

 

Thanks :-),
Mathew K J
Advanced Technologies Division (ATD)
Samsung India Software Operations Pvt. Ltd.