TIPP: Codify object sections, add "Extras"

[GoogleCodeExporter]

This issue came out of the Linport discussions.  The proposed change is:

* Right now each core task defines, for example, its own version of the 
"bilingual" section, even though they serve the same purpose.  (If you look at 
the URIs in the task definitions you will see that this is true.)  Under the 
Linport proposal, the sections used by the core tasks would be consolidated 
into a set of core sections (ie, there would be one URI for the bilingual 
section, the tmx section, the sts section, etc....) that could be shared 
amongst approved/core task types.
* Additionally, we would define a new object section called "Extras".
* New/custom task definitions would be restricted to only using the core 
sections.  Anything that didn't fit into one of the well-defined sections like 
bilingual/tmx/sts/etc would go within "extras".  Within the "extras" section, 
arbitrary folder structure could be imposed by the custom task definition.
* Over time, it is expected that more custom task types could be "promoted" to 
the core spec as approved task types.  When this happened, any use of "extras" 
would be replaced with a core section.  The set of core sections could also be 
expanded over time.

Original issue reported on code.google.com by tingley on 29 May 2012 at 5:35

[GoogleCodeExporter]

Original comment by tingley on 23 Jul 2012 at 3:46

• Added labels: Milestone-TIPP1.5

[GoogleCodeExporter]

Original comment by tingley on 2 Mar 2013 at 3:56

• Changed state: Fixed