ISSUE-170: FURTHER INVESTIGATION: To examine adding EMMA attributes to enable annotation of type information on components of a semantic representation, e.g. distinguishing numbers from strings when they are coming from, e.g. JSON

For example, EMMA would provide attributes or elements in its namespace that could be used for typing values. An example from Michael Bodell from the June 2011 f2f:
<quan emma:type="number">3</quan> (where "quan" is in the application namespace.)
or emma:type="string"
For arrays,
<toppings emma:type="array">
<emma:item emma:index="100">pepperoni</emma:item>
<foo>bar</foo>
</toppings>
the SISR to produce the above is:
out.toppings = new Array();
out.toppings[100] = "pepperoni";
out.toppings.foo = "bar";

Discussed during June 14 call. Could certainly do this in the application namespace, maybe not really an EMMA problem, more generally a problem between JSON and XML.If strings, numbers and arrays are the only types we could put them in. Is there another solution that we could recommend? Is this a general W3C problem? We will check, if not, it's something we could easily add. Should they be optional? Seems like they should be.