- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Fri, 25 May 2012 00:38:45 +0800
- To: "'Josh Mandel'" <Joshua.Mandel@childrens.harvard.edu>
- Cc: 'François Daoust' <francois@joshfire.com>, "'Linked JSON'" <public-linked-json@w3.org>
> I think François is advocating for `@vocab` for the same
> reason we have prefixes: to avoid having to explicitly define
> *every* predicate with the same prefix. (It's not "built-in,"
> it's established in a context.) The special thing about
> `@vocab` is to establish an *empty* prefix, with no colon.
> And this might sound trivial (?), but colons make property
> names really annoying to work with in JavaScript.
>
> E.g. with @vocab the SMART context could be ~1k instead of 16k
Oh sorry.. then I completely misunderstood his mail.
> "Alert": {
> "@id": "http://smartplatforms.org/terms#Alert"
You know that you can use prefixes in the context as well!? Something like
{
"@context": {
"spt": "http://smartplatforms.org/terms#",
"Alert": "spt:Alert",
...
},
.. data (not using prefix) ..
}
I'm still not convinced that @vocab would be a good idea.. there are many
ways to solve this in an application but of course it depends on the
application's specific requirements.
--
Markus Lanthaler
@markuslanthaler
Received on Thursday, 24 May 2012 16:39:34 UTC