Difference between revisions of "Scope Management"
Manuele.simi (Talk | contribs) (→Modelling Scope) |
Manuele.simi (Talk | contribs) (→Modelling Scope) |
||
| Line 8: | Line 8: | ||
== Modelling Scope == | == Modelling Scope == | ||
| − | Three levels of scope may be assigned to a resource: a gCube Infrastructure (GI), a Virtual Organisation (VO), or a Virtual Research Environment (VRE). | + | Three levels of scope may be assigned to a resource: a ''gCube Infrastructure'' (GI), a ''Virtual Organisation'' (VO), or a ''Virtual Research Environment'' (VRE). |
| − | The levels are hierarchically ordered: GIs are above VOs and VREs are below VOs. | + | The levels are hierarchically ordered: GIs are ''above'' VOs and VREs are ''below'' VOs. |
We follow a grammar to denote scopes in a way which explicitates their hierarchical relationships: | We follow a grammar to denote scopes in a way which explicitates their hierarchical relationships: | ||
| − | + | <pre> | |
| − | + | SCOPE : = = GI | VO | VRE | |
GI :== /l | GI :== /l | ||
VO :== GI/l | VO :== GI/l | ||
| − | VRE :== VO/l | + | VRE :== VO/l |
| + | </pre> | ||
where l ranges over an alphabet of labels. | where l ranges over an alphabet of labels. | ||
| − | For convenience, we write S1 below S2 to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly below S2. | + | For convenience, we write '''S1 below S2''' to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly below S2. |
| − | Similarly, we write S1 above S2 to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly above S2. | + | Similarly, we write '''S1 above S2''' to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly above S2. |
| − | We model scoping as a binary relationship between resource and scopes. | + | We model '''scoping''' as a binary relationship between resource and scopes. |
| − | We write R in S to denote a pair (R,S) of a resource R and a scope S in the scoping relationship. | + | We write '''R in S''' to denote a pair (R,S) of a resource R and a scope S in the scoping relationship. |
== gCube Calls & the gCube Handler == | == gCube Calls & the gCube Handler == | ||
Revision as of 21:58, 15 August 2008
[coming soon]
Contents
What's in Scope?
Any gCube resource may only be shared within one or more scopes in the infrastructure on which it is deployed. Outside its scopes, in particular, the resource can neither be discovered nor used.
Scope is a multi-valued property of all gCube resources.
Modelling Scope
Three levels of scope may be assigned to a resource: a gCube Infrastructure (GI), a Virtual Organisation (VO), or a Virtual Research Environment (VRE).
The levels are hierarchically ordered: GIs are above VOs and VREs are below VOs.
We follow a grammar to denote scopes in a way which explicitates their hierarchical relationships:
SCOPE : = = GI | VO | VRE GI :== /l VO :== GI/l VRE :== VO/l
where l ranges over an alphabet of labels.
For convenience, we write S1 below S2 to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly below S2. Similarly, we write S1 above S2 to indicate that S1 and S2 denote the scope or that S1 is directly or indirectly above S2.
We model scoping as a binary relationship between resource and scopes. We write R in S to denote a pair (R,S) of a resource R and a scope S in the scoping relationship.
gCube Calls & the gCube Handler
[coming soon]
Scope Managers
[coming soon]
