Licensed deliverables: Difference between revisions

Revision as of 19:59, 9 June 2003

Licensed deliverables are registered with Sourceforge as several projects, e.g. dividing the project into three parts:

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.

Executables 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 producers, 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 GDL or some other viral license with terms to make it easy to keep code making similar assumptions together in one module.

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 factions 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 consumers.

@@ Line 1: / Line 1: @@
-'''[[License]]d [[deliverables]]''' are registered with [[Sourceforge]] as seve projects.  ''See [[Talk:Sourceforge]] and move what is necessary here.''
+'''[[License]]d [[deliverables]]''' are registered with [[Sourceforge]] as several projects, e.g. dividing the project into three parts:
+*[[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").
+''This will likely be a [[GDL]] or some other [[viral license]] with terms to make it easy to keep code making similar assumptions together in one module.''
+*[[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.