Difference between revisions of "Submissions:Literal Reification"

 
(14 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
{{Graphical representation header}}
 
{{Graphical representation header}}
 
{{Graphical representation
 
{{Graphical representation
−
|ImageName=Literalreification.png
+
|ImageName=Literalreification_new.png
 
}}
 
}}
 
{{Content OP Proposal Template
 
{{Content OP Proposal Template
−
|SubmittedBy=SilvioPeroni
+
|SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali
 
|Name=Literal Reification
 
|Name=Literal Reification
−
|Intent=The goal of this pattern is to allow the reification of literal values within OWL.
+
|Intent=This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal.
 
|Domain=General
 
|Domain=General
−
|CompetencyQuestion=What is the context in which entities refer to a particular literal value? , What are the meanings of a particular value considering the context in which it is used?
+
|CompetencyQuestion=What is the context in which entities refer to a particular literal value? ,
−
|ContentODPDescription=Literals are reified in proper ontological individual, expressing the literal value they refer to through a data property. This reification allows to use each 'reified literal' as subject or object of assertions.
+
What is the meaning of a particular value considering the context in which it is used?
 +
|ContentODPDescription=Literals are reified in proper ontological individual (belonging to the class 'Literal'), expressing the literal value they refer to through a data property. This reification allows to use each 'reified literal' as subject or object of assertions.
 
|ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification
 
|ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification
−
|Scenario=From a Web 2.0 point of view, a tag is a non-hierarchical keyword (e.g., a string) assigned to a piece of information, such as a web document. A particular tag can have more than one meaning according to the context in which it is specified. Let us consider the following two article from Wikipedia: 1) http://en.wikipedia.org/wiki/Ulysses_%28novel%29 2) http://en.wikipedia.org/wiki/Paris_Hilton  The tag 'Paris' can be added to both articles, of course, but it brings with itself two different meanings, even though it is exactly the same string that has been used. In the above example, we want to say that 'Paris' is a first name of the person document 2) is about (i.e., Paris Hilton), while in document 1) 'Paris' is the name of the city in which the subject of the document (the novel 'Ulysses' by James Joyce) was published the very first time.  Using the reified literal pattern, we can express tags as proper individuals of the class 'Literal' (or of a specific subclass of it, such as 'Tag'), connecting them when refer to the same literal value. Writing the previous example down in a Turtle format, we could have:  <http://en.wikipedia.org/wiki/Ulysses_%28novel%29> a foaf:Document ; prism:keyword :parisTag1 . <http://en.wikipedia.org/wiki/Paris_Hilton> a foaf:Document ; prism:keyword :parisTag2 . :parisTag1 a litre:Literal ; litre:hasLiteralValue "Paris" ; a [ a skos:Concept ; skos:definition "the name associated to a particular city"@en ] . :parisTag2 a litre:Literal ; litre:hasSameLiteralValueAs :parisTag1 ; a [ a skos:Concept ; skos:definition "the first name of a person"@en ] .
+
|Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.
 +
|Scenario=Modelling domains concerning descriptive tags, in which each tag may have more than one meaning depending on the context in which it is used. Extending quickly the capabilities of a model by adding the possibility to make assertions on values, previously referred through data properties, without modifying it.
 
|SpecializationOf=Region
 
|SpecializationOf=Region
 
|RelatedCP=Region
 
|RelatedCP=Region
 
}}
 
}}
 
{{Element list header}}
 
{{Element list header}}
 +
{{Has Element Template
 +
|HasElement=Literal
 +
}}
 +
{{Has Element Template
 +
|HasElement=hasSameLiteralValueAs
 +
}}
 +
{{Has Element Template
 +
|HasElement=hasLiteral
 +
}}
 +
{{Has Element Template
 +
|HasElement=isLiteralOf
 +
}}
 +
{{Has Element Template
 +
|HasElement=hasLiteralValue
 +
}}
 
{{Additional information header}}
 
