Figure out consistent way to handle pre-defined property values

[cbashioum]

Need pre-defined values identified clearly and concisely. (e.g., for format, define minimum required as "kml", "geojson", "wms"). Channels and properties that have pre-defined values include:
a. Map.feature.plot - format, feature
b. Map.feature.plot.batch - format, feature
c. Map.feature.plot.url - format, feature
d. Map.vew.zoom - zoom
e. Map.view.center (and all the sub channels) – zoom
f. Map.view.clicked – button, type, keys
g. Map.status.request – types
h. Map.status.format - format
i. Map.status.about – version, type, extensions
j. Map.status.initialization – status
k. User manipulation
i. map.message.complete - status
ii. Details object for map.feature.edit – format, status, type
iii. Details object for map.feature.draw – type, format, type
iv. map.feature.draw – type, format, type
v. map.feature.clicked – button, type, keys
vi. map.feature.mousedown – button, type, keys
vii. map.view.mouseup – button, type, keys
viii. map.view.mousedown – button, type, keys
ix. Map.view.area.selected – button, keys
x. Map.menu.create – menuType
xi. map.feature.mouseup – button, type, keys
l. GeoJSON Support – timespan begin and end, timestamp
m. Area of Interest Support – type
n. Symbology – type
i. Symbology.Mil B – format, type (do we need more on symbolCode or modifiers?
ii. Symbology.Mil C – format, type (do we need more on symbolCode or modifiers?
o. Runtime Extensions
i. Drag and drop – format

[eric-briscoe]

Structure supports this now with the allowableValues keyword in the description files. Need to go through and make sure all of these are populated where applicable

[eric-briscoe]

Chris will verify this has been done