Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implement schema.org in responses #33

Open
tomkralidis opened this issue Apr 19, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@tomkralidis
Copy link
Member

commented Apr 19, 2018

@pvgenuchten

This comment has been minimized.

Copy link
Contributor

commented Apr 11, 2019

schema.org is relevant in the html encoding of collections/features. However it can also be added to a json representation, as a json-ld context. But consider that json-ld is currently incompatible with geojson. To support json-ld a response encoding application/ld+json should be added.

Various vocabulaires exist to annotate geometry, a suggestion was made at the final geo4web conference why not add all of them. A selection can be made from geojson-ld, geosparql and https://schema.org/geo. Last years the schema.org/geo vocabulaire was limited, but it will probably improve.

There are generally 2 options to add schema.org annotations, embed a json-ld representation of the content or add microdata to each of the html tags. The first approach seems most valid, as a json representation of the object is already available in the software.

For each collection a configuration option should be added (like available in ldproxy) to define definitions for the objects in the collection (what type of schema.org/Thing (or any other vocab) does it contain). An alternative starting point could be the vocabulaires defined for INSPIRE. Then for each Feature property a mapping should be made to a schema.org property of the Thing. This configuration can then be used to generate the ld-context.

A good place to get started with structured text in html pages is https://search.google.com/structured-data/testing-tool

@pvgenuchten

This comment has been minimized.

Copy link
Contributor

commented Apr 11, 2019

For the api and collections page, consider to define the parent (api) as a schema.org/DataCatalog, and each of the collections as a schema.org/Dataset, the api will then auto-popup in https://toolbox.google.com/datasetsearch

DataCatalog

  • name: Api-title
  • description: Api description
  • author: Api contact
  • dataset
    • name: collection title
    • description: collection description
    • distribution: dataDownload
      • contentUrl: features/collections/things/items?f=gml
      • encodingFormat: application/gml+xml
    • ...
  • dataset
    • name: collection title
    • description: collection description
    • distribution: dataDownload
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.