{{Additional information header}}
−
From a Web 2.0 point of view, a tag is a non-hierarchical keyword (e.g., a string) assigned to a piece of information, such as a web document. A particular tag can have more than one meaning according to the context in which it is specified. Let us consider the following two article from Wikipedia:
 
−
 
−
# <nowiki>http://en.wikipedia.org/wiki/Ulysses_%28novel%29</nowiki>
 
−
# <nowiki>http://en.wikipedia.org/wiki/Paris_Hilton</nowiki>
 
−
 
−
The tag 'Paris' can be added to both articles, of course, but it brings with itself two different meanings, even though it is exactly the same string that has been used. In the above example, we want to say that 'Paris' is a first name of the person document 2) is about (i.e., Paris Hilton), while in document 1) 'Paris' is the name of the city in which the subject of the document (the novel 'Ulysses' by James Joyce) was published the very first time.
 
−
 
−
Using the reified literal pattern, we can express tags as proper individuals of the class 'Literal' (or of a specific subclass of it, such as 'Tag'), connecting them when refer to the same literal value. Writing the previous example down in a Turtle format, we could have:
 
  
−
<pre>
 
−
<http://en.wikipedia.org/wiki/Ulysses_%28novel%29> a foaf:Document
 
−
; prism:keyword :parisTag1 .
 
−
 
−
<http://en.wikipedia.org/wiki/Paris_Hilton> a foaf:Document
 
−
; prism:keyword :parisTag2 .
 
−
 
−
:parisTag1 a litre:Literal
 
−
; litre:hasLiteralValue "Paris"
 
−
; a [ a skos:Concept
 
−
; skos:definition "the name associated to a particular city"@en ] .
 
−
 
−
:parisTag2 a litre:Literal
 
−
; litre:hasSameLiteralValueAs :parisTag1
 
−
; a [ a skos:Concept
 
−
; skos:definition "the first name of a person"@en ] .
 
−
</pre>
 
 
{{Scenarios about me}}
 
{{Scenarios about me}}
 
{{Reviews about me}}
 
{{Reviews about me}}
 
{{Modeling issues about me}}
 
{{Modeling issues about me}}
 
{{My references}}
 
{{My references}}
 +
{{Submission to event
 +
|Event=WOP:2010
 +
}}[[Category:Review assigned]]

Latest revision as of 14:38, 30 September 2010

Warning.gif

Warning!

This is an old revision. Go to current revision

Certified.png
This pattern has been certified.

Related submission, with evaluation history, can be found here

Working.gif Last modified date is: 2010-09-30

Graphical representation

Diagram

Literalreification new.png

General description

Name: Literal Reification
Submitted by: AldoGangemi, SilvioPeroni, FabioVitali
Also Known As:
Intent: This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal.
Domains:

General

Competency Questions:
Solution description: Literals are reified in proper ontological individual (belonging to the class 'Literal'), expressing the literal value they refer to through a data property. This reification allows to use each 'reified literal' as subject or object of assertions.
Reusable OWL Building Block: 1 (625)
Consequences: This pattern allows to specify different contexts and/or meanings to a particular literal value.
Scenarios: Modelling domains concerning descriptive tags, in which each tag may have more than one meaning depending on the context in which it is used. Extending quickly the capabilities of a model by adding the possibility to make assertions on values, previously referred through data properties, without modifying it.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:



Elements

The Literal Reification Content OP locally defines the following ontology elements:

ArrowRight.gif Literal page
ArrowRight.gif hasSameLiteralValueAs page
ArrowRight.gif hasLiteral page
ArrowRight.gif isLiteralOf page
ArrowRight.gif hasLiteralValue page

Additional information

Scenarios

Scenarios about Literal Reification

No scenario is added to this Content OP.

Reviews

Reviews about Literal Reification
There is no review about this proposal.
Some subquery has no valid condition.

This revision (revision ID 10190) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Literal Reification
There is no Modeling issue related to this proposal.
Some subquery has no valid condition.


References

Add a reference


Timer.png Submission to event

WOP:2010

Retrieved from "http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&oldid=10190"
The page [[Bootstrap:Footer]] was not found.