Resources and Properties Clause Samples
The "Resources and Properties" clause defines the specific assets, materials, or rights that are made available or utilized under the agreement. It typically outlines what resources (such as equipment, personnel, or intellectual property) each party is responsible for providing or maintaining, and may specify conditions for their use, access, or return. By clearly delineating these responsibilities, the clause helps prevent disputes over ownership or access and ensures that all parties understand their obligations regarding the resources and properties involved in the contract.
Resources and Properties. The Service adopts a Factory Pattern and creates a WS-Resource for each Metadata Collection. The Metadata Manager Factory creates new Collection Managers and offers some cross- Collection operations. Moreover, it operates on Metadata Objects as Information Objects related to other Information Objects and not as Members of Metadata Collections.
Resources and Properties. It is a stateful WSRF service following the Factory/Instance pattern. It uses WS- Resources to represent the gLite jobs. Such a kind of resource contains the following job information:
Resources and Properties. This service adopts a ▇▇▇▇▇▇▇▇▇ Pattern. The resource managed exposes the operational status of the service by declaring the number of software packages currently managed and the number of software packages waiting for approval.
Resources and Properties. For each Aggregator Source the IS-IC is requested to aggregate an ISICResource is created and managed (for each Aggregator Source registration a new ServiceGroupEntry is created). Such a WS-Resource extends the AggregatorServiceGroupResource and each time the state of the ServiceGroupEntry changes the underlying Aggregator Framework invokes the relative delivery method.
Resources and Properties. THE VRE Manager adopts the Factory pattern. In particular, it creates and manages two types of resources: the VREManagerVREScope and the VREManagerVOScope. The former, i.e. the VREManagerVREScope, is created whenever a new VRE is created and used to keep track of the status of the VRE including the set of resources belonging to it, e.g. the list of the gHNs, the list of the Running Instances, the list of Collections. For such a resource the service exposes the VRE name and its ID. The latter, i.e. the VREManagerVOScope, is created to manage each VO and used to manage it with respect to the purpose of this service, i.e. keep track of the set of VO mandatory services deployed. For such a resource the service exposes the VO name and the relative map, i.e. the IDs of the backbone services (non VRE specific) governing the operation of the VO and the relative VRE, e.g. the Software Repository, the IS-Registry.
Resources and Properties. The Archive Import Service is implemented as a stateful WSRF-compliant web-service, following a factory-instance pattern, and publishes a WS-resource for each instance. The WS-resource contains the parameters that are used to create the instance (e.g. the related AISL script), but also contains summary information like the current status of an import (on-going, completed, continuous), the collections involved in the import, information on errors and other information useful for monitoring the import of collections.
Resources and Properties. The CSValidator service is implemented as a stateless WRSF-compliant service. It does not publish any resource on the Information system.
Resources and Properties. The Service adopts a Factory pattern and creates a WS-Resource per each XML Indexer. Since there are two kinds of XML Indexer, there are also two kinds of WS-Resource that the Factory service can create: the GCUBEDaix resource and the WSDaix resource. The state of each Indexer is published in the DIS by means of its WS-ResourceProperties. These resource properties includes the creation parameters and, if the Indexer is a WSDaix, the SetTerminationTime and CurrentTime WS-ResourceProperties. A GCUBEDaix operates on a collection of homogeneous XML documents bound to a specific Metadata Collection. Since the managed XML documents are wrapped in the Metadata envelope, each document is identified by a unique ID (the Metadata Object ID) and this allows a more advanced management of this type of Indexer with respect to the WSDaix one.
Resources and Properties. The CSEngine is a stateful web service. Each running CSEngine service provides a WSRF resource for process instances it is involved in. The purpose of these resources is to allow for the monitoring (cf. Section 8.4.11) of the execution of a process, as the execution proceeds, for the coordination of process joins (where parts of the process might be executed on different nodes of the infrastructure and need to “agree” on the node where the process join takes place), and for retrieving the result of a process which was run asynchronously. All resource properties that are available for the process instance have a dynamic QName (based on the process instance ID, and possibly information on which step in the
Resources and Properties. The Content Management Service is implemented as a stateless WRSF-compliant web service. It does not publish any resource, and only depends on the underlying Storage Management Service for its operation.