Running example data

Throughout the documentation, we use the following running examples.

A full list of the current DZT domain specifications can be seen here.

Running examples

Event without identifiers

The following example is a JSON-LD file compliant with the Event domain specification.

{
  "@type": "https://schema.org/Event",
  "https://schema.org/description":"This is the running example event description",
  "https://schema.org/name":"Running example",
  "https://schema.org/startDate": "2023-05-16T18:00:00+02:00",
  "https://schema.org/url": "http://example.com/exampleEvent",
  "https://vocab.sti2.at/ds/compliesWith": {
    "@id": "https://semantify.it/ds/mhpmBCJJt"
  }
}

Important, each entity needs to state to which Domain Specification it complies with:

"https://vocab.sti2.at/ds/compliesWith": {
    "@id": "https://semantify.it/ds/mhpmBCJJt"
  }

LocalBusiness with external identifier

Next, a LocalBusiness based on the DZT LocalBusiness domain specification with an external identifier http://example.com/entity/LB1. Please note, that the PostalAddress has no explicit assigned identifier ( @id information are missing). During the import or update process, the system will assign an internal identifier to this object.

{
        "@id": "http://example.com/entity/LB1",
        "@type": "https://schema.org/LocalBusiness",
        "https://schema.org/address": {
            "@type": "https://schema.org/PostalAddress",
            "https://schema.org/addressCountry": "DE",
            "https://schema.org/addressLocality": "city",
            "https://schema.org/postalCode": "1234",
            "https://schema.org/streetAddress": "example street"         
        },
        "https://schema.org/description": "A simple description about the local business",
        "https://schema.org/name": "LocalBusinessTest",
        "https://vocab.sti2.at/ds/compliesWith": {
            "@id": "https://semantify.it/ds/uGBhB9lBI"
        }
    }