OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

icom message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [icom] Scope?


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
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]