OCL25 — OCL 2.1 conformsTo definition suggestion

OCL allows a user to define a run-time OCL meta-model through Property and Operation definitions that is based upon a specification-time UML meta-model.

It would be useful to allow a user to also introduce inheritance/conformance polymorphisms.

Thus:

context CommonPackage::CommonObject

context CommonPackage::CommonObject::isSerializable() : Boolean = false

context OCL::String conformsTo CommonPackage::CommonObject

context MyPackage::MyObject conformsTo CommonPackage::CommonObject

context YourPackage::YourObject conformsTo CommonPackage::CommonObject

could mix-in the capabilities of CommonObject to each of MyObject and YourObject and String.

This would allow common functionality to be mixed in once and used polymorphically rather than being added in amorphously and requiring an if-tree of per-context invocations of that functionality.