json-ld | Ruby JSON-LD reader/writer for RDF.rb | JSON Processing library

You can simply continue by using the advertools SEO crawler. It has a crawl function that also extracts structured data by default (JSON-LD, OpenGraph, and Twitter).

I tried to crawl a sample of ten pages, and this what the output looks like:

What you want to do is remove the @vocab definition within license, alias spdx_id to @id, and remove the default vocabulary. This treats the object value of license as a node object (really node reference) as all keys other than spdx_id are ignored. See playground link here.

As described here, the NGSI-LD interface is a flexible API which outputs various JSON and JSON-LD formats and is used for data exchange. The tutorials are describing the correct use of the interface only. They do not cover production deployments.

After I restart the tutorial all data i have written is deleted.

The tutorials are just that - they start from a clean slate. The Mongo-DB instance in the docker-file does not have a persistent volume and cleans up after itself.

it accepts any data, ignoring the data-model.

That is because JSON-LD @context isn't used to validate JSON data - you need a JSON schema for that. Technically the @vocab element in the NGSI-LD core context @context file pushes any unknown elements onto the so-called default context https://uri.etsi.org/ngsi-ld/default-context/. The @context file is simply providing a mechanism to standardize the attribute names into IRIs. Assuming you have created a Swagger/Open API file for your use case, then you can use the Swagger editor to generate server or client code stubs. Doing this in Java say, will result in a POJO which just accepts the attributes of your model.

How to setup the orion context broker

You could use the docker-compose provided as a basis for getting started, but for proper large scale deployments on Kubernetes, the provided Helm Charts are recommended. The Orion-LD documentation goes into more details.

How to provide the context File to the Context Broker

You place the @context file on a public web server. How you host your @context file is up to you. The tutorials use HTTPD for this purpose. The main idea behind an @context is that you are publishing an agreed set of IRIs which correspond to the attributes in your data. Smart Data Models, Schema.org, GS1 and plenty of other bodies generate IRIs, you should reuse them and link to them or publish your own @context describing your own world.

Once an @context just append the Link header to each context broker request.

Nuxt 3 support will be added soon: https://github.com/ymmooot/nuxt-jsonld/issues/763

HTTPS is HTTP over TLS. In the context of vocabularies and namespaces these URIs are just opaque strings, they will never be visited so whether the scheme is http or https doesn't matter for security. Maybe software will compare those strings if they match to know what type of document it is, but nothing will visit those URIs.

Just use whatever URI is defined in the standards that you follow, use the same exactly. So if the standard says http:// use that, and if it says https:// then use that, don't change them. Know that it has no impact on security.

Older standards use the http protocol, and newer standards may use the https protocol, but it really doesn't matter, they're just opaque strings to match against, not to connect to.

It looks like you are doing it correctly. In JSON-LD you can use any of the properties of a class in any of its subclasses.

In order to validate your JSON-LD, I have used the Google's structured tool JSON-LD validator, available at https://validator.schema.org/. I think you may find it useful in the future.

Your snippet passed the tests with zero errors or warnings. Just be careful with "logo.svg", because it is a relative path.I would add the full URL to your logo. The same applies for img.jpg

That's because there is no key "SportsEvent" in your item. Its a value under the key '@type'.

So you'd need to alter your save_teams() function to:

The Rich Result Tester only reports on Structured Data that contributes to Rich Results in Google.

Their Search Gallery is a good place to learn about what can cause Rich Results:

https://developers.google.com/search/docs/advanced/structured-data/search-gallery

If you look at just the JSON and remove all your PHP and parse it through a JSON validator you will realise that the error is that you do not close the JSON block. If you remove the PHP and replace "value": {{$post->salary_max}}, with "value": "{{$post->salary_max}}", just so a JSON validator is able to eat it.