...
Ed Seidewitz, MDS - ed-s@modeldriven.com
Jason, Doris, Blake
Considerations
The purpose of the server is to store and retrieve SysML models based on the abstract syntax as defined in the SysML Spec.
The primary & initial interface to RDF repositories will utilize the open-api specification. As the project progresses, the following capabilities can be implemented in stages:
Generic “stubbed out” API server implementation
Push and retrieve full SysML-RDF models without regard to versioning – this can use generic RDF SparQL
Respect API versioning mapped to Flexo capabilities, which are still in pre-release.
Support the API capability for derived relationships
Support Diff/Merge
The current OSLC specification is not considered sufficient and has been replaced by the OASIS-OSLC team. Flexo may want to implement the OSLC interface, that will be looked at after the full API implementation.
We will use the same URIs between the UML/Flexo , OSLC, & API representations. There are technical and “political” considerations.
OSLC requires URIs that are not version-specific, this would also be preferable for Flexo. The OMG spec may also have version-specific URIs.
OSLC requires that the URIs be “dereferenceable”, thus if they are OMG URIs, OMG would have to host, at a minimum, the RDFS representation compatible with OSLC. Oasis typically hosts OSLC specifications with a Oasis namespace but has agreed to use the OMG namespace.
Besides open API and OSLC, an additional interface is possible via XMI.
Once we have the API and repository we can start work on UI and document generation.
There are issues with respect to retaining the order of lists in RDF, which are discussed below.
...