identify semantic-web-compatible file format

[7yl4r]

that is: in the headers we should use some sort of triple language (OWL?) to define the object the page represents.

The idea here is that the .md file header is used to define the semantic details of the page's object and the markdown content below generates an custom view of the object which uses the details from the header. Perhaps it makes sense to include some of the semantic information in the markdown? I am not sure. Here is an example page content:

title: a thingy
----
# {{thingy}}
This is the page about the thingy.

[7yl4r]

• search result for example .owl files from github
• open bio ontology foundry
• WebVOWL cool visualizer of ontologies
• stanford web-protege
• OWLGrEd viewer
• LODE OWL-to-human-readable-html-renderer

[7yl4r]

1. sparql query to create a webpage. view of each result based on the type of the results?
2. sparql query to find a programming function with given outputs, inputs, and other characteristics.
3. sparql-powered programming language, enabling maximally-DRY code

[7yl4r]

• visualize w/ webVOWL
• deploy w/ SaGe client & server

steps:

1. set up SaGe server
2. load appropriate onthologies
3. create .owl files/pages for wowchemy data & product browser
4. create view of SPARQL query result

[7yl4r]

okay. I think I have finally learned enough to come to the following conclusion: This project led to me reinventing semantic web concepts. Luckily those already exist. SaGe seems to be the best stack for building upon, but for most things it is probably better to use (and extend) wikidata and their SPARQL endpoint query.wikidata.org.

I will be exploring creation & editing of wikidata pages in place of things I usually create a spreadsheet for.

From there it may make sense to create a template renderer for SPARQL query results.