Submissions:ReportingNewsEvent

From Odp

(Difference between revisions)
Jump to: navigation, search
(Imported from OWL file.)
Line 2: Line 2:
{{Graphical representation header}}
{{Graphical representation header}}
{{Graphical representation
{{Graphical representation
-
|ImageName=
+
|ImageName=ReportingNewsEvent-scheme.png‎
}}
}}
{{Content OP Proposal Template
{{Content OP Proposal Template
|SubmittedBy=EwaKowalczuk
|SubmittedBy=EwaKowalczuk
-
|ReusableOWLBuildingBlock=http://www.cs.put.poznan.pl/ekowalczuk/ont/reportingnewsevent.owl
 
|Name=ReportingNewsEvent
|Name=ReportingNewsEvent
 +
|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.
 +
|ContentODPDescription=TODO
 +
|ReusableOWLBuildingBlock=http://www.cs.put.poznan.pl/ekowalczuk/ont/reportingnewsevent.owl
 +
|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).
 +
|Scenario=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.
 +
|HasComponent=IntensionExtension, ActingFor
 +
|SpecializationOf=ReportingEvent
 +
|RelatedCP=ReportingEvent, IntensionExtension, ActingFor, Situation
}}
}}
{{Element list header}}
{{Element list header}}
Line 43: Line 57:
|HasElement=scenarios
|HasElement=scenarios
}}
}}
-
 
{{Additional information header}}
{{Additional information header}}
{{Scenarios about me}}
{{Scenarios about me}}
-
{{Reviews about me}}{{Modeling issues about me}}{{My references}}
+
{{Reviews about me}}
 +
{{Modeling issues about me}}
 +
{{My references}}

Revision as of 09:35, 16 July 2016


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 12697

Graphical representation

Diagram

Image:ReportingNewsEvent-scheme.png‎

General description

Name: ReportingNewsEvent
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: TODO
Reusable OWL Building Block: http://www.cs.put.poznan.pl/ekowalczuk/ont/reportingnewsevent.owl (26)
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:

coversRequirements (owl:AnnotationProperty) This annotation property is used for exemplifying possible requirements the content pattern provides a solution for. Requirements are expressed as natural language competency questions.
coversRequirements page
extractedFrom (owl:AnnotationProperty) This annotation property should be assigned with a URI, which points to the possible reference ontology which the annotated pattern was extracted from (i.e. the reference ontology that the ontology elements have been deeply or partially cloned by). The range is not explicit in the definition of the annotation property because it would turn the ontology to OWL Full. E.g. The participation pattern is extracted from the Dolce Ultra Lite ontology, hence the value for this annotation property is http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
extractedFrom page
hasComponent (owl:AnnotationProperty) This annotation property is useful for content ontology design patterns. Its value is a URI, which refers to another content ontology design pattern which is a component of the annotated one.
hasComponent page
hasConsequences (owl:AnnotationProperty) This annotation property is used for briefly describing the benefits and/or possible trade-offs when using the CP.
hasConsequences page
hasIntent (owl:AnnotationProperty) This annotation property is used in order to describe the intent of the content pattern.
hasIntent page
hasUnitTest (owl:AnnotationProperty) This property can be used to annotate a unit test (e.g. in the form of a SPARQL query) to be launched to evaluate an ontology against a requirement-based task.
hasUnitTest page
isCloneOf (owl:AnnotationProperty) This annotation property is used for referring a cloned ontology entity to its cloning source.
isCloneOf page
isSpecializationOf (owl:AnnotationProperty) This annotation property is useful for content ontology design patterns and its elements. Its value is a URI, which refers either to a content ontology design pattern that is specialized by the annotated one, or to an ontology element that is specialized by the annotated one.
isSpecializationOf page
reengineeredFrom (owl:AnnotationProperty) This annotation property should be assigned with a URI, which points to the concept schema, page, or anything else from which the annotated pattern was reengineered. If the source does not have any URI e.g., a printed book, this property value should provide information as precise as possible in order to identify the source. This property is alternative to the extractedFrom property because it is used when the pattern come from a concept schema which is not an owl ontology. For example content ontology design patterns, which are reengineered from data model patterns, rdf schemas, etc. should be annotatd with this property. E.g. The basicpersonalfoaf pattern is extracted from the rdf FOAF specification, hence the value for this annotation property is http://xmlns.com/foaf/spec/20071002.rdf
reengineeredFrom page
relatedCPs (owl:AnnotationProperty) This annotation property can be used to indicate other CPs (if any) that specialize, generalize, inlcude, or are components of the CP. Furthermore, this field may indicate other CPs that are typically used in conjunction with the described one. Important similarities and differences with other patterns can be also described here.
relatedCPs page
scenarios (owl:AnnotationProperty) This annotation property is used for describing examples of instantiation of the Content OP. For example, for the part-of Content OP (which represents part-whole relations) a possible scenario is the sentence: "the brain is part of the human body". Scenarios are expressed as natural language sentences.
scenarios page

Additional information

Scenarios

Scenarios about ReportingNewsEvent

No scenario is added to this Content OP.

Reviews

Reviews about ReportingNewsEvent

There is no review about this proposal. This revision (revision ID 12697) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about ReportingNewsEvent

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers