-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start a MOF2RDF-aware variant of the driver #15
Comments
Having some initial slides to kick-off the discussion and agree on a strategy would be useful, according to Gian. |
Dimitris and I had a brief chat about this. The idea would be to create a |
We could try going for this structure, so that the MOF2RDFModel is kept as simple as possible (turning all We'd need to create a new |
To support different flavours of RDFModels like MOF2RDF, specific pairs of Model and Resource type extensions will be used. Property "gets" happen through the RDFResource class, before invoking the more general propertyGetter. Therefore, the type and creation of Resources need to be adapted to enable different getProperty results processing. Change how RDFModel creates RDFResources
Create MOF2RDF extensions for (RDF) Model and Resource
Change getProperty() on RDFResourcel and MOF2RDFResource
Create EclipseMOF2RDFModel extension
UI updates
|
The OMG has published a specification providing a standardised mapping from MOF metamodels and models to RDF (including use RDFS and OWL), with some conventions on how to map some MOF-specific features, such as the relative order of the elements of an
OrderedSequence
:https://www.omg.org/spec/MOF2RDF/1.0/PDF
We could investigate creating a subclass of the current
RDFModel
with specialised property getters that are aware of the MOF2RDF transformation (could be called something likeMOFAwareRDFModel
?), e.g. sorting the resources linked through a property using thelinkSequence
annotation.The text was updated successfully, but these errors were encountered: