ontology-summit
[Top] [All Lists]

Re: [ontology-summit] First Model Bench Challenge

To: "Ontology Summit 2012 discussion" <ontology-summit@xxxxxxxxxxxxxxxx>
From: "doug foxvog" <doug@xxxxxxxxxx>
Date: Wed, 2 May 2012 13:55:12 -0400
Message-id: <d7a1e4ab0779b0fff25bf725f00bd46e.squirrel@xxxxxxxxxxxxxxxxx>
On Wed, May 2, 2012 10:05, Peter R. Benson wrote:
> Interesting choice of concept at least it will demonstrate the challenge.
> Marriage is a legal construct as in it is "recognized" by government as
> the law makers and enforcers.    (01)

Marriage is a religious concept, a social concept, a legal concept, and
a personal concept between two people.  One of these does not
necessarily mean another.    (02)

Between two people, it is a commitment to each other.
As a religious concept, it is a commitment of two people to a religious
body or a supernatural being respected by the religious body.
As a legal concept, it is a commitment to a government.
As a social concept, it is a situation that affects how those who are aware
of the situation interact with the participants.    (03)

Numerous rules can be stated for each of these contexts.    (04)

Note that a couple can be
* married in the view of a religion and not married in the view of the state
* married in the view of the state and not married in the view of a religion
* married in the view of one state and not married in the view of another
* secretly married such that no state and/or religious body and/or society
   in general is aware
* a couple can pretend to be married, such that in the view of the state/
   religious body/society they are married, when "in actuality" they are
   not.    (05)

> The ceremony is just an overlay to the creation of a legal
> document typical recorded in a registry.    (06)

This would be in the legal context.  In the religious context, the legal
document is just an overlay to the ceremony!    (07)

> The
> definition of the term should reflect the legal requirements necessary to
> create "a marriage". It is actually very similar to any contract entered
> into by two parties and upheld by the state.    (08)

Again, this is in the legal context.    (09)

In all contexts, it seems that Marriage is a subclass of Agreement.  In
some contexts, a Marriage (or all marriages) are also LegalAgreements.
Those that are LegalAgreements have all the properties of LegalAgreements
(as well as additional properties).    (010)

-- doug f    (011)

> Peter
> Cell: +1 610 462 5923
>
> On May 1, 2012, at 4:43 PM, Jack Ring <jring7@xxxxxxxxx> wrote:
>
>> Well said.
>>
>> On Apr 30, 2012, at 6:54 PM, Hans Polzer wrote:
>>
>>> Isn't it both? Marriage is both a state transition (the rite that
>>> signals
>>> the transition to a married state from an unmarried state), and a
>>> steady
>>> state condition after the state transition occurs (as in "their
>>> marriage has
>>> lasted for 50 years"). The word "wedding" is often used to distinguish
>>> between the state transition and the steady state condition, denoting
>>> the
>>> former but not the latter (although common usage isn't always precise
>>> on
>>> this point, as  in "wedded bliss").
>>>
>>> Hans
>>>
>>> Hans
>>>
>>> -----Original Message-----
>>> From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
>>> [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack
>>> Ring
>>> Sent: Monday, April 30, 2012 8:44 PM
>>> To: doug@xxxxxxxxxx; Ontology Summit 2012 discussion
>>> Subject: Re: [ontology-summit] First Model Bench Challenge
>>>
>>> ??
>>> Marriage is a situation in which a couple BECOMES married.") On Apr 30,
>>> 2012, at 1:39 PM, doug foxvog wrote:
>>>
>>>> Marriage is a situation in which a couple is married.")
>>>
>>>
>>> _________________________________________________________________
>>> Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
>>> Subscribe/Config:
>>> http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
>>> Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
>>> Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
>>> Community Wiki:
>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
>>> Community Portal: http://ontolog.cim3.net/wiki/
>>>
>>>
>>> _________________________________________________________________
>>> Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
>>> Subscribe/Config:
>>> http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
>>> Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
>>> Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
>>> Community Wiki:
>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
>>> Community Portal: http://ontolog.cim3.net/wiki/
>>
>>
>> _________________________________________________________________
>> Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
>> Subscribe/Config:
>> http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
>> Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
>> Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
>> Community Wiki:
>> http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
>> Community Portal: http://ontolog.cim3.net/wiki/
>
> _________________________________________________________________
> Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
> Subscribe/Config:
> http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
> Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
> Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
> Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
> Community Portal: http://ontolog.cim3.net/wiki/
>    (012)



_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/   
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/  
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012  
Community Portal: http://ontolog.cim3.net/wiki/     (013)
<Prev in Thread] Current Thread [Next in Thread>