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

WaDE #94

Open
ksonda opened this issue Mar 23, 2021 · 0 comments
Open

WaDE #94

ksonda opened this issue Mar 23, 2021 · 0 comments

Comments

@ksonda
Copy link
Member

ksonda commented Mar 23, 2021

We're going to need to give some very specific guidance to WaDE, which is attempting to geoconnex up.

https://wade-mapbox-prototype.azureedge.net/details/UTwr_S204978 new landing pages for wade.

They dont want to embed the actual json-ld here, because they want to limit hits to their mapbox and don't necessarily want us crawling it, so they have implemented a separate json-ld page for each site.

https://wade-mapbox-prototype.azureedge.net/details/UTwr_S204978/json-ld

Something is wrong with those pages though. The source is a bunch of js injectio with no ld+json content.

Once that is solved, need to decide

  • Should PIDs just go to their JSON-LD endpoints directly?
  • If not, can their landing pages just not have a map? the source makes it look pretty inextricably tied to mapbox though
  • What should go in their json-ld? I know "SELFIE report stuff" generally but to start out I think we're just going to have to build a base community of example implementing partners that we have pretty much specified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant