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

define a mapping of iso19139 to schema.org/dataset #1

Open
pvgenuchten opened this issue Nov 17, 2015 · 4 comments
Open

define a mapping of iso19139 to schema.org/dataset #1

pvgenuchten opened this issue Nov 17, 2015 · 4 comments

Comments

@pvgenuchten
Copy link

Search engines use the http://schema.org vocab to analyse content that they crawl. To make search engines understand iso19139 a mapping to schema.org should be made available. For those iso19139 aspects currently not available in schema.org, we can suggest an extension of schema.org.

This mapping can be implemented in GeoNetwork in 2 ways:

  • create a schema.org schema-profile, which can be set up to store metadata using the schema.org model and transform documents to other schema's. The output format (xml,rdf,json) is arbitrary
  • add a new schema.org output format (json-ld), which can be adopted by all schema-profiles (this is how the transformation to DCAT is currently implemented)

Option 1 may over time be the best option, however may have too much impact in the scope of the current testbed.

There is a number of ways to expose schema.org so it can be ingested by search engines.

  • as RDFa/microdata, where the model is embedded in html
  • as json-ld embedded in <script/> tags in html
  • as json-ld

The advantage of options 1 & 2 is that users using a webbrowser to browse the web will see attractive content once they click a search-result in a search engine. The advantage for 3 is that webdevelopers can use the API to develop applications to.

Content negotiation will guide webbrowsers to html representations and machines to json representations of the documents

@Delawen
Copy link

Delawen commented Nov 17, 2015

If we are thinking on crawlers we will probably need some kind of list (rss?) for schema.org formatted data, right?

And link that list from the robots.txt

@pvgenuchten
Copy link
Author

@Delawen, You mean a startpoint of the crawl (bootstrap)? The geonetwork sitemap will do, make sure it supports pagination though

@pvgenuchten
Copy link
Author

Please mind this initiative: http://www.w3.org/wiki/WebSchemas/Datasets and http://blog.schema.org/2012/07/describing-datasets-with-schemaorg.html to see if we can use or contribute to some of their work. Discussion moved to github, for example schemaorg/schemaorg#713, schemaorg/schemaorg#688, schemaorg/schemaorg#583, schemaorg/schemaorg#113

@Delawen
Copy link

Delawen commented Nov 17, 2015

Links of interest:

http://schema.org/docs/full.html
http://schema.org/DataCatalog: not sure if useful to define the GeoNetwork instance or just a very big dataset.
http://schema.org/Dataset
http://schema.org/DataDownload
http://schema.org/Map

@Delawen Delawen removed their assignment Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants