OntoViewer is an open-source project that is hosted by EDM Council. The project started in May 2019. OntoViewer is a JAVA application that is specifically designed to access both the ontology structure and its content in the easiest possible way. OntoViewer servers both as a web application and REST API.
Home Page: https://spec.edmcouncil.org/fibo/ontology
License: MIT License
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
The README.md file should give the port where docker runs the onto viewer instance.
We would like to change the way how OV configuration is loaded and handled.
Unit tests for configuration files
There are multiple issues in how the ontological characteristics of rdfs:label is displayed:
In the OV Toolkit we would like to have a way to map ontologies IRI to map to documents in the filesystem. For this, the --ontology-mapping command line parameter with the path to mapping file should be used.
The json returned from onto-viewer for a search request contains a typo: "totalResut".
This field should read "totalResult".
Note that when this is fixed we need to update the html-pages - see: edmcouncil/html-pages#110 (comment).
{
"type": "list",
"result": [
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/FBC/FunctionalEntities/MarketsIndividuals/Exchange-CCMX",
"label": "CARTAX",
"description": "",
"relevancy": 5,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/FundsTax",
"label": "funds tax",
"description": "",
"relevancy": 3.75,
"maturityLevel": {
"label": "provisional",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Provisional",
"icon": "develop"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/incursTax",
"label": "incurs tax",
"description": "",
"relevancy": 3.333333333333333,
"maturityLevel": {
"label": "provisional",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Provisional",
"icon": "develop"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/incursTax.1",
"label": "incurs tax",
"description": "",
"relevancy": 3,
"maturityLevel": {
"label": "provisional",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Provisional",
"icon": "develop"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/AccruedTaxes",
"label": "accrued taxes",
"description": "",
"relevancy": 2.5,
"maturityLevel": {
"label": "provisional",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Provisional",
"icon": "develop"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/FBC/FunctionalEntities/RegulatoryAgencies/TaxAuthority",
"label": "tax authority",
"description": "regulatory agency that has jurisdiction over the assessment, determination, collection, imposition and other aspects of any tax",
"relevancy": 2.5,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Parties/TaxIdentifier",
"label": "tax identifier",
"description": "identifier assigned to a taxpayer that enables compulsory financial charges and other levies to be imposed on the taxpayer by a governmental organization...",
"relevancy": 2.307692307692308,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/Bonds/SpecialTaxBond",
"label": "special tax bond",
"description": "bond secured by revenues derived from designated taxes other than ad valorem taxes",
"relevancy": 2.142857142857143,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/FBC/FunctionalEntities/MarketsIndividuals/Exchange-MKAA",
"label": "MARKETAXESS ATS",
"description": "",
"relevancy": 2,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
},
{
"iri": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/Bonds/TaxAllocationBond",
"label": "tax allocation bond",
"description": "bond payable from the incremental increase in tax revenues realized from any increase in property value and other economic activity, often designed...",
"relevancy": 1.7647058823529413,
"maturityLevel": {
"label": "release",
"iri": "https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Release",
"icon": "release"
}
}
],
"query": "tax",
"page": 1,
"hasMore": true,
"maxPage": 9,
"totalResut": 86
}
We would like to add a consistency check for ontologies to the OV Toolkit.
We want to re-implement the current searching capability with the usage of the Apache Lucene search engine.
All datatypes defined in FIBO should be displayed.
https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/FinancialDates/CombinedDateTime does not display.
Update the README file with Docker instructions for local setup.
We want to have a new goal in the OV Toolkit that will merge multiple ontologies into a new one.
The hint doesn't work on dev page.
OV should generate ontology modules when there aren't any specified ontology files.
It seems that usages of individuals are not shown.
Consider GB-284-RegionKind:
(from https://spec.edmcouncil.org/fibo/ontology?query=https%3A%2F%2Fwww.omg.org%2Fspec%2FLCC%2FCountries%2FRegions%2FISO3166-2-SubdivisionCodes-GB%2FGB-284-RegionKind.)
It does not show any usages despite the fact that UnitaryAuthority is used by GB-CBF-Subdivision:
(from https://spec.edmcouncil.org/fibo/ontology?query=https%3A%2F%2Fwww.omg.org%2Fspec%2FLCC%2FCountries%2FRegions%2FISO3166-2-SubdivisionCodes-GB%2FGB-CBF-Subdivision)
On the auto-viewer page, some classes from the VEHICLE SIGNALS ONTOLOGY (VS) are not displayed.
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/
For example:
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/MediaAction
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/AbsoluteLoad
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/GPSAccuracy
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/AirDistribution
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/AirStatus
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/MediaAlbum
https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/AmbientAirTemperature
Modify the Actuator prefix and add a custom status during the first load of the ontology.
We would like to have a tool that would generate a spreadsheet file based on an input ontology. This would replace code in ontology-publisher's product "datadictionary" (see: https://github.com/edmcouncil/ontology-publisher/blob/master/publisher/product/datadictionary/build.sh).
Ontoviewer seems to render in a different way language tags for rdfs:label and for datatypeproperties.
Some resources in FIBO are now displayed as rather long pages of text - see, for example, https://spec.edmcouncil.org/fibo/ontology/IND/EconomicIndicators/NorthAmericanIndicators/USEconomicIndicators/UrbanConsumerPriceIndex.
I think such pages were more readable if such long lists of items as generated descriptions will be displayed by default as collapsed provided that they are longer than, say, 5 items.
I think this change needs to be applied to all such lists, in particular to:
Legal Core Ontology shows string as an (external) object property, while it actually is a datatype:
Ontoviewer should not attempt to display empty lists of generated descriptions.
Ontoviewer displays empty lists of generated descriptions:
We need to use new find api endpoint (#144) for hints.
Currently, in many controllers, we use something like this:
LOG.debug("[REQ] GET : api / stats");
Instead of that, we would like to have more robust requests logging. This can be done using Spring's built-in logging capabilities.
To fulfill this task, check all of the existing controllers in onto-viewer and remove all manual request logging. Also, implement the aforementioned Spring-based request logging handling.
We need to be able to load ontologies in formats other than RDF/XML, e.g.:
We need to refactor search REST API endpoint so that it is split into two endpoints:
Note that the text searches are now handled by /api/find endpoint.
@trojczak
When using Find search API
https://github.com/edmcouncil/onto-viewer/blob/develop/api-doc/rest_api.md#10-find-search
some terms result in the error below:
Some examples of terms that return the error:
https://spec.edmcouncil.org/fibo/ontology/api/find?term=is
https://spec.edmcouncil.org/fibo/ontology/api/find?term=pl
https://spec.edmcouncil.org/fibo/ontology/api/find?term=en
https://spec.edmcouncil.org/fibo/ontology/api/find?term=and
https://spec.edmcouncil.org/fibo/ontology/api/find?term=pol
https://spec.edmcouncil.org/fibo/ontology/api/find?term=has
Some examples of API working as intended:
https://spec.edmcouncil.org/fibo/ontology/api/find?term=poland
https://spec.edmcouncil.org/fibo/ontology/api/find?term=privately
https://spec.edmcouncil.org/fibo/ontology/api/find?term=corporation
Request to https://spec.edmcouncil.org/fibo/ontology/IND/AllFBC/, which is not in FIBO, does not return any default 'page not found' response. Ditto for other mistyped URLs within the FIBO domain.
FIBO viewer should return some kind of 404 HTTP response - perhaps with some polite or tongue-in-cheek response like the ones on https://elementor.com/blog/404-page-inspiration/ or similar webpage.
No alternatives exist.
The following logs appear after the Add a new update request to the queue:
java[57503]: 2022-02-10 23:08:35,769 DEBUG [http-nio-0.0.0.0-9001-exec-9] org.springframework.web.filter.CommonsRequestLoggingFilter: Before request [PUT /auto/ontology/api/update, client=172.25.1.33, headers=[host:"172.25.1.32:9001", user-agent:"curl/7.61.1", accept:"application/json", x-api-key:"_API_KEY_"]] java[57503]: 2022-02-10 23:08:35,776 INFO [UpdateThread-1] org.edmcouncil.spec.ontoviewer.webapp.boot.UpdaterThread: Configuration loaded ? : true java[57503]: 2022-02-10 23:08:35,776 INFO [UpdateThread-1] org.edmcouncil.spec.ontoviewer.webapp.boot.UpdaterThread: File system manager created ? : true java[57503]: 2022-02-10 23:08:35,778 DEBUG [http-nio-0.0.0.0-9001-exec-9] org.springframework.web.filter.CommonsRequestLoggingFilter: After request [PUT /auto/ontology/api/update, client=172.25.1.33, headers=[host:"172.25.1.32:9001", user-agent:"curl/7.61.1", accept:"application/json", x-api-key:"_API_KEY_"]] java[57503]: 2022-02-10 23:08:40,140 INFO [UpdateThread-1] org.edmcouncil.spec.ontoviewer.webapp.search.LuceneSearcher: Starting to populate the Lucene index located on path 'lucene_index'... java[57503]: 2022-02-10 23:08:40,143 INFO [UpdateThread-1] org.edmcouncil.spec.ontoviewer.webapp.search.LuceneSearcher: 'reindexOnStart' not set in the configuration. Using application property value 'true'. java[57503]: 2022-02-10 23:08:40,143 INFO [UpdateThread-1] org.edmcouncil.spec.ontoviewer.webapp.search.LuceneSearcher: Search configuration property 'reindexOnStart' is on. Deleting the old index directory. java[57503]: Exception in thread "UpdateThread-1" java.lang.IllegalStateException: do not share IndexWriterConfig instances across IndexWriters java[57503]: at org.apache.lucene.index.IndexWriterConfig.setIndexWriter(IndexWriterConfig.java:129) java[57503]: at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:917) java[57503]: at org.edmcouncil.spec.ontoviewer.webapp.search.LuceneSearcher.populateIndex(LuceneSearcher.java:192) java[57503]: at org.edmcouncil.spec.ontoviewer.webapp.boot.UpdaterThread.run(UpdaterThread.java:175)
then all subsequent Get update status requests returns:
{ "id": "1", "status": "IN_PROGRESS", "msg": "", "startTimestamp": 1644530915773 }
and /actuator/health request returns:
{ "status": "UP", "components": { "custom": { "status": "UP", "details": { "UPDATE_ONTOLOGY_IN_PROGRESS": true, "BLOCKED": true, "INITIALIZATION_DONE": true } } } }
The update process should begin and then complete - get update status requests should return:
{ "id": "1", "status": "DONE", "msg": "", "startTimestamp": 1644530915773 }
curl -v -H 'Accept: application/json' -H 'X-API-Key: _API_KEY_' https://spec.edmcouncil.org/fibo/ontology/master/latest/api/update -X PUT
Onto-viewer backend changes required by new GUI
Please include in the search:
Currently, the FV search takes into account only rdfs:label(s).
We should separate code from ontology data, in particular, we should avoid maintaining manual update service - see #155 (comment).
So staticOntologies folder should be removed and code should be improved in such a way that when an imported ontology cannot be downloaded, it informs the user and keeps going.
Initially, we may just log the fact that some ontologies cannot be imported, but later we should log such messages in front end.
fibo-der-drc-raw:hasConversionRatio should be displayed.
FIBO viewer hangs on this request:
This bug may have to do with edmcouncil/fibo#1628, but in any case we should handle this issue somehow.
When requesting class with IRI through SearchApiController result.type is always null
For the data property types are displayed, e.g. xsd: anyUri, dateTime:
https://spec.edmcouncil.org/fibo/ontology/FBC/FunctionalEntities/MarketsIndividuals/Exchange-DASH
https://spec.edmcouncil.org/fibo/ontology/IND/MarketIndices/EquityIndexExampleIndividuals/DowJonesIndustrialAverageValue-2020-03-06T120514-0500
When hint functionality cannot find the appropriate concept in FIBO for a given search string, 'Cannot fetch data' error is thrown
Instead we should catch this error and handle it properly.
We would like to have a commit hash returned in the OV's status endpoint. OV Toolkit should also return a commit hash when asked for version.
https://spec.edmcouncil.org/fibo/ontology/IND/InterestRates/InterestRates/MarketDataProvider should have this generated description:
Market data provider may publishes published financial information.
or, even better, this one:
Market data provider may publish published financial information.
https://spec.edmcouncil.org/fibo/ontology/IND/InterestRates/InterestRates/MarketDataProvider has this generated description:
Market data provider publmay behes published financial information.
The ontological characteristics of data properties, including list of subproperties, should be displayed in the same way as the ontological characteristics of object properties are displayed:
ObjectProperties
DataProperties
The descriptions of some individuals are displayed in 'other' section.
Given recent changes in REST API, e.g., #152, documentation needs to be updated
https://spec.edmcouncil.org/fibo/ontology/BE/Corporations/Corporations/ shows external datatypes in other section.
This looks wrong to me.
Write configuration tests for the label provider.
We would like for OV Toolkit's goal 'extract-data' to be able to run quicker
MISSING_IMPORTS data needs to be moved from actuator to api rest endpoint.
If a list is empty, its 'header' should not be displayed.
For example, in the case below (https://spec.edmcouncil.org/fibo/ontology/IND/InterestRates/MarketDataProviders/ReferenceBanks)
OntoViewer logs available without logging into the production server
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.