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

Explore alternate ways to generate and display data model #236

Closed
gxclark opened this issue Apr 12, 2024 · 8 comments · Fixed by #242
Closed

Explore alternate ways to generate and display data model #236

gxclark opened this issue Apr 12, 2024 · 8 comments · Fixed by #242
Labels

Comments

@gxclark
Copy link

gxclark commented Apr 12, 2024

While the main modeling activity is using OWL, the primary published data model does not seem to be in a standardized format, such as ... IDEF1X, Martin/ER/IE, UML ...
https://en.wikipedia.org/wiki/IDEF1X
https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model
https://en.wikipedia.org/wiki/Class_diagram

A while back, ~2020, I "reverse-engineered" ... (mostly manual) the PDF and XLSX files into an ER diagram in Oracle Data Modeler, see image below. This is now out of date, but is there a way to be able to produce this type of improved artifact as part of the standard model development process?

image

@NiclasScheiber
Copy link
Contributor

Very good, I support this. I would also suggest to create a mkdocs page akin to the api
https://iata-cargo.github.io/ONE-Record/
to document the concepts and most complex elements in written form.

@lambertciata
Copy link
Collaborator

Hi @gxclark thanks for the issue. This is something we always had in mind but also always struggled with because:

  1. Our main objective is to maintain the ontology
  2. The gap between the ontology and any vizualisation (apart from vOWL) can only be manual, and it is becoming quite big.

We have for instance a detailed view of the ontology here: https://onerecord.iata.org/ns/cargo/index-en.html This is automatically updated with the ontology and in my opinion is much more usable than what others can propose (e.g. https://vocabulary.uncefact.org/classes from UNCEFACT).

I am not against maintaining a classical data model view but till today I'm still struggling to find a proper, collaborative, simple as possible tool.

With regards to @NiclasScheiber comment above, let's assess what can be created as documentation indeed.

@gxclark
Copy link
Author

gxclark commented May 7, 2024

Hello @lambertciata @NiclasScheiber ,
Thanks for your ideas and consideration on this. I've refreshed my searches for a good way to bridge the gap between the relational database world and the semantic web / RDF triple-store / graph world.
I'm looking now at: https://github.com/jimjonesbr/rdf_fdw
I'll attempt a prototype with the .TTL file that is published here over the next few weeks, and report back here.

@lambertciata
Copy link
Collaborator

Hello!

We are also making progress on our side. We had first identified dbdiagram (https://dbdiagram.io/) and we are focusing on:

  1. Working on translating the TTL into DBML (https://dbml.dbdiagram.io/home)
  2. Using https://github.com/sqlhabit/sql_schema_visualizer as a basis to then display DBML in a way that suits our needs

We will share a MVP in the next couple of weeks to get feedback.

@lambertciata
Copy link
Collaborator

Hi,

As promised, the visualizer we've been working on is accessible here: https://aloccid-iata.github.io/ontology_visualizer/

It is an unofficial version that is not yet on IATA's repository and we are open to any feedback to make it better.

There are 2 views:
o ONE Record Full Datamodel that is the equivalent view of the previous pdf version. We intentionally limit what is displayed to keep it usable
o ONE Record Conceptual Datamodel that is a simpler view with main objects.

@gxclark
Copy link
Author

gxclark commented Jun 19, 2024

This is fantastic, thanks @lambertciata ! I've had no chance to experiment with RDF.
Appreciate your effort to make this more accessible.

@gxclark gxclark closed this as completed Jun 19, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in Data Model Changes Jun 19, 2024
@gxclark
Copy link
Author

gxclark commented Jun 19, 2024

This enables a way to visualize the data model as tables, columns and keys ... it is not quite as useful as a standard relational data model (for example, no definitions), but it is better than the older PDF.

@lambertciata
Copy link
Collaborator

Well, we do have the definitions, we added a feature when you hold shift key and go over a property the description is shown :)

@lambertciata lambertciata linked a pull request Nov 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants