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

High-level Strategy for rdf-vocabularies #118

Closed
6 tasks done
l00mi opened this issue Jan 25, 2022 · 0 comments · Fixed by #141 or #153
Closed
6 tasks done

High-level Strategy for rdf-vocabularies #118

l00mi opened this issue Jan 25, 2022 · 0 comments · Fixed by #141 or #153

Comments

@l00mi
Copy link

l00mi commented Jan 25, 2022

Requirements

  • Opinionated list of prefixes, and namespaces independently available.
  • Opinionated list of snapshotted ntriple dumps, and their definition how it was fetched on their (original) source.
  • Optional (added) metadata on the used meta-ontology and its used annotations (rdfs:label vs. schema:name). (RDFS/OWL etc.)

JS Requirements

  • Opinionated map of prefixes, and namespaces independently available.
  • Opinionated list of snapshotted transformed to RDF/JS quads.
  • Defined package structure / define ontologies in a NPM package.

Implementation

  • Ontology package -> annotation (prefix, how to get it) -> tiny (<5kb) (as Turtle) [authorative source]

    • updates JS prefix map (transformation)
    • publishes a NPM package with the JS prefix maps
  • Snapshots package -> uses the Ontology package

    • fetches (on the web) the snapshotted ntriple dumps (gzipped)
    • publishes a NPM package with the RDF-JS quads versions (only)
      • define an interface that covers the quads and metadata for external people to create compatible ontology packages
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

Successfully merging a pull request may close this issue.

1 participant