Add second "bucket" for facility-specific workflows - things we are gong to call Arbitrary Parameters

[GoogleCodeExporter]

Geometric types to provide a second compound property for storing of workflow 
specific attributes that aren't typically meant to be passed to a renderer.

Original issue reported on code.google.com by cookingw...@gmail.com on 6 Jul 2011 at 3:27

[GoogleCodeExporter]

This seems like a good idea, but I can't tell if there is still strong 
opposition to this or not. Discuss further, get buy off.

Original comment by ble...@gmail.com on 7 Jul 2011 at 10:03

• Added labels: Milestone-1Disc, EstimateInDays-2

[GoogleCodeExporter]

The controversial part was whether our reference implementations would natively 
support it.  I think we've agreed that it wouldn't, and we would provide the 
hooks for handling this via Issue 179.

As far as I know it's no longer controversial.

Original comment by miller.lucas on 7 Jul 2011 at 10:21

[GoogleCodeExporter]

Part of the question is should the schema types in AbcGeom provide a method 
getUserParams () that like getArbGeomParams () would return a 
compooundProperty. This way we'd have a specific idiom people should use (e.g. 
call getUserParams () and create your your workflow-specific extra properties 
there)

Original comment by ble...@gmail.com on 7 Jul 2011 at 10:26

[GoogleCodeExporter]

Original comment by ble...@gmail.com on 7 Jul 2011 at 10:26

• Added labels: Priority-P1

[GoogleCodeExporter]

Original comment by ble...@gmail.com on 8 Jul 2011 at 2:10

[GoogleCodeExporter]

Original comment by ble...@gmail.com on 8 Jul 2011 at 2:20

• Added labels: EstimateInDays-1
• Removed labels: EstimateInDays-2

[GoogleCodeExporter]

Created new issue with shorter description of task.

Original comment by ble...@gmail.com on 11 Jul 2011 at 8:35

• Changed state: Duplicate