Schema JSON-LD standards closing the gap toward RDF paradigm
The Schema vocabulary receives 3 new elements that provide clues about the general direction taken by the most popular initiative on Structured Data.
The Schema standard offers these 3 new elements, its mere existence together with the independent initiative of json-ld.org suggests that the use of Schema is being oriented beyond the markup on HTML and the Rich Snippets, towards a more diversified, multilayer (TCP) and clearly betting on the Linked Data.
Do not forget that Linked Data correspons to the “LD” at JSON-LD.
Thus, the W3C Semantic Web working groups are bringing Schema JSON-LD closer to the world of RDF and the exchange of data between different platforms, in a distributed environment.
Detailed review of the new Schema elements
As far as my professional opinion is concerned, these Schema elements must appear in any script that does not have size restrictions, although this is going very far to the limit… To give us an idea, implement the 3 Schema elements correctly , using the ProfessionalService element to define me as sdPublisher, it costs exactly 814 bytes of code that are added to the total weight of the page to load.
Coherently for a professional SEO CMS, the new version of Relevant CMS that we will have available at the end of T1 2019 will incorporate these three Schema elements in a configurable way; they will allow us (for example) to differentiate our Schema authorship in the code of our SEO Structured Data service, from whatever the client content is. Remember that the Google Structured Data tandem has its own anti-spam rules!