mention aliases

Author: gtfierro

README.md

@@ -37,6 +37,10 @@ Specifically, `ontoenv` looks for patterns like the following inside local ontol
 
 When initialized, `ontoenv` searches the specified directories for ontology declarations, identifies their `owl:imports`, and recursively pulls in dependencies. Runtime queries operate on an in‑memory Oxigraph store. Persistent on‑disk state uses a compact RDF5D file at `.ontoenv/store.r5tu` with single‑writer, shared reader locking.
 
+### Canonical IRIs and Source URLs
+
+Ontologies fetched from a URL often declare a different, usually versioned, ontology IRI inside the file. `ontoenv` now remembers that relationship. When an ontology is added we record the source location and, if its declared name differs, create an alias from the normalized URL to the canonical ontology identifier. Future `owl:imports` that reference the versionless URL will therefore reuse the already downloaded ontology instead of refetching it. Removing an ontology clears any aliases associated with it, and loading an existing environment rebuilds the mapping automatically.
+
 ## CLI
 
 ### Installation

python/README.md

@@ -23,6 +23,11 @@ env = OntoEnv()
 brick_name = env.add("../brick/Brick.ttl")
 print(f"Added ontology {brick_name}")
 
+# When you add from a URL whose declared ontology name differs (for example a
+# versioned IRI served at a versionless URL), pyontoenv records that alias. You
+# can later refer to the ontology by either the canonical name or the original
+# URL when resolving imports or querying.
+
 # get the graph of the ontology we just added
 # env.get_graph returns an rdflib.Graph
 brick_graph = env.get_graph(brick_name)