Reportingnewsevent Pattern¶

Source: ODP portal · Published by: semantic.cs.put.poznan.pl · Category: structural · Domain: media

This is the same pattern as newsreportingevent

The library lists it under both names. Importing both would import the same terms twice.

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.

What it answers¶

In addition to the competency questions defined for pattern ReportingEvent (http:/ontologydesignpatterns.org/wiki/Submissions:ReportingEvent) the pattern allows to answer the following questions: - What aspects of an actual event were presented in the news message? - Who reported an actual event? Which news provider they represented? - When was a certain actual event reported for the first time? - What actual events are presented in a certain medium/by media of a certain news provider? - How was an actual event presented?

The pattern¶

The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.

Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.

Download the pattern

Should you use this one?¶


Size	10 classes, 5 properties, 41 axioms
Brings in	3 imported ontologies, so adopting it adopts those too
Reasoning	HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.
Duplicate of	`newsreportingevent` - pick one of the two, not both

A situation it was written for. 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.

Check it yourself: the published pattern · an archived copy · the ontology itself.

If a link does not open

ontologydesignpatterns.org, which publishes most of this library, does not currently answer over HTTPS, and its wiki redirects submission pages to its front page. The archived copy is there for exactly that reason. The ontology files themselves are still served over plain HTTP.

Terms it declares¶

The 31 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.

http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#Media
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#NewsEventReporter
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#NewsPresentationContext
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#NewsProvider
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#NewsReportingEvent
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#PresentationContext
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#hasPresentationContext
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#owns
http://semantic.cs.put.poznan.pl/ontologies/newsreportingevent.owl#presentedAt
http://semantic.cs.put.poznan.pl/ontologies/reportingevent.owl#EventReporter
http://semantic.cs.put.poznan.pl/ontologies/reportingevent.owl#ReportingEvent
http://semantic.cs.put.poznan.pl/ontologies/reportingevent.owl#hasAuthor
http://semantic.cs.put.poznan.pl/ontologies/reportingevent.owl#reports
http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl#Agent
http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl#SocialAgent
http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl#actsFor
http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl#actsThrough
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#Situation
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#hasSetting
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#isSettingFor
http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl#TimeIndexedSituation
http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl#atTime
http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl#forEntity
http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl#hasTimeIndexedSetting
http://www.ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl#isTimeIndexFor
http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#TimeInterval
http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#hasIntervalDate
http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#hasIntervalEndDate
http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#hasIntervalStartDate
http://www.ontologydesignpatterns.org/cp/owl/typesofentities.owl#Entity
http://www.ontologydesignpatterns.org/cp/owl/typesofentities.owl#Object

An example of it in use¶

The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.

Download the example

Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.

Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.