Scope: The various ome:Event subcategories represent the types of events that were considered likely candidates for use.
The omea:Sex and ontomedia:Violence related classes were included both for their commonality and because these types of events were highlighted as being important to users as metrics which they could use to inform their choice of whether or not to consume the item of media in question
The class omes:First-Meeting, as with ome:Introduction, is for use in the case of purely descriptive narrative during which nothing happens other than the image being painted for the audience. This is distinct from a ome:Social event where there character interaction actually occurs and thus does not subclass ome:Social in addition to ome:Introduction.
Once described, no ontomedia:Entity ceases to exist on the metadata level (although the described ome:Entity may be non-existent). Equally, the information about the ontomedia:Entity may exist before the ontomedia:Entity does within the narrative sequence. The omeg:Creation and omel:Destruction events, which subclass ome:Gain and ome:Loss respectively, delimit the existence of an entity from an in-universe perspective.
The ome:Transformation subclasses represent the exchange of an ome:Entity between two others (omet:Transference), the separation of an ome:Entity into component parts (either in a single ome:Event, omet:Division, or over an extended period of time, omet:Degradation) and the combining of ome:Entitys into a single whole (omet:Merge). The distinction between ome:Gain/ome:Loss events and ome:Merge/ome:Division is whether the resulting ome:Entity, in the case of ome:Gain/ome:Merge, or the initial ome:Entity, in the case of ome:Loss/omet:Division, can be regarded as a single unit or multiple units, one of which may contain the others. In all of these cases and ome:Entitys contained by the ome:Entitys being transferred go with their parent ome:Entity
The transfer of an ome:Abstract-Item is the exception to the general transformation rule than while things may change there is no overall gain or loss within the transformation event. The transfer of a physical object typically contains a loss event for the giver and a gain event for the receiver. However, when an ome:Abstract-Item, most commonly some form of information, omk:Knowledge or omt:Motivation, is transferred it is not removed from the giver while it is still gained by the receiver. This arguably represents an overall gain within the event however it was decided that the metaphorics of the case were less important than consistency and therefore this case if treated like any other transfer.
The other case which sometimes presents an apparent inconsistency is omet:Degradation, especially in cases of decomposition or erosion. However, in the case a degrading ome:Entity there are one of more ome:Entitys being created and separating from it but these are typically of a level and importance that makes modelling them an exercise in completeness rather than practicality. For general use, the subject of a ontomedia:Degradation event is seen to be the ome:Entity undergoing the transformation. Only if the resultant ome:Entitys produced are of signiﬁcant size or interest will they be listed within the ome:to property along with the originating ome:Entity which will also provide the ome:from
The event properties exist to allow us to differentiate between forced actions and those done of a ome:Entity’s freewill. This is most important when modelling the actions of omb:Beings and related subclasses.
The consent being modelled is that of the subject of the event. It was decided that for any given ome:Event instance the question of consent should only be speciﬁed for the ome:Entity that is acting as the focus. This decision was made due to the fact that the level of consent given for an event may not be the same from the perspective of each of those involved. In cases such as this, multiple instances describing the event from the perspective of the various ome:Entitys involved can be created with the respective consent levels for each subject ome:Entity speciﬁed. An ome:is statement can then be used to clarify the fact that the different instances all refer to the same event.