This code sample illustrates a sample aggregater application for an requisition engineer using ISO 15926 Part 9.
Workflow :
Requisition engineer gets a PID and wants to identify matching equipments from suppliers catalog.
PID designer exposes the pid at part 9 endpoint.
Equipment supplier exposes his catalog at part 9 endpoint.
Requisition engineer queries PID endpoint to get details about items on the PID.
Based on the results he fires queries on equipment manufacturer's endpoint and gets matching equipment models.
To run the application :
Pre. reqs. : Check out and build the code in VS 2010. I have not tried with other versions but it should work.
There is no installer yet so checking out and building and running the code is only way. Installer work is in progress. Visual Studio is not needed to look at ISO 15926 sample files in data folder of code.
To work with the sample data (pid and supplier owl files) you will need to expose it at a sparql endpoint. Using Joseki is the easiest option.
Steps :
1. Start two ISO 15926 endpoints pid and supplier using files from data folder.
2. Start the application. It will open Requisition Engineer UI.
a. Put the path of pid endpoint. "http://localhost:2020/pid" (varies as per your setting).
b. Click "Get Manifest" button. It will fire sparql to investigate the manifest of pid endpoint and display the RDL class names for the classes whose instances are exposed at given (PID) endpoint.
c. Select the desired item and click "Get Items". This will fire a query to get instances of selected RDL class. Result instance ids are displayed in the next grid.
d. Select the desired item and click "Get Details". This will fire a query to get the template instances associated with the item which have property values associated with given item.
e. Select desired properties which should be used as criteria for model selection.
f. Click "Get Models". This will fire a query on equipment suppliers endpoint to get matching models based on the property ranges for the selected properties.
Demo covers :
1. Modeling of pid using ISO 15926 part 8.
2. Modeling of equipment catalog using ISO 15926 part 8.
3. Examples of Part 9 manifest in owl files.
4. Example queries to get manifest, payload as well as class information from an endpoint.