equal
deleted
inserted
replaced
9 <text xmlns="http://www.w3.org/1999/xhtml"> |
9 <text xmlns="http://www.w3.org/1999/xhtml"> |
10 |
10 |
11 <h2>Sane software</h2> |
11 <h2>Sane software</h2> |
12 <p> |
12 <p> |
13 <m:name/> (both the specification and the reference implementation) should be developed according to the <a href="https://sane-software.globalcode.info/">Sane software manifesto</a> (draft). |
13 <m:name/> (both the specification and the reference implementation) should be developed according to the <a href="https://sane-software.globalcode.info/">Sane software manifesto</a> (draft). |
14 Many of principles mentioned below are part of <em>being sane</em>. |
14 Many of the principles mentioned below are part of <em>being sane</em>. |
15 </p> |
15 </p> |
16 |
16 |
17 <h2>Free software and open specification</h2> |
17 <h2>Free software and open specification</h2> |
18 |
18 |
19 <p> |
19 <p> |
20 <m:name/> is and always will be a <a href="https://www.gnu.org/philosophy/free-sw.html">free software</a> and the specification of the format, tools and libraries will be open. |
20 <m:name/> are and always will be a <a href="https://www.gnu.org/philosophy/free-sw.html">free software</a> and the specification of the format, tools and libraries will be open. |
21 It must not be impaired by software patents or other similar restrictions. |
21 It must not be impaired by software patents or other similar restrictions. |
22 In our country, we do not accept the existence of patents at all. |
22 In our country, we do not accept the existence of patents at all. |
23 </p> |
23 </p> |
24 |
24 |
25 <h2>Divide and conquer</h2> |
25 <h2>Divide and conquer</h2> |
63 <p> |
63 <p> |
64 This is not a recommended approach, but should be possible. |
64 This is not a recommended approach, but should be possible. |
65 </p> |
65 </p> |
66 |
66 |
67 <p> |
67 <p> |
68 However, in any case, we should provide also an option of producing <em>raw</em> data in the <m:name/> format and allow others to convert it to any other format according their needs. |
68 However, in any case, we should provide also an option of producing <em>raw</em> data in the <m:name/> format and allow others to convert it to any other format according to their needs. |
69 </p> |
69 </p> |
70 |
70 |
71 <h2>Specification-first, contract-first</h2> |
71 <h2>Specification-first, contract-first</h2> |
72 |
72 |
73 <p> |
73 <p> |