3 Feb
2014
3 Feb
'14
6:50 a.m.
Hi Jarek What do you mean by the following sentence?
- Drop “dc:", "cc:" and "rdf:" namespaces and
remove any elements and attributes using them as this is just useless noise.
Isn't better to actually use those namespaces for proper attribution and license information?
As a FYI, "Commons Machinery" [1] is working on exactly this. I helped out last summer trying to figure out those parts in Inkscape but at that time the code base was to heavy to work with instead focus is put in other software areas [2, 3]. The lessons learned from "Commons Machinery" will definitely be useful in Inkscape in the future. The project just got another year of funding and have two developers working now. Anyone with ideas and questions can join #commonsmachinery on Freenode IRC network.
[1] http://commonsmachinery.se/ [2] http://commonsmachinery.se/labs/ [3] https://github.com/commonsmachinery/
Regards
--
Christoffer Holmstedt
2014-02-02 Jarek Foksa <jarek@...3085...>:
> Are there any plans for Inkscape to move away from XML namespaces when SVG
> 2, HTML 5 and Web Components will become widely supported and XML
> namespaces will get deprecated?
>
> If this is the case, I think it would be great opportunity to clean up the
> current namespace mess. Ideally, I would like to see all vendors of SVG
> editors to agree on a common “editor” namespace that would be implemented
> with HTML 5 data- attributes and custom elements.
>
> My proposal:
>
> 1. Drop “dc:", "cc:" and "rdf:" namespaces and remove any elements and
> attributes using them as this is just useless noise.
> 2. Drop "xlink:" namespace prefix (as defined by the SVG 2 spec).
> 3. Convert all elements in “inkscape:" and "sodipodi:" namespace to custom
> elements with "editor-" prefix (as defined by Web Components spec)
> 4. Convert all attributes in “inkscape:” and "sodipodi:" namespace to
> data- attributes (as defined by HTML 5 spec).
>
> For example following SVG 1.1 document generated by current stable version
> of Inkscape:
>
> <svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="
> http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
> xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
> xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
> version="1.0" width="1000" height="2000" viewBox="0 0 1000 2000">
> <sodipodi:namedview pagecolor="#ffffff" bordercolor="#666666"
> borderopacity="1" objecttolerance="10" gridtolerance="10"
> guidetolerance="10" inkscape:pageopacity="0" inkscape:pageshadow="2"
> inkscape:window-width="1366" inkscape:window-height="689"
> id="namedview1530" showgrid="false" inkscape:zoom="0.57"
> inkscape:cx="542.23281" inkscape:cy="1495.4813" inkscape:window-x="0"
> inkscape:window-y="27" inkscape:window-maximized="1"
> inkscape:current-layer="svg2"/>
> <image sodipodi:absref="/image.png" xlink:href="image.png" width="950"
> height="632"/>
> <path inkscape:connector-curvature="0" d="M 60,10 L -40,-45"/>
> </svg>
>
> ... could become this in future when saved as SVG 2 document:
>
> <graphics width="1000" height="2000" viewbox="0 0 1000 2000">
> <defs>
> <editor-namedview
> pagecolor="#ffffff"
> bordercolor="#666666"
> borderopacity="1"
> objecttolerance="10"
> gridtolerance="10"
> guidetolerance="10"
> pageopacity="0"
> pageshadow="2"
> windowwidth="1366"
> windowheight="689"
> id="namedview1530"
> showgrid="false"
> zoom="0.57"
> cx="542.23281"
> cy="1495.4813"
> windowx="0"
> windowy="27"
> windowmaximized="1"
> currentlayer="svg2">
> </editor-namedview>
> </defs>
> <image data-editor-absref="/image.png" href="image.png" width="950"
> height="632"/>
> <path data-editor-connector-curvature="0" d="M 60,10 L -40,-45"/>
> </graphics>
>
> Some related documents:
> - Custom elements: http://w3c.github.io/webcomponents/spec/custom/
> - Proposal for improving SVG DOM:
> http://dev.w3.org/SVG/proposals/improving-svg-dom/
> - Data attributes:
> http://www.whatwg.org/specs/web-apps/current-work/#embedding-custom-non-visi...
>
> Do you think this has any chance to get adopted by Inkscape? If not, do
> you have any alternative plan to improve the way how Inkscape stores
> non-standard data in SVG documents in the upcoming post-XML future?
>
>
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends. Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.cl...
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>