SilvioPeroni (Talk | contribs) |
SilvioPeroni (Talk | contribs) |
||
Line 7: | Line 7: | ||
|SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali | |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali | ||
|Name=Literal Reification | |Name=Literal Reification | ||
− | |Intent= | + | |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 | + | |CompetencyQuestion=What is the context in which entities refer to a particular literal value? , |
+ | 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. | |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 | ||
|Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value. | |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value. | ||
− | |Scenario= | + | |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. |
+ | |CPInstantiationExample=http://www.essepuntato.it/2010/06/sc1.ttl , http://www.essepuntato.it/2010/06/sc2.ttl | ||
|SpecializationOf=Region | |SpecializationOf=Region | ||
|RelatedCP=Region | |RelatedCP=Region |
Diagram
The Literal Reification Content OP locally defines the following ontology elements:
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:
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 ] .
No scenario is added to this Content OP.
This revision (revision ID 10183) takes in account the reviews: none
Other info at evaluation tab
![]() |
Submission to event |
---|