I'm trying to get my arms around an ontology management workflow. I've been reading the docs on the Apache Jena site and a couple of books. I was hoping to test my understanding of the technology by sharing my current plan and gathering some feedback.
Thanks in advance if you have the time to comment! I intend to tightly manage a pretty broad ontology. Let's say it includes assets, locations, people and workflows. I think I want to have a single "schema" file that describes the asset class hierarchy and the rules for validating assets based on properties, disjointness etc. Then I might have a bunch of other "data" files that enumerate all the assets using that first "schema" file. I'd repeat this structure using a schema file each for locations, people, workflows. Having created these files, I think I can use an assembler file to pull them into a single model. Ultimately, I expect to query the data using Fuseki and this is where I get a little hazy. I think the assembler can pull the files into a single memory model, then I can write it to a tdb. Is that necessary, though? it's a simple bit of java, but I have the nagging feeling that there's a shorter path to automatically load/validate those files for Fuseki Is this approach to organizing the files sound?
