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

identify the shapes for which to develop ShEX #67

Open
9 tasks
egonw opened this issue Jun 10, 2019 · 7 comments
Open
9 tasks

identify the shapes for which to develop ShEX #67

egonw opened this issue Jun 10, 2019 · 7 comments
Assignees

Comments

@egonw
Copy link
Member

egonw commented Jun 10, 2019

The list (growing):

  • Pathway
  • DataNode
  • GeneProduct
  • Protein
  • Metabolite
  • Interaction
  • DirectedInteraction
  • TypedDirectedInteraction
  • ...
@egonw
Copy link
Member Author

egonw commented Jun 10, 2019

Okay, done:

But now I'm stuck (cc @andrawaag @nunogit):

image

I think we first need HTTPS support on http://sparql.wikipathways.org/ first.

@egonw egonw self-assigned this Jun 10, 2019
@ericprud
Copy link

Yeah, the HTTPS miltia has seized control of the browsers. You're basically stuck setting up HTTPS everywhere in order to work in today's Web.

@egonw
Copy link
Member Author

egonw commented Jul 13, 2019

HTTP is working now.

@ericprud
Copy link

Meaning the browser is is no longer refusing to load HTTP resources? Is it because the rawgit image you loaded was from HTTP instead of HTTPS?

@egonw
Copy link
Member Author

egonw commented Jul 15, 2019

Interesting questions. Not sure. I always thought it was the HTTP/-S difference between the currently loaded HTML and the additional remote resources that mattered, not just between the additional remote resources.

Anyway, the one thing that changed is that the WikiPathways SPARQL endpoint now supports HTTPS too.

I also note the typo in my comment of two days ago, which should have said: "HTTPS is working now" :)

@ericprud
Copy link

I also note the typo in my comment of two days ago, which should have said: "HTTPS is working now" :)

Ahh yes, that implies a different subject.

Re HTTP/S. This is a continuously-shifting battle-ground. As last I understood it, most browsers would refuse to fetch HTTPS from a page loaded with HTTP. At some point after that change, I believe rawgit changed to only serve HTTPS, which had the effect of requiring that all required resources be available by HTTPS. Then the squirrels arrived and chewed off my fingers and I swore off web development forever.

@egonw
Copy link
Member Author

egonw commented Oct 7, 2020

Some initial info here: https://github.com/egonw/shexWorkingBio/blob/master/index.md

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