Re: A use case for @vocab?

>
> > Having to specify the full list of properties would require shipping a
> > large structure to the thin client for basically nothing.
>
> Why for nothing? You are describing above a quite common use case..
>


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

{


    "Alert": {
        "@id": "http://smartplatforms.org/terms#Alert"

    },


    "Allergy": {

        "@id": "http://smartplatforms.org/terms#Allergy"


    },



    ...
}