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
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
- State:
- OPEN
- Product:
- EMMA 1.1
- Raised by:
- Opened on:
- 2010-11-18
- Description:
- Related Actions Items:
- No related actions
- Related emails:
- Re: [emma] subgroup meeting 080212 (from ashimura@w3.org on 2012-08-02)
- Re: Self introduction: Hiroshi Yamada, NEC, Japan (from ashimura@w3.org on 2012-07-17)
- [emma] minutes June 28, 2012 (from dahl@conversational-technologies.com on 2012-06-28)
- [emma] June 21, 2012 minutes (from dahl@conversational-technologies.com on 2012-06-21)
- ISSUE-170: 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 (from sysbot+tracker@w3.org on 2010-11-18)
Related notes:
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.
Deborah Dahl, 14 Jun 2012, 14:42:37Display change log