Plausible way to distinguish what goes in producer schema vs. producer config

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Put the data dictionary and mining fields into the schema (a current, 
typical, use-case of the 
baseline producer)
2.  The segmentation and model specification are put into the config file.
3.

What is the expected output? What do you see instead?

This seems ad hoc. the motiviation for it ought to be at least put into the 
documentation, or 
perhaps revisited.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by collinbe...@gmail.com on 5 Oct 2009 at 7:23

[GoogleCodeExporter]

Re-categorizing issues to belong to the 0.4.x version of Augustus.

Original comment by collinbe...@gmail.com on 30 Oct 2011 at 4:07

• Added labels: Release-4.x

[GoogleCodeExporter]

Marking all 0.4 bugs as low.

Original comment by collinbe...@gmail.com on 13 Apr 2012 at 5:53

• Added labels: Priority-Low
• Removed labels: Priority-Medium