pyLODE
pyLODE copied to clipboard
RDFLib
An OWL ontology documentation tool using Python and templating, based on LODE
Attempted to generate documentation for an ontology which included some text in Chinese- failed with a message about the character map. (Problem went away when I removed the Chinese). Here...
#46 got sidetracked and the main issue got lost. Datatypes need to be documented too. Examples: - https://github.com/CSIRO-enviro-informatics/geosparql-ext-ont/blob/dggs-issue7/geox.ttl#L77 - https://github.com/AGLDWG/asgs-ont/blob/master/asgs-id.ttl#L605 etc
The SKOSP profile can show the `broader`/`narrower` Concept hierarchy of a SKOS taxonomy and yet the OWLP profile only shows lists for `Class`/`Properties` which have hierarchical relations between them (`subClassOf`/`subPropertyOf`)....
Markdown and|or `^^rdf:HTML` literals should be enabled on the following properties uniformly: - `rdfs:comment` - `skos:note` and its sub-properties (including `skos:definition`) - `dc:description` / `dcterms:description` On the overall `owl:Ontology` rendering...
Many RDF properties that typically take string literals (^^xsd:string) may also have HTML fragments (^^rdf:HTML) which allows for formatted documentation. pyLODE currently re-writes these into pre-formatted code. This content should...
Use case: Useful when trying to build a custom HTML/CSS to render. When wanting to use frameworks such as SemanticUI or Bootstrap, classes need to be added in HTML elements...
We now have two profiles for documentation, OWLP & SKOSP, and they do different things. They need to be documented separately. - [ ] blend SNIPPETS content into README -...
Make FID generator use the same font case at class names so PIDs like `http://linked.data.gov.au/def/geofabric#ContractedCatchment` redirect to a working fragment, not the page top. Here for ContractedCatchment, currently only `http://www.linked.data.gov.au/def/geofabric/#contractedcatchment`...
Because rdflib and pyLODE are Python projects, and Python projects tend to lean towards using rST as the standard for the documentation, it would be great to have an rST...
* `owl:imports` * `prof:isProfileOf` * if this property is found, we should infer `owl:imports` * alignments to other ontologies * normal sub-classing/sub-propertying * will infer `owl:imports`