This first figure is an example of a diagram from the perspective of an OSLC Change Management Change Request definition.
I'll go into a bit more detail about this model a bit later.
In an attempt to simply view these resource models, I started with some work that Scott Rich had done, along with some approaches I had experimented with using Rational Software Architect (RSA)
To keep things very simple, I'll highlight some guidelines on how to develop this model in a UML modeling tool:
To keep things very simple, I'll highlight some guidelines on how to develop this model in a UML modeling tool:
- This is just a picture (for now), semantics are not clearly defined and they are not those of OO design.
- All properties are modeled as an 'Attribute', they are just visualized in the diagram as an association (since property values/objects in RDF are nothing special).
- Each domain, which has its own vocabulary document, is a separate package. Also give each domain/package its own color
- No special profile is used (I attempted to use OWL profile from OMG).
- Even though there isn't an example restriction on the resource types (range) of properties, an explicit expected Class is still set. A diagram with everything pointing to rdf:Resource wouldn't be too interesting. Note to self: create a stereotype/visualization to make this obvious.
Ideally (and I know my modeling geek friends are going to like this) we can transform to/from some other descriptive form (OSLC Resource Shapes + RDFSchema).
The current model has been shared in the Eclipse Lyo project and additional examples are highlighted over on the OSLC Core wiki page. I tucked the RSA model file into an Eclipse project titled org.eclipse.lyo.model which you can find in expected git location. For those that use some tool other than RSA, I have also provided the .uml file. I'd be interested to hear if anyone has another tool (and/or approach) to modeling these. I'll try to advance in my spare time, including improving the diagrams.