- From: Simon Grant <asimong@gmail.com>
- Date: Fri, 4 Oct 2013 13:13:50 +0100
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-linked-json@w3.org
Received on Friday, 4 October 2013 12:14:18 UTC
On 4 October 2013 12:02, Markus Lanthaler <markus.lanthaler@gmx.net> wrote: > On Friday, October 04, 2013 12:48 PM, Simon Grant > [...] > > > To me (and possibly others) it would be helpful either > > (a) to put a note in section 5.4 in any case -- not talking about > > type coercion, but simply noting that @type arrays cannot be used > > within @context (you don't have to say why at that point), or > > What about adding a statement saying that using @type in the context > cannot be sued to specify the node's type but is used for type coercing > values? I think that would also address the overloading issue. > Something like that would be fine with me, and I think would serve the purpose as you suggest. > > > > (b) to dis-overload (?) @type, so that within @context there is > > "@valuetype" or something, with @type reserved for nodes outside > > the context. > > I don't like that because it introduces other problems (people have to > remember one more keyword, need to know when to use which, etc.) > I'm fine with that. No problem. Thanks! Simon -- from Simon Grant +44 7710031657 http://www.simongrant.org/home.html
Received on Friday, 4 October 2013 12:14:18 UTC