http://ontologydesignpatterns.org/api.php?action=feedcontributions&feedformat=atom&user=SilvioPeroni 2026-05-22T17:58:22Z User contributions MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=Submissions:Description_in_Range&diff=12611 2016-07-13T14:03:42Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Dir.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Description in Range<br /> |Intent=This pattern allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |CompetencyQuestion=What are the descriptions related to a particular entity? , What entities are described in terms of a particular concept? , How the concepts involved in the description of a certain entity have been restricted within particular bounds?<br /> |ContentODPDescription=The Description In Range (DIR) ontology design patterns is a specialization of the Description ODP, that allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |ReusableOWLBuildingBlock=https://w3id.org/food/ontology/dir<br /> |Scenario=# Scenario 1: In order to obtain the registered quality scheme PDO, the wine &quot;Amarone della Valpolicella&quot; has to comply with a set of rules including grape composition rules. In particular, it has to be made with a specific ampelographic composition that indicates the different types of grapes that contribute to form the wine, together with their percentage ranges. In this case, the &quot;Amarone della Valpolicella&quot; must be composed (among the others) by Corvina and Corvinone grapes from 45% to 95%. --- # Scenario 2: The policy document of &quot;Parmigiano Reggiano&quot; indicates that, for consumers, it presents a set of characteristics among which the &quot;diameter of the plain faces&quot;, which must be within the range &quot;35-45 cm&quot;, and the &quot;external aspect&quot; that should be &quot;natural straw-coloured rind&quot;.<br /> |HasComponent=Description<br /> |SpecializationOf=Description<br /> |RelatedCP=Description<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=DescriptionInRange<br /> }}<br /> {{Has Element Template<br /> |HasElement=Entity<br /> }}<br /> {{Has Element Template<br /> |HasElement=isRangedByValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=isDescribedBy<br /> }}<br /> {{Has Element Template<br /> |HasElement=describes<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP 2016<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Description_in_Range&diff=12610 2016-07-13T14:02:42Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Dir.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Description in Range<br /> |Intent=This pattern allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |CompetencyQuestion=What are the descriptions related to a particular entity?<br /> What entities are described in terms of a particular concept?<br /> How the concepts involved in the description of a certain entity have been restricted within particular bounds?<br /> |ContentODPDescription=The Description In Range (DIR) ontology design patterns is a specialization of the Description ODP, that allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |ReusableOWLBuildingBlock=https://w3id.org/food/ontology/dir<br /> |Scenario=# Scenario 1: In order to obtain the registered quality scheme PDO, the wine &quot;Amarone della Valpolicella&quot; has to comply with a set of rules including grape composition rules. In particular, it has to be made with a specific ampelographic composition that indicates the different types of grapes that contribute to form the wine, together with their percentage ranges. In this case, the &quot;Amarone della Valpolicella&quot; must be composed (among the others) by Corvina and Corvinone grapes from 45% to 95%. --- # Scenario 2: The policy document of &quot;Parmigiano Reggiano&quot; indicates that, for consumers, it presents a set of characteristics among which the &quot;diameter of the plain faces&quot;, which must be within the range &quot;35-45 cm&quot;, and the &quot;external aspect&quot; that should be &quot;natural straw-coloured rind&quot;.<br /> |HasComponent=Description<br /> |SpecializationOf=Description<br /> |RelatedCP=Description<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=DescriptionInRange<br /> }}<br /> {{Has Element Template<br /> |HasElement=Entity<br /> }}<br /> {{Has Element Template<br /> |HasElement=isRangedByValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=isDescribedBy<br /> }}<br /> {{Has Element Template<br /> |HasElement=describes<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP 2016<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Description_in_Range&diff=12609 2016-07-13T13:59:28Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Dir.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Description in Range<br /> |Intent=This pattern allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |CompetencyQuestion=1. What are the descriptions related to a particular entity?<br /> <br /> 2. What entities are described in terms of a particular concept?<br /> <br /> 3. How the concepts involved in the description of a certain entity have been restricted within particular bounds?<br /> |ContentODPDescription=The Description In Range (DIR) ontology design patterns is a specialization of the Description ODP, that allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.<br /> |ReusableOWLBuildingBlock=https://w3id.org/food/ontology/dir<br /> |Scenario=# Scenario 1 In order to obtain the registered quality scheme PDO, the wine &quot;Amarone della Valpolicella&quot; has to comply with a set of rules including grape composition rules. In particular, it has to be made with a specific ampelographic composition that indicates the different types of grapes that contribute to form the wine, together with their percentage ranges. In this case, the &quot;Amarone della Valpolicella&quot; must be composed (among the others) by Corvina and Corvinone grapes from 45% to 95%. # Scenario 2 The policy document of &quot;Parmigiano Reggiano&quot; indicates that, for consumers, it presents a set of characteristics among which the &quot;diameter of the plain faces&quot;, which must be within the range &quot;35-45 cm&quot;, and the &quot;external aspect&quot; that should be &quot;natural straw-coloured rind&quot;.<br /> |HasComponent=http://www.ontologydesignpatterns.org/cp/owl/description.owl<br /> |SpecializationOf=http://www.ontologydesignpatterns.org/cp/owl/description.owl<br /> |RelatedCP=http://www.ontologydesignpatterns.org/cp/owl/description.owl<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=DescriptionInRange<br /> }}<br /> {{Has Element Template<br /> |HasElement=Entity<br /> }}<br /> {{Has Element Template<br /> |HasElement=isRangedByValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveLowerBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasNonInclusiveUpperBoundValue<br /> }}<br /> {{Has Element Template<br /> |HasElement=isDescribedBy<br /> }}<br /> {{Has Element Template<br /> |HasElement=describes<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP 2016<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Description_in_Range&diff=12608 2016-07-13T13:53:14Z

<p>SilvioPeroni: Imported from OWL file.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |ReusableOWLBuildingBlock=https://w3id.org/food/ontology/dir<br /> |Name=Description in Range<br /> }}<br /> {{Element list header}}<br /> <br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}{{Modeling issues about me}}{{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:Dir.png&diff=12607 2016-07-13T13:51:52Z

<p>SilvioPeroni: </p> <hr /> <div></div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification/Scenario_2&diff=10296 2010-10-23T00:05:36Z

<p>SilvioPeroni: </p> <hr /> <div>{{Scenario Template<br /> |Description=NameHistory3.0 is a (fictional) institution that keeps track of all the names of people, and stores them as an ABox of the FOAF ontology. In particular, each person is stored as an individual of the class foaf:Person with a specific first name (data property foaf:givenName) and family name (data property foaf:familyName). On 24/09/2010, Bruce Wayne formally applied for changing his first name to Jack. Since NameHistory3.0 has to keep track of everything concerning names of people, on that date “Jack” was added as Mr. Wayne's first name. It was then that NameHistory3.0 noticed that, without any additional information, it is not possible to know which of the two first names are legally valid at any given point in time. A solution to that scenario, which avoids any modification of the ontology model and consequently of the entire triple store (operation that is obviously time-consuming and error-prone), is to use the literal reification pattern in combination with the new expressivity for punning in OWL 2. Through them, it is possible to define a literal individual as also belonging to the class foaf:givenName – that is actually defined as a data property, but may be additionally be meta-modelled as a class. We can now associate a particular time interval to each literal, so as to represent when the literal itself, i.e., the given name, is legally valid.<br /> |Image=LiteralReificationExample_revised.png<br /> |OWLFile=http://www.essepuntato.it/2010/06/sc2.ttl<br /> |ScenarioOf=Submissions:Literal Reification<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:LiteralReificationExample_revised.png&diff=10295 2010-10-23T00:03:58Z

<p>SilvioPeroni: </p> <hr /> <div></div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=10190 2010-09-30T14:38:02Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification_new.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal.<br /> |Domain=General<br /> |CompetencyQuestion=What is the context in which entities refer to a particular literal value? ,<br /> What is the meaning of a particular value considering the context in which it is used?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.<br /> |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.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}[[Category:Review assigned]]</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification/Scenario_2&diff=10189 2010-09-30T14:27:25Z

<p>SilvioPeroni: New page: {{Scenario Template |Description=NameHistory3.0 is a (fictional) institution that keeps track of all the names of people, and stores them as an ABox of the FOAF ontology. In particular, ea...</p> <hr /> <div>{{Scenario Template<br /> |Description=NameHistory3.0 is a (fictional) institution that keeps track of all the names of people, and stores them as an ABox of the FOAF ontology. In particular, each person is stored as an individual of the class foaf:Person with a specific first name (data property foaf:givenName) and family name (data property foaf:familyName). On 24/09/2010, Bruce Wayne formally applied for changing his first name to Jack. Since NameHistory3.0 has to keep track of everything concerning names of people, on that date “Jack” was added as Mr. Wayne's first name. It was then that NameHistory3.0 noticed that, without any additional information, it is not possible to know which of the two first names are legally valid at any given point in time. A solution to that scenario, which avoids any modification of the ontology model and consequently of the entire triple store (operation that is obviously time-consuming and error-prone), is to use the literal reification pattern in combination with the new expressivity for punning in OWL 2. Through them, it is possible to define a literal individual as also belonging to the class foaf:givenName – that is actually defined as a data property, but may be additionally be meta-modelled as a class. We can now associate a particular time interval to each literal, so as to represent when the literal itself, i.e., the given name, is legally valid.<br /> |Image=LiteralReificationExample2.png<br /> |OWLFile=http://www.essepuntato.it/2010/06/sc2.ttl<br /> |ScenarioOf=Submissions:Literal Reification<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:LiteralReificationExample2.png&diff=10188 2010-09-30T14:26:46Z

<p>SilvioPeroni: </p> <hr /> <div></div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification/Scenario_1&diff=10187 2010-09-30T14:26:03Z

<p>SilvioPeroni: </p> <hr /> <div>{{Scenario Template<br /> |Description=Used frequently in the Web 2.0, descriptive tags such as the ones used in folksonomies are keywords (e.g., strings) assigned to a particular resource, such as a web document, with the intent to describe it. Just like words in any natural language, tags may have different meanings depending on the context in which they are used. For instance, the word “Paris” may be either a name of a city or a first name of a person. Here, it is clear that the act of tagging with “Paris” both the Wikipedia pages about the Eiffel Tower and the one about Paris Hilton hides two different intents: in the former case, “Paris” denotes the city in which the tower stands; in the latter case, “Paris” denotes a particular person, i.e., Paris Hilton. Using the literal reification pattern it is possible to express descriptive tags as first class objects in OWL, by considering them as proper individuals of the class litre:Literal. Different individuals may thus represent different meanings even if their literal values are identical.<br /> |Image=LiteralReificationExample1.png<br /> |OWLFile=http://www.essepuntato.it/2010/06/sc1.ttl<br /> |ScenarioOf=Submissions:Literal Reification<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification/Scenario_1&diff=10186 2010-09-30T14:25:08Z

<p>SilvioPeroni: New page: {{Scenario Template |Description=Used frequently in the Web 2.0, descriptive tags such as the ones used in folksonomies are keywords (e.g., strings) assigned to a particular resource, such...</p> <hr /> <div>{{Scenario Template<br /> |Description=Used frequently in the Web 2.0, descriptive tags such as the ones used in folksonomies are keywords (e.g., strings) assigned to a particular resource, such as a web document, with the intent to describe it. Just like words in any natural language, tags may have different meanings depending on the context in which they are used.<br /> For instance, the word “Paris” may be either a name of a city or a first name of a person. Here, it is clear that the act of tagging with “Paris” both the Wikipedia pages about the Eiffel Tower and the one about Paris Hilton hides two different intents: in the former case, “Paris” denotes the city in which the tower stands; in the latter case, “Paris” denotes a particular person, i.e., Paris Hilton.<br /> Using the literal reification pattern it is possible to express descriptive tags as first class objects in OWL, by considering them as proper individuals of the class litre:Literal. Different individuals may thus represent different meanings even if their literal values are identical.<br /> |Image=LiteralReificationExample1.png<br /> |OWLFile=http://www.essepuntato.it/2010/06/sc1.ttl<br /> |ScenarioOf=Submissions:Literal Reification<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:LiteralReificationExample1.png&diff=10185 2010-09-30T14:24:44Z

<p>SilvioPeroni: </p> <hr /> <div></div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=10184 2010-09-30T14:22:46Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification_new.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal.<br /> |Domain=General<br /> |CompetencyQuestion=What is the context in which entities refer to a particular literal value? ,<br /> What is the meaning of a particular value considering the context in which it is used?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.<br /> |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.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Review assigned]]<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=10183 2010-09-30T14:21:55Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification_new.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal.<br /> |Domain=General<br /> |CompetencyQuestion=What is the context in which entities refer to a particular literal value? ,<br /> What is the meaning of a particular value considering the context in which it is used?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.<br /> |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.<br /> |CPInstantiationExample=http://www.essepuntato.it/2010/06/sc1.ttl , http://www.essepuntato.it/2010/06/sc2.ttl<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Review assigned]]<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=10182 2010-09-30T14:12:56Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification_new.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Review assigned]]<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:Literalreification_new.png&diff=10181 2010-09-30T14:12:38Z

<p>SilvioPeroni: </p> <hr /> <div></div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9817 2010-08-10T16:39:23Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Consequences=This pattern allows to specify different contexts and/or meanings to a particular literal value.<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> <br /> [[Category:Waiting for review]]<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9816 2010-08-10T16:27:41Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> <br /> <br /> <br /> <br /> [[Category:Waiting for review]]<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP:2010<br /> }}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9815 2010-08-10T16:26:28Z

<p>SilvioPeroni: Article is waiting for review.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> [[Category:Waiting for review]]</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9814 2010-08-10T16:24:46Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=AldoGangemi, SilvioPeroni, FabioVitali<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9813 2010-08-10T16:22:05Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=Literal<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasSameLiteralValueAs<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteral<br /> }}<br /> {{Has Element Template<br /> |HasElement=isLiteralOf<br /> }}<br /> {{Has Element Template<br /> |HasElement=hasLiteralValue<br /> }}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9812 2010-08-10T16:19:49Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Scenario=A Delicious user adds the tag 'Paris' to the wiki article about Joyce's Ulysses, that represents the city in which the novel was published the very first time. Another Delicious user adds the same tag to the article about Paris Hilton, where here 'Paris' stands for a first name of a person.<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9811 2010-08-10T16:07:03Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |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: &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document ; prism:keyword :parisTag1 . &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document ; prism:keyword :parisTag2 . :parisTag1 a litre:Literal ; litre:hasLiteralValue &quot;Paris&quot; ; a [ a skos:Concept ; skos:definition &quot;the name associated to a particular city&quot;@en ] . :parisTag2 a litre:Literal ; litre:hasSameLiteralValueAs :parisTag1 ; a [ a skos:Concept ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> 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:<br /> <br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&lt;/nowiki&gt;<br /> # &lt;nowiki&gt;http://en.wikipedia.org/wiki/Paris_Hilton&lt;/nowiki&gt;<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;pre&gt;<br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> &lt;/pre&gt;<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9810 2010-08-10T15:55:48Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |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?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |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: &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document ; prism:keyword :parisTag1 . &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document ; prism:keyword :parisTag2 . :parisTag1 a litre:Literal ; litre:hasLiteralValue &quot;Paris&quot; ; a [ a skos:Concept ; skos:definition &quot;the name associated to a particular city&quot;@en ] . :parisTag2 a litre:Literal ; litre:hasSameLiteralValueAs :parisTag1 ; a [ a skos:Concept ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> |SpecializationOf=Region<br /> |RelatedCP=Region<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9809 2010-08-10T15:48:17Z

<p>SilvioPeroni: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=Literalreification.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |Domain=General<br /> |CompetencyQuestion=What is the context in which entities refer to a particular literal value?<br /> What are the meanings of a particular value considering the context in which it is used?<br /> |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.<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |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: &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document ; prism:keyword :parisTag1 . &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document ; prism:keyword :parisTag2 . :parisTag1 a litre:Literal ; litre:hasLiteralValue &quot;Paris&quot; ; a [ a skos:Concept ; skos:definition &quot;the name associated to a particular city&quot;@en ] . :parisTag2 a litre:Literal ; litre:hasSameLiteralValueAs :parisTag1 ; a [ a skos:Concept ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=Submissions:Literal_Reification&diff=9808 2010-08-10T15:40:49Z

<p>SilvioPeroni: Imported from OWL file.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=<br /> }}<br /> {{Content OP Proposal Template<br /> |HasComponent=<br /> |SpecializationOf=<br /> |RelatedCP=<br /> |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:<br /> 1) http://en.wikipedia.org/wiki/Ulysses_%28novel%29<br /> 2) http://en.wikipedia.org/wiki/Paris_Hilton<br /> <br /> 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.<br /> <br /> 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:<br /> <br /> &lt;http://en.wikipedia.org/wiki/Ulysses_%28novel%29&gt; a foaf:Document<br /> ; prism:keyword :parisTag1 .<br /> <br /> &lt;http://en.wikipedia.org/wiki/Paris_Hilton&gt; a foaf:Document<br /> ; prism:keyword :parisTag2 .<br /> <br /> :parisTag1 a litre:Literal<br /> ; litre:hasLiteralValue &quot;Paris&quot;<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the name associated to a particular city&quot;@en ] .<br /> <br /> :parisTag2 a litre:Literal<br /> ; litre:hasSameLiteralValueAs :parisTag1<br /> ; a [ a skos:Concept<br /> ; skos:definition &quot;the first name of a person&quot;@en ] .<br /> |ReusableOWLBuildingBlock=http://www.essepuntato.it/2010/06/literalreification<br /> |Intent=The goal of this pattern is to allow the reification of literal values within OWL.<br /> |CompetencyQuestion=What is the context in which entities refer to a particular literal value?<br /> What are the meanings of a particular value considering the context in which it is used?<br /> |SubmittedBy=SilvioPeroni<br /> |Name=Literal Reification<br /> }}<br /> {{Element list header}}<br /> <br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}{{Modeling issues about me}}{{My references}}</div>

SilvioPeroni http://ontologydesignpatterns.org/index.php?title=File:Literalreification.png&diff=9807 2010-08-10T15:39:09Z

<p>SilvioPeroni: A diagram for the proposed Literal Reification pattern</p> <hr /> <div>A diagram for the proposed Literal Reification pattern</div>

SilvioPeroni