Clarify and improve triple store (or ditch it)

geneontology / project-management

Tracking project metadata in the GO as issues.

2 stars 0 forks source link

Clarify and improve triple store (or ditch it) #70

Open kltm opened 1 year ago

kltm commented 1 year ago

Project link

https://github.com/orgs/geneontology/projects/TBD

Project description

Lorem ipsum

PI

TBD

Product owner (PO)

TBD

Technical lead (TL)

TBD

Other personnel (OP)

TBD

Technical specs

TBD (template: https://docs.google.com/document/d/111UqtS3G0aJZpAijZYI3Da0t94OQpGePlPJsqZE4Tio/edit)

Other comments

N/A

pgaudet commented 1 year ago

AI add a note on the SPARQL endpoint that this is not exactly maintained (@suzialeksander to create a go website ticket to hide the SPQARQL endpoint more)

balhoff commented 1 year ago

The only place I know that it is linked is on https://geneontology.cloud/home

kltm commented 1 year ago

https://geneontology.org/docs/sparql https://geneontology.github.io/docs/tools-guide/

suzialeksander commented 3 days ago

@pgaudet there's been no action here. Should I go ahead and delete links to/mentions of sparql on the site, or do I leave the links intact with a note it's not maintained?