Indeed. But isn't the case that for every single website, there is a single LegalEntity to attach it to, use cases otherwise paired downward on the spectrum--or attributed to--after that?
Michael A. Norton
________________________________
From: Patrick Logan <patrickdlogan@gmail.com>
To: Mike Norton <xsideofparadise@yahoo.com>
Cc: public-egov-ig@w3.org; Dave Reynolds <dave.e.reynolds@googlemail.com>; William Waites <william.waites@okfn.org>; Linked Data community <public-lod@w3.org>; William Waites <ww-keyword-okfn.193365@styx.org>; Emmanouil Batsis (Manos) <manos@abiss.gr>
Sent: Mon, June 7, 2010 4:50:03 PM
Subject: Re: Organization ontology
Large corporations often have multiple legal entities and many informal, somewhat overlapping business organizations. Just saying. I wrangled with that. There're several different use cases for these for internal vs external, customer/vendor, financial vs operations, etc.
On Jun 7, 2010 3:19 PM, "Mike Norton" <xsideofparadise@yahoo.com> wrote:
>
>
>I can see Manos' point. It seems that LegalEntity rather the Organization would work well under a sub-domain such as .LAW or .DOJ or .SEC, but under other sub-domains such as .NASA, the Organization element might be better served as ProjectName. All instances would help specify the Organization type, while keeping Organization as the general unstylized element is probably ideal, as inferred by William Waites.
>>
>Michael A. Norton
>
>
>
>
>
>
________________________________
>>From: Emmanouil Batsis (Manos) manos@abiss.gr
>
>>>
>>>a) the way i get FormalOrganization, it could as well be called LegalEntity to be more precise....
>
Received on Tuesday, 8 June 2010 02:49:50 UTC