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

Fully specify what a bootstrapping environment is & MOP vocabulary #7

Open
aamedina opened this issue Aug 22, 2023 · 1 comment
Open
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@aamedina
Copy link
Owner

aamedina commented Aug 22, 2023

Problem:
The mop/*env* is a dynamic variable that specifies an environment where metaobjects are resolved during processing. If it is nil, the assumption is that you are searching required Clojure namespaces for the RDF terms that have names. Usually it is bound to either an XTDB node or Datomic database.

While convenient having this be a dynamic variable complicates many aspects of the protocol since the implementation of each method depends on the class of the environment.

Furthermore I think this is a good time to start thinking about what a fully specified MOP ontology in OWL would look like.

@aamedina aamedina added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 22, 2023
@aamedina aamedina self-assigned this Aug 22, 2023
@aamedina
Copy link
Owner Author

#14 may involve this as I need the ability for datafy to look into different environments based on the bound value of env. If I am separating the MOP from this library then the env variable should live in the primary rdf namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant