Licensed deliverables: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
*[[XML/DTD]] and [[XML/Schema]] documented also in [[ASN.1]] for [[Minimum Message Length]] and proof that the [[Consumerium protocol]] is efficient. ''This must probably be [[GFDL]].'' | *[[XML/DTD]] and [[XML/Schema]] documented also in [[ASN.1]] for [[Minimum Message Length]] and proof that the [[Consumerium protocol]] is efficient. ''This must probably be [[GFDL]].'' | ||
*[[Executable]]s which implement this protocol and data model / [[schema]] / [[foundation ontology]]; The goal is to let programmers sharing some list of concerns collaborate to improve the way [[Consumerium]] signals those concerns to the [[consumer]]. Knowing who can be trusted with what code, who is and is not a saboteur working for the [[producer]]s, is a key problem for which we need a [[trust model]] of some kind (this starts with "who will not break builds"). | *[[Executable]]s which implement this protocol and data model / [[schema]] / [[foundation ontology]]; The goal is to let programmers sharing some list of concerns collaborate to improve the way [[Consumerium]] signals those concerns to the [[consumer]]. Knowing who can be trusted with what code, who is and is not a saboteur working for the [[producer]]s, is a key problem for which we need a [[trust model]] of some kind (this starts with "who will not break builds"). ''This will likely be a [[GPL]] or some other [[viral license]] with terms to make it easy to keep code making similar assumptions together in one module, and prevent [[bad copy problem]] and [[self-interested fork problem]] GPL creates - but which [[open source]] makes worse! So maybe [[consortium license]] is needed, a specific [[Consumerium License]]?'' | ||
''This will likely be a [[ | |||
*[[Label data]] which can and must be consistently gathered and is what is subject to [[audit]] most often. The goal is to let organizations and people with [[expertise]] and historical, [[built trust]] in things like [[audit]], [[anti-brainwashing techniques]], [[fair]] [[economy]] and [[safe]] [[economy]] gather information from and about the [[producer]]. To avoid a [[centrally controlled information economy]] some party-like [[faction]]s must be involved - these control our bureaucracy and code. Labels data gathering must be up to th factions. ''These may create their own [[consortium]] with their own [[consortium license]]'', e.g. [[Greens]] will not let weapons companies use theirs, WAR FTP is not available for military use, but is a terrific product. Executables may also need to use the same license as the label data if there is a lot of markup specific to some [[faction]] that only that faction can be trusted to unravel for its own [[consumer]]s. | *[[Label data]] which can and must be consistently gathered and is what is subject to [[audit]] most often. The goal is to let organizations and people with [[expertise]] and historical, [[built trust]] in things like [[audit]], [[anti-brainwashing techniques]], [[fair]] [[economy]] and [[safe]] [[economy]] gather information from and about the [[producer]]. To avoid a [[centrally controlled information economy]] some party-like [[faction]]s must be involved - these control our bureaucracy and code. Labels data gathering must be up to th factions. ''These may create their own [[consortium]] with their own [[consortium license]]'', e.g. [[Greens]] will not let weapons companies use theirs, WAR FTP is not available for military use, but is a terrific product. Executables may also need to use the same license as the label data if there is a lot of markup specific to some [[faction]] that only that faction can be trusted to unravel for its own [[consumer]]s. |