Create OWL metamodel

[darkobozhinoski]

• Create OWL metamodel that can be used to represent the runtime model of the system architecture that can be used by the metacontroller. The OWL metamodel should capture the “Systems Modes and Hierarchy” developed in metacontrol_ontology issue

[chcorbato]

@darkobozhinoski are you referring to creating the OWL T-box for MROS?
I agree you need it for the tooling, but I think it is being developed in another repo.
I have created the issue in the https://github.com/MROS-RobMoSys-ITP/metacontrol_ontology repo and linked it in the description above.

[rsanz]

In principle, this was the purpose ot the T-Box of MO. But I think that MO as it is now, is too broad and somewhat disconnected from RobMoSys and the ECore metamodel that Darko proposed.

What I'm doing is to rethink/realign it under the light of the current discussions on the Pilot and the scenarios. This will lead to MO TBox v2 and a Pilot ABox (and maybe a NOv2).

I still don't understand how the RobMoSys tooling (SmartMDSD) and workflow fits our picture.

Are we going to develop ISE&PPOOA models of the Pilot ?

[chcorbato]

I still don't understand how the RobMoSys tooling (SmartMDSD) and workflow fits our picture.

Are we going to develop ISE&PPOOA models of the Pilot ?

@darkobozhinoski I think we need to work on the Engineering Scenarios for MROS, to

• refine the left side of the overview figure
• motivate the metamodel and the Eclipse tooling

Wee need to define:

• What information needs to be captured in the models that are the outcome of those scenarios -> metamodel
• How it is captured: Xtext&Ecore implementation of the metamodel