Transporting document fragments
Problem: Conforming Included SVG Document Fragments must be surrounded by an <n:svg xmlns:n="blabla">...</n:svg>. We cannot append these to the main document, so we would have to walk through each child element.
In addition, I imagine we would not be able to append completely arbitrary svg elements to <n:svg>, just as you can't append <input> to <body> in XHTML.
Possible solution: as in transport limitations, transport all SVG escaped. Grr...
Possible solution: ignore the spec and do it anyway.
Possible solution: use some pseudo-SVG namespace over transport (e.g. not://2000/svg)
- up:
- it works
- provides discrimination, which is what we want.
- down:
- so we have to do this with every doctype we transfer that has strict fragmenting rules? I don't think so.
Chosen solution: ignore the spec and do it anyway.
Each chunk from a chunked HTTP transfer doesn't have to be a conformant XHTML document.
It's in transport. Think of it as a diff or a patch. Diffs don't compile. There's no requirement to be a valid SVG document in transport.
© 2006. Some rights reserved. Author: Ian Sollars.
