- RDS/WIP Introduction
- RDS/WIP Sample Queries
- RDS/WIP Staging Diagrams
- RDS/WIP 1.0 Plan
- RDS/WIP 1.0 Testing
- RDS/WIP 1.0 Process
- RDS/WIP 1.0 Inventory
- RDS/WIP 2.0 Plan
- RDS/WIP ID Generator
- RDS/WIP Domain Proposal
- RDS/WIP Requirements Table
- RDS/WIP Use Case: Discrete Editing
- RDS/WIP Use Case: CSV Upload
- RDS/WIP 1.0 General Use Cases
- RDS/WIP 2.0 General Use Cases
- RDS/WIP ISO 15926 Template Definitions
- RDS/WIP OWL/RDF Definition
- RDS/WIP OWL/RDF Project Plan
- RDS/WIP Forums
- RDS/WIP Use Case: Bulk Upload
RDS/WIP Use Case: CSV Upload
This page notes the case for upload of definitions specified in comma-separated variable (CSV) format to the RDS/WIP.
The use case for CSV upload of definitions into the RDS/WIP stems largely from these fundamental drivers:
- the discomfort of engineers with technology such as OWL/RDF and its related tools
- the familiarity of engineers with tabular formats and tools such as spreadsheets
- the existing definition of dictionary style materials in this or a similar format
- the mandated use of such formats by other bodies such as SC4.
Use Case for RDS/WIP 1.0
In the next RDS/WIP release (1.0), the easiest way to conceive of this working is that contributors pass SC4 specified definitions to DNV's IRM team, along with some guidance about the intended endpoint and function.
At this point, the IRM team will need to make an internal decision about the material: if it is intended to be included in the RDS/WIP per se, then it might be best to enter it via the Brutus system, for eventual automatic upload into the RDS/WIP via the usual means specified for that process. Since submission is via Brutus under existing contractual arrangements between DNV and POSC Caesar (I think - Julian), and the IDS-ADI RDS/WIP service itself is ultimately intended to be a free one for contributors, then so long as the input is SC4 compliant, it would be best if the submitter is not charged (this should be OK because it should all be an automatic process anyway).
On the other hand, if it is intended to be its own endpoint (for example, its not intended to be ISO 15926 compliant), then it will need to be transformed into RDF in some way and then uploaded directly into the RDS/WIP. How this is achieved, where the costs will be borne etc. are all internal matters for IRM, possibly up for negotiation with the submitter.
Similarly, if the definitions are intended for ISO 15926, but are not in the SC4 form, then it would be reasonable for the work required to analyse and recast the data in compliant terms to be negotiated and charged for.
Use Case for RDS/WIP 2.0
In the following RDS/WIP release (2.0) the means will exist for users to directly interoperate with the RDS/WIP server to perform bulk uploads of OWL/RDF definitions. The problem will be, what if they cannot or do not want to use OWL/RDF?
So long as the SC4 format is sufficiently rich, it should be possible to create an SC4 CSV to OWL/RDF format converter that could be used as a standalone conversion tool. This sort of tool will be useful for people wanting to learn about ISO 15926 representation in OWL/RDF.
Longer term, it would be theoretically possible to integrate such functionality into the submittal framework - allowing submissions to be made in OWL/RDF or SC4 CSV.
Ad-hoc CSV will never be supported directly, however, its possible that 3rd parties with the necessary skillsets (such as DNV's IRM section) could charge to transform CSV data into compliant SC4 CSV, raw RDF or ISO 15926 OWL/RDF formats.