Variable-type (object vs array vs string) syntax elements in Moonwalk

[handrews]

@darrelmiller it's been observed that both the original Moonwalk proposal and the imports idea (as seen in the Deployments proposal) handle certain things by changing the type of a field's value. Specifically:

• when importing an object value, a string is used in its place (imports/deployments)
• when combining multiple references, an array is used in place of an object (original proposal)

The questions that come up include:

• Is this a general syntax approach that we want to use?
• are there any situations where the "normal" value is not an object, but something else that might conflict with type variations? (see also Map vs list in responses (and in general) #25 and Consideration for moving from objects to arrays. #32)
• how will implementors using strictly typed languages feel about this?