You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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:
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.
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
The text was updated successfully, but these errors were encountered: