As I understood there is no well established tool, technique and method  to specify common concepts and business riles for further (or on top of) RDBMS persistence (currently specified by ORM and a "plethora-of"), content (XML) and object (by UML) modeling.

That was my illusion from coming to ORM. That it was object and role and modeling .

ORM (Object Role Modeling) and all introductory texts use misnomers like "object", "concept", "conceptual modeling", "modeling", "model", "reference", "scheme", "identification".

The terms are even not defined. All texts on ORM just illustrate their use.

That is, it is necessary to cross-read hundreds of pages, just to understand that it is impossible to specify in ORM neither concepts nor business rules or roles since they are inseparably fused with decision-after (I'd say impementation&deployment-after) persistence-only and only through RDBMS necessities and terms.

Since there are quiet a plethora of methods, techniques, notations and tools for storage/persistence relational  modeling(I'd say specification), there would be very nice to separate all the terms in ORM clearly for conceptual modeling only and (or, at least) do not mix them with any other/further necessities,