RDS/WIP Use Case: Discrete Editing

A description of the use that backs up the requirement for discrete editing - distilled from a phone conversation between Julian Bourne (NRX) and Robin Benjamins (Bechtel) 2008-06-10.

Overview

Discrete editing is a term we use in contrast to bulk editing. It means being able to edit the RDS/WIP interactively on the actual RDS/WIP server.

The need for this is seen to stem from EPCs who wish to have a one-stop-shop for editing into the RDS/WIP built around thin-client principles with a high degree of accessibility.

Background

Current Bechtel practice is to maintain an internal class library consisting of some 50 classes and 2000 properties. They would prefer that the class library is discarded and rebuilt from scratch in ISO 15926, since it is currently fairly flat in structure.

For that reason, they see no requirement for bulk upload as they are not anticipating loading their existing classes into the RDS/WIP in either raw RDF, shortcut template or ISO 15926 forms.

Moreover, they feel that designing directly in ISO 15926 will be appropriate and beneficial in that they have the domain expertise to create those classes directly in ISO 15926 without the need for an interim description or harmonization done collaboratively in public.

Process

The editing process should be close to that provided by the existing SQL Server/.NET implementation.

Implementation Limitations

From an implementation point of view, submission would still be via the bulk upload processes. The reason for this is so that the administrative @todo

Other Considerations

Bechtel's investment in the SQL Server/.NET Tarcus implementation for RDS/WIP 1.0 provided @todo