Submissions:ReportingNewsEvent
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 12893 |
Graphical representation
Diagram
General description
| Name: | NewsReportingEvent |
|---|---|
| Submitted by: | EwaKowalczuk |
| Also Known As: | |
| Intent: | The pattern can be used for modelling situations in which we are not certain that a particular actual event has the properties which were described in a news message. We want to define the properties of an actual event which were reported (time, place, actors, subevents, cause, effect etc.), but not to treat them as universal, verified knowledge. The pattern also allows to define who is responsible for a particular description of an event and how this description is dealt with. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | The pattern extends the ReportingEvent pattern by specifying the primary properties of the specialisation of the ReportingEvent class. The specialisation, NewsEventReportingEvent, denotes the act of providing a unit of information (ReportedNewsEvent) to the general public.
The act utilises a certain Media (TV station, radio station, newspaper, website). A Media is owned by a certain SocialAgent - NewsProvider. This agent takes partial responsibility for the content provided, but its responsibility differs from the one of the NewsEventReporter -- an Agent that directly reports the ActualEvent. Other properties which are very important for NewsEventReportingEvent are time at which the event is reported and the context of presentation. |
| Reusable OWL Building Block: | http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl (1257) |
| Consequences: | The pattern is rather complex and should only be used if the circumstances of the events presented in a media
are expected to be uncertain (to differ in different news event reports of different news providers). |
| Scenarios: | A single actual event, bus drivers protest, is presented in to different media: a TV news station and a news website. John Doe prepared the material for the station Channel 55, owned by Media Corp. This material was presented as first material in a news programme on 16/07/2016, started at 19:30 and ended at 19:35. It was based on correspondent report. The material said that the cause of the protest was malfunction of buses, and that a brutal police intervention took place. The article from website livingintheworld.com also mentioned malfunction of buses, but it also mentioned other cause of protest: planned reduction of social benefits. It did not mention brutal police intervention, but it did mention destruction of public property. The article seems not important for the website authors, it was presented at the page bottom. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The ReportingNewsEvent Content OP locally defines the following ontology elements:
Additional information
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 12893) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
