Re: [icom] Scope?

["Eric S. Chan" <eric-s.chan@oracle.com>]

Please see my response to Patrick's comments:

[Patrick] OK, but I got the impression from the presentation today and 
to some degree confirmed by the text that "enterprises, organizations, 
and workspaces" define scopes. Yes?

[Eric] In Beehive Object Model (BOM), Scope is superclass of Community,  
Enterprise, Organization, and Workspace. Hence a workspace, say the  
"ICOM TC Workspace," is a scope. The "ICOM TC Workspace" contains a 
variety of entities. A workspace defines a boundary--you can query 
whether an entity is contained or not contained by the workspace.

[Patrick] The reason I ask is that when I think about "scope" as we use 
the terms in topic maps (not arguing for that definition here) I think 
of it as a characteristic that is possessed by an entity, not that it 
defines. Such that any number of entity could, at least in theory, share 
the same scope.

[Eric]  The workspace is a neighborhood shared by entities in the 
workspace. "ICOM TC Workspace" itself is an entity in a parent 
community, say "OASIS TC Community," which is a scope. Thus the "ICOM TC 
Workspace" shares the scope "OASIS TC Community" with other TC workspaces.

[Patrick] I suppose it could be thought of as "re-use" of scope by more 
than one top level entity. Moreover, I suspect that it may be useful for 
entities under a top level entity to not only inherit a "scope" but also 
be able to be assigned one or more other scopes.

[Marc] Hence entities might be necessarily related to more than one 
project.

[Eric] An entity in "ICOM TC Workspace" scope is also in the "OASIS TC 
Community" scope, which as you pointed out, is an "inherited" scope. As 
part of the ICOM work, we can review how an entity can be placed into 
multiple workspaces or communities and hence be explicitly assigned to 
more than one scope.

[Patrick] That implies to me that scope should be defined separate and 
apart from any top level entity and applicable separate from that entity.

[Eric] I believe the Beehive Object Model of scope can be extended to 
allow explicit assignment of an entity to more than one scope. It is 
similar to the CMIS model for filing the same document in multiple folders.

Thanks,
Eric

marco pallot wrote:
> Hi Patrick,
>
> Interesting comments about the "scope" used in the Beehive model.
>
> My interpretation is that "scope" could be for example projects that 
> bring together different "enterprises" and "organisations" as well as 
> "individuals" (crowdsourcing) that are partners collaborating in the 
> projects within different "workspaces".
>
> Hence entities might be necessarily related to more than one project.
>
> Cheers,
> Marc
>
> Marc Pallot
> Centre for Concurrent Enterprise
> Nottingham University
> Collaborative Work & Infrastructure
> ESoCE-NET
>
>
>
> ----- Original Message ----- From: "Patrick Durusau" 
> <patrick@durusau.net>
> To: <icom@lists.oasis-open.org>
> Sent: Friday, April 03, 2009 2:05 AM
> Subject: [icom] Scope?
>
>
>> Greetings!
>>
>> Just checking my understanding of "scope" as used in the Beehive model.
>>
>> The text says:
>>
>> "A scope defines a logical region or neighborhood in the universe of 
>> entities that is governed by a common set of policies, which includes 
>> memberships, roles, and groups. Enterprises, organizations, and 
>> workspaces define the boundaries of hierarchies of scopes."
>>
>> OK, but I got the impression from the presentation today and to some 
>> degree confirmed by the text that "enterprises, organizations, and 
>> workspaces" define scopes. Yes?
>>
>> The reason I ask is that when I think about "scope" as we use the 
>> terms in topic maps (not arguing for that definition here) I think of 
>> it as a characteristic that is possessed by an entity, not that it 
>> defines.
>>
>> Such that any number of entity could, at least in theory, share the 
>> same scope.
>>
>> I suppose it could be thought of as "re-use" of scope by more than 
>> one top level entity. Moreover, I suspect that it may be useful for 
>> entities under a top level entity to not only inherit a "scope" but 
>> also be able to be assigned one or more other scopes.
>>
>> That implies to me that scope should be defined separate and apart 
>> from any top level entity and applicable separate from that entity.
>>
>> Hope everyone is having a great day!
>>
>> Patrick
>>
>> -- 
>> Patrick Durusau
>> patrick@durusau.net
>> Chair, V1 - US TAG to JTC 1/SC 34
>> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
>> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php