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

More discussion is required on how to structure meaningful (spatial) queries with search engines #181

Closed
6a6d74 opened this issue Jan 3, 2016 · 2 comments
Labels

Comments

@6a6d74
Copy link
Contributor

6a6d74 commented Jan 3, 2016

Relating to Best Practice 25: Make your entity-level data indexable by search engines, more discussion is required on how to structure meaningful (spatial) queries with search engines (e.g. based on identifier, location, time etc.).

@6a6d74
Copy link
Contributor Author

6a6d74 commented Jan 3, 2016

During the SDW f2f meeting during TPAC, Sapporo, @danbri demonstrated that Google can provide search over structured content; example of structured markup (https://developers.google.com/structured-data/testing-tool/?url=http://travel.cnn.com/tokyo/sleep/hokutosei-sleeper-train-tokyo-sapporo-905418) which has 'City' named 'Tokyo' … Google Custom Search restricted to pages describing a schema:City: https://cse.google.com/cse/publicurl?cx=013484121852858951051:_k8pkh6pfio

Can this be turned into an example / commentary? (not necessarily by @danbri - but his help would be useful).

@6a6d74
Copy link
Contributor Author

6a6d74 commented Feb 2, 2017

At the SDW face-to-face meeting in London, December 2016, we agreed the following:

this is not a data publishing issue; you need to create the rich data before you can begin to do simple queries

Creating the queries is beyond the scope of our discussion about how to publish spatial data on the Web.

Closing this ISSUE.

@6a6d74 6a6d74 closed this as completed Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants