http://ontologydesignpatterns.org/api.php?action=feedcontributions&feedformat=atom&user=LUIGISELMI 2026-05-12T18:02:40Z User contributions MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=Community:Sex_(of_those_who_are_not_angels)&diff=10897 2012-01-23T13:36:08Z

<p>LUIGISELMI: how this issue is managed in DOLCE</p> <hr /> <div>{{TitleDescription Template<br /> |Title=Sex (of those who are not angels)<br /> |Description=Sex, or more properly genre, can be used to separate a species into two disjoint subsets: male and female. The two properties (in the sense of DOLCE) are rigid (by nature at list). So it seems to make sense to model the genre of a species, human for example, as two subproperties (subclasses) of dul:NaturalPerson: Woman and Man. An other approach could be tu create a :Genre as a quality and then two qualia :Male and :Female. The :Genre dul:isQualityOf dul:NaturalPerson while :Male and :Female should be values available for :Genre. The problem with this approach is that DUL doesn't have Quale as property and there is not a relation between a dul:Quality and some other entity that could be a quale. In DOLCE a dol:quality and a dol:quale could be linked through the dol:hasQuale relation. <br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Sex_(of_those_who_are_not_angels)&diff=10896 2012-01-23T13:28:48Z

<p>LUIGISELMI: DUL doesn't have qualia</p> <hr /> <div>{{TitleDescription Template<br /> |Title=Sex (of those who are not angels)<br /> |Description=Sex, or more properly genre, can be used to separate a species into two disjoint subsets: male and female. The two properties (in the sense of DOLCE) are rigid (by nature at list). So it seems to make sense to model the genre of a species, human for example, as two subproperties (subclasses) of dul:NaturalPerson: Woman and Man. An other approach could be tu create a :Genre as a quality and then two qualia :Male and :Female. The :Genre dul:isQualityOf dul:NaturalPerson while :Male and :Female should be values available for :Genre. The problem with this approach is that DUL doesn't have Quale as property.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Sex_(of_those_who_are_not_angels)&diff=10895 2012-01-23T11:22:15Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Sex (of those who are not angels)<br /> |Description=Sex, or more properly genre, can be used to separate a species into two disjoint subsets: male and female. The two properties (in the sense of DOLCE) are rigid (by nature at list). So it seems to make sense to model the genre of a species, human for example, as two subproperties (subclasses) of dul:NaturalPerson: Woman and Man. An other approach could be tu create a Genre as a quality and then two qualia Male and Female as qualities of Natural Person or what ever other biological entity.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Sex_(of_those_who_are_not_angels)&diff=10894 2012-01-23T11:21:11Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Sex (of those who are not angels)<br /> |Description=Sex, or more properly genre, can be used to separate a species in to two disjoint subsets: male and female. The two properties (in the sense of DOLCE) are rigid (by nature at list). So it seems to make sense to model the genre of a species, human for example, as two subproperties (subclasses) of dul:NaturalPerson: Woman and Man. An other approach could be tu create a Genre as a quality and then two qualia Male and Female as qualities of Natural Person or what ever other biological entity.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Sex_(of_those_who_are_not_angels)&diff=10893 2012-01-23T11:20:01Z

<p>LUIGISELMI: Two approaches to define the genre of a species</p> <hr /> <div>{{TitleDescription Template<br /> |Title=Sex (of those who are not angels)<br /> |Description=Sex, or more properly genre, can be used to separate a species in to two disjoint subsets: male and female. The two properties (in the sense of DOLCE) are rigid (by nature at list). So it seems to make sense to model the genre of a species, human for example, as two subproperties (subclasses) of dul:NaturalPerson: Woman and Man. An other approach could be tu create a Genre as a quality and then two qualia Male and Female as qualities of Natural Person or what ever other biological entity.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template}}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Data_type_values_in_DOLCE&diff=10892 2012-01-21T15:41:39Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Data type properties<br /> |Description=It happens often that some entity has attributes that are simply strings, an array of characters like the title of a book or the name of a person. It is not clear what pattern should be used in DOLCE (also DUL) in these cases. In a pattern it is suggested to use the data type property dul:hasDataValue to attach a value to an instance, but that should mean that, for a dul:Person, a Name class must be created in advance related to the dul:Person. Another pattern suggests to use dul:Region but it seems quite awkward for names, last names etc. that are not defined in a dimensional space. In the case in which there are too many possible values and we are not interested to link these values to another object it is allowed to use simple data type properties.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Data_type_values_in_DOLCE&diff=10891 2012-01-21T15:41:02Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Data type values in DOLCE<br /> |Description=It happens often that some entity has attributes that are simply strings, an array of characters like the title of a book or the name of a person. It is not clear what pattern should be used in DOLCE (also DUL) in these cases. In a pattern it is suggested to use the data type property dul:hasDataValue to attach a value to an instance, but that should mean that, for a dul:Person, a Name class must be created in advance related to the dul:Person. Another pattern suggests to use dul:Region but it seems quite awkward for names, last names etc. that are not defined in a dimensional space. In the case in which there are too many possible values and we are not interested to link these values to another object it is allowed to use simple data type properties.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template<br /> |Author=Luigi Selmi<br /> }}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Data_type_values_in_DOLCE&diff=10890 2012-01-20T10:20:00Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Data type values in DOLCE<br /> |Description=It happens often that some entity has attributes that are simply strings, an array of characters like the title of a book or the name of a person. It is not clear what pattern should be used in DOLCE (also DUL) in these cases. In a pattern it is suggested to use the data type property dul:hasDataValue to attach a value to an instance, but that should mean that, for a dul:Person, a Name class must be created in advance related to the dul:Person. Another pattern suggests to use dul:Region but it seems quite awkward for names, last names etc. that are not defined in a dimensional space. In the case in which there are too many possible values and we are not interested to link these values to another object it is allowed to use simple data type properties.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template}}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Data_type_values_in_DOLCE&diff=10889 2012-01-20T09:58:09Z

<p>LUIGISELMI: </p> <hr /> <div>{{TitleDescription Template<br /> |Title=Data type values in DOLCE<br /> |Description=It happens often that some entity has attributes that are simply strings, an array of characters like the title of a book or the name of a person. It is not clear what pattern should be used in DOLCE (also DUL) in these cases. In a pattern it is suggested to use the data type property dul:hasDataValue to attach a value to an instance, but that should mean that, for a dul:Person, a Name class must be created in advance related to the dul:Person. Another pattern suggests to use dul:Region but it seems quite awkward for names, last names etc. that are not defined in a dimensional space. In the case in which there are too many possible values and we are not interested to link these values to another object it is allowed to use simple data type values. Names, last names <br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template}}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI http://ontologydesignpatterns.org/index.php?title=Community:Data_type_values_in_DOLCE&diff=10885 2012-01-09T17:14:22Z

<p>LUIGISELMI: Data type values for attributes whose value is a string (like names for person)</p> <hr /> <div>{{TitleDescription Template<br /> |Title=Data type values in DOLCE<br /> |Description=It happens often that some entity has attributes that are simply strings, an array of characters like the title of a book or the name of a person. It is not clear what pattern should be used in DOLCE (also DUL) in these cases. In a pattern it is suggested to use the data type property dul:hasDataValue to attach a value to an instance, but that should mean that, for a dul:Person, a Name class must be created in advance related to the dul:Person. Another pattern suggests to use dul:Region but it seems quite awkward for names, lastnames etc. that are not defined in a dimensional space.<br /> }}<br /> {{Graphical representation}}<br /> {{Modeling Issue Template}}<br /> {{Additional information header}}<br /> <br /> {{My references}}<br /> {{Modeling Issue toolbar}}</div>

LUIGISELMI