Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Test turtle file from Information Model in graphdb #138

Open
tloubrieu-jpl opened this issue Mar 5, 2021 · 4 comments
Open

Test turtle file from Information Model in graphdb #138

tloubrieu-jpl opened this issue Mar 5, 2021 · 4 comments

Comments

@tloubrieu-jpl
Copy link
Contributor

tloubrieu-jpl commented Mar 5, 2021

Steve created a turtle file from the information model.

We need to ingest it in a graph database and understand how it makes sense to have it stored this way and give him feedback on that.

pds4_ontology_classes_properties_instances.ttl.zip

Feedback:

  • TTL file is ANSI / ASCII encoded. To load it into Apache Jena I had to convert the file into UTF-8.
  • The file has a subset of ontology (instrument types, some properties)
  • The file has a subset of PDS context products: instruments only.

Questions / Issues

  • Why instruments don't have references to instrument hosts, even though instrument_to_instrument_host property is defined.
  • Why pds4:urn:nasa:pds:context:type_list_area::1.0 extends pds4:urn:nasa:pds:context::1.0 similar to Instrument, Target, etc. How it is used?
  • There are 2 branches of dust detectors: (1) instrument → dust → leam.a17a; cda.co; hrd.co. (2) (unused?) instrument → dust_detector → [no instruments]
@tloubrieu-jpl
Copy link
Contributor Author

The turtle file handles inheritance and jena need to be reconfigured to handle that.

@tloubrieu-jpl
Copy link
Contributor Author

@tloubrieu-jpl need to transfer to steve

@jordanpadams
Copy link
Contributor

@tloubrieu-jpl what needs to happen with this ticket?

@tloubrieu-jpl
Copy link
Contributor Author

We can keep it in the ice box until we have a student who can work on it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants