|
|
| (114 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| == EGI Glossary (draft) ==
| | {{DeprecatedAndMovedTo|new_location=http://go.egi.eu/glossary}} |
| | |
| === Why a Common Glossary ===
| |
| | |
| The EGI Community is composed by a large number of heterogenous actors who contribute to providing or consuming services for e-Science. Policy makers produce policies and procedures that govern the EGI processes; dissemination experts write articles for communicating the progress and results in using or evolving EGI; end-users write papers on research results achieved through the infrastructure; technology providers report on the advancement of technology components that enable EGI to operate and so on.
| |
| | |
| From many parties, it has been often expressed the need to identify a common set of terms which definition is agreed and shared so to improve the understanding and consistency of documents. In the current scenario, several independent glossaries exist sometimes with not consisten definitions.
| |
| | |
| The goal of the EGI Glossary is to address this problem by identifying and maintaining a shared set of terms across all the functional areas of EGI in order to enable a consistent understanding and usage within a well-defined scope. The EGI Glossary is maintained by the [[GCG|EGI Glossary Coordination Group]] who collect feedback from the whole EGI community through the EGI policy boards.
| |
| | |
| This page contains the first version of the EGI Glossary of terms, still under discussion within the community. This draft builds on the work of the [https://documents.egi.eu/document/71 SPG Glossary], the [https://documents.egi.eu/document/31 Resource Centre OLA Glossary], a number of TCB terms, and try to leverage external glossaries such as [http://www.ggf.org/documents/GFD.181.pdf OGF PGI Glossary] and the [http://www.best-management-practice.com/gempdf/ITIL_Glossary_V3_1_24.pdf ITIL Glossary].
| |
| | |
| In its current version, the EGI Glossary aims at minimising the usage of the term "EGI" in the definitions following a requirement from SPG. The goal is to simplify the writing of policies and procedures that can be re-used by other e-infrastructures.
| |
| | |
| === How to Report your Feedback ===
| |
| | |
| Please, provide your feedback to the proposed terms and definitions to [http://www.egi.eu/about/people/Sergio_Andreozzi.html Sergio Andreozzi] (previous feedback is [[Glossary V1 Feedback|in this page]]).
| |
| | |
| === How to Reference ===
| |
| | |
| *EGI Glossary - latest version: http://wiki.egi.eu/wiki/Glossary
| |
| *EGI Glossary - Version 1: http://wiki.egi.eu/wiki/Glossary_V1
| |
| *A term definition in the latest EGI Glossary: http://wiki.egi.eu/wiki/Glossary#TERM_NAME
| |
| *A term definition in the EGI Glossary Version 1: http://wiki.egi.eu/wiki/Glossary_V1#TERM_NAME
| |
| | |
| === Terms and Definitions ===
| |
| | |
| *Where a definition of a term includes another term, those related terms are given initial capitals
| |
| *The form 'See also Term X, Term Y' is used at the end of a definition where an importan related term is not used with the text of the definition itself<br>
| |
| | |
| | |
| {| width="100%" border="1" cellpadding="3" cellspacing="0" class="wikitable sortable"
| |
| |+
| |
| === EGI Glossary ===
| |
| | |
| |-
| |
| ! style="width:300px" scope="col" | Term
| |
| ! align="center" scope="col" | Abbr.
| |
| ! scope="col" | Definition
| |
| |-
| |
| ! scope="row" | <div id="Accounting_Record">[[#Accounting_Record|Accounting Record]]</div>
| |
| |
| |
| | An entry in an accounting database identifying the quantitative usage of [[#Resource|Resources]] by [[#User|Users]].
| |
| |-
| |
| ! scope="row" | <div id="Acceptable_Use_Policy">[[#Acceptable_Use_Policy|Acceptable Use Policy]]</div>
| |
| | AUP
| |
| | A set of terms and conditions applicable to the [[#User|Users]] of an [[#IT_Infrastructure|IT Infrastructure]].
| |
| |-
| |
| ! scope="row" | <div id="Appliance">[[#Appliance|Appliance]]</div>
| |
| |
| |
| | The technical implementation of a [[#Capability|Capability]]. An Appliance may be delivered in a single, monolithic [[#Package|Package]], or it may be delivered as a set of components that are grouped into a set of [[#Package|Packages]]. In the latter case all packages must be installed to provide the complete Appliance.
| |
| |-
| |
| ! scope="row" | <div id="Application_Service_Provider">[[#Application_Service_Provider|Application Service Provider]]</div>
| |
| | ASP
| |
| | An external service provider that provides [[#IT_Service|IT Services]] using applications running at the Service Provider's premises. [[#Users|Users]] access the Applications by network connections to the Service Provider (''Source:'' ITIL)
| |
| |-
| |
| ! scope="row" | <div id="Business_Model">[[#Business_Model|Business Model]]</div>
| |
| |
| |
| | Describes the rationale of how an organisation creates, delivers, and captures value. The process of business model construction is part of business strategy. The term business model is used for a broad range of informal and formal descriptions to represent core aspects of a business, including purpose, offerings, strategies, infrastructure, organizational structures, trading practices, and operational processes and policies.
| |
| |-
| |
| ! scope="row" | <div id="Capability">[[#Capability|Capability]]</div>
| |
| |
| |
| | The ability of an [[#IT_Service|IT Service]] to carry out an activity. A capability may be 1) functional if providing an Activity for the direct benefit of the [[#User|User]]; 2) operational if providing an Activity for supporting the Operations of an [[#IT_Infrastructure|IT Infrastructure]]; 3) security if related to security aspects. A Capability may depend on others Capabilities. A Capability is defined and delivered by one or more Interfaces supported by one or more technology providers.
| |
| |-
| |
| ! scope="row" | <div id="Certified_Resource_Centre">[[#Certified_Resource_Centre|Certified Resource Centre]]</div>
| |
| | CRC
| |
| | A [[#Resource_Centre|Resource Centre]] that conforms to the requirements specified in the [[PROC09|Resource Centre Registration and Certification Procedure]].
| |
| |-
| |
| ! scope="row" | <div id="Contract">[[#Contract|Contract]]</div>
| |
| |
| |
| | A legally binding Agreement between two or more parties. (''Source:'' ITIL)<br>The rules and constraints description for interaction via the Interface associated with the Contract; a Contract represents the unit of service specification in the technology neutral architecture. (''Source:'' TMF)
| |
| |-
| |
| ! scope="row" | <div id="EGI.eu">[[#EGI.eu|EGI.eu]]</div>
| |
| |
| |
| | Organisation based in Amsterdam established to coordinate and manage [[#European_Grid_Infrastructure|the infrastructure (EGI)]] on behalf of its participants: [[#National_Grid_Initiative|National Grid Initiatives (NGIs)]] and [[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisations (EIROs)]].
| |
| |-
| |
| ! scope="row" | <div id="EGI-InSPIRE">[[#EGI-InSPIRE|EGI-InSPIRE]]</div>
| |
| |
| |
| | A four-year project, co-funded by the European Commission’s 7th Framework Programme (contract number: RI-261323), helping to establish a sustainable, reliable e-Infrastructure that can support researchers’ needs for large-scale data analysis.
| |
| |-
| |
| ! scope="row" | <div id="e-Infrastructure">[[#e-Infrastructure|e-Infrastructure]]</div>
| |
| |
| |
| | An [[#IT_Infrastructure|IT Infrastructure]] for instant access to data, remote instruments, "in silico" experimentation, as well as the setup of [[#Virtual_Research_Community|Virtual Research Communities]] and/or [[#Virtual_Organisation|Virtual Organisations]].
| |
| |-
| |
| ! scope="row" | <div id="European_Grid_Infrastructure">[[#European_Grid_Infrastructure|European Grid Infrastructure]]</div>
| |
| | EGI
| |
| | Federation of resource providers set up to deliver sustainable, integrated and secure computing services to European researchers and their international partners.
| |
| |-
| |
| ! scope="row" | <div id="European_Intergovernmental_Research_Organisation">[[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisation]]</div>
| |
| | EIRO
| |
| | European Intergovernmental scientific Research Organisation that have extensive expertise in the areas of basic research and the management of large, international infrastructures, facilities and research programmes.
| |
| |-
| |
| ! scope="row" | <div id="European_Research_Area">[[#European_Research_Area|European Research Area]]</div>
| |
| | ERA
| |
| | The ERA is composed of all research and development activities, programmes and policies in Europe which involve a transnational perspective. Together, they enable researchers, research institutions and businesses to increasingly circulate, compete and co-operate across borders.
| |
| |-
| |
| ! scope="row" | <div id="Federated_e-Infrastructure">[[#Federated_e-Infrastructure|Federated e-Infrastructure]]</div>
| |
| |
| |
| | An [[#e-Infrastructure|e-Infrastructure]] which is composed of autonomous (maintaining their own policies) e-Infrastructure providers.
| |
| |-
| |
| ! scope="row" | <div id="Grade_of_Service">[[#Grade_of_Service|Grade of Service]]</div>
| |
| | GoA
| |
| | The designed service quality, also known as guaranteed QoS, used as a comparison with delivered (measured) QoS. A Service Provider commits a particular GoS to their Customers and then the QoS is a measurement of what was actually delivered. (''Source'': TMF)
| |
| |-
| |
| ! scope="row" | <div id="Grid">[[#Grid|Grid]]</div>
| |
| |
| |
| | [[#IT_Infrastructure|IT Infrastructure]] that is concerned with the integration, virtualisation, and management of services and resources in a distributed, heterogeneous environment that supports collections of users and resources ([[#Virtual_Organisation|Virtual Organisations]]) across traditional administrative, trust and organisational boundaries (real organisations). (''Source: ''OGF GFD-I.181)
| |
| |-
| |
| ! scope="row" | <div id="Grid_Initiative">[[#Grid_Initiative|Grid Initiative]]</div>
| |
| | GI
| |
| | An approved body that provides grid computing services or represents grid providers in a region, country or group of countries. Grid Initiatives may be organized in larger bodies, creating a hierarchical structure, with primary GIs federated in secondary GIs etc. In Europe, the primary GIs are created at national level forming National Grid Initiatives (NGIs), and are federated in the European Grid Initiative (EGI.eu). The infrastructure and middleware supporting the GIs on all levels constitute a Grid. The GI is a Single Point of Contact for a VO, representing the Grid as a whole. The added value of a GI may range from a simple aggregation (GI as “mediator”) to full integration (GI as “service provider”) of the underlying resources.
| |
| |-
| |
| ! scope="row" | <div id="Incident">[[#Incident|Incident]]</div>
| |
| |
| |
| | Any event which is not part of the standard operation of a service and which causes or may cause an interruption to, or a reduction in, the quality of that service. (''Source: ''ISO 20000-1)<br>Problem Unknown underlying cause of one or more incidents. (''Source: ''ISO 20000-1)
| |
| |-
| |
| ! scope="row" | <div id="Interoperability">[[#Interoperability|Interoperability]]</div>
| |
| |
| |
| | Interoperability is the ability of systems, people and organisations to provide services to and accept services from other systems, people and organisations and to use the services so exchanged to enable them to operate effectively together
| |
| |-
| |
| ! scope="row" | <div id="IT_Capability">[[#IT_Capability|IT Capability]]</div>
| |
| |
| |
| | See [[#Capability|Capability]]
| |
| |-
| |
| ! scope="row" | <div id="IT_Infrastructure">[[#IT_Infrastructure|IT Infrastructure]]</div>
| |
| |
| |
| | All of the hardware, software, networks, facilities, etc. that are required to develop, test, deliver, monitor, control or support [[#IT_Service|IT Services]]. The term [[#IT_Infrastructure|IT Infrastructure]] includes all of the information technology but not the associated people, Processes and documentation. (''Source'': ITIL V3)
| |
| |-
| |
| ! scope="row" | <div id="IT_Service">[[#IT_Service|IT Service]]</div>
| |
| |
| |
| | A Service provided to one or more [[#User|Users]] by a [[#Resource_Centre|Resource Centre]] or a [[#Resource_Infrastructure_Provider|Resource Infrastructure Provider]]. An [[#IT_Service|IT Service]] is based on the use of Information Technology and supports the [[#User|User]] Business Processes. An [[#IT_Service|IT Service]] is made up from a combination of people, Processes and technology and should be defined in a [[#Service_Level_Agreement|Service Level Agreement]]. An IT Service provides one or more [[#IT_Capability|IT Capabilities]]. (''Source'': ITIL V3, adapted)
| |
| |-
| |
| ! scope="row" | <div id="Memorandum_of_Understanding">[[#Memorandum_of_Understanding|Memorandum of Understanding]]</div>
| |
| | MoU
| |
| | An agreement that clarifies the relationships, responsibilities and communication channels between two or more parties that may share services, clients, and resources. The MoU is used when both parties do not want to pursue a contract that is legally binding (generally). Formal contracts can be intimidating therefore MoUs are the better option for some communities. However, it can also be used to regulate the relationship between parties.
| |
| |-
| |
| ! scope="row" | <div id="National_Grid_Initiative">[[#National_Grid_Initiative|National Grid Initiative or Infrastructure]]</div>
| |
| | NGI
| |
| | National Grid Infrastructures are legal organisations that (a) have a mandate to represent their national Grid community in all matters falling within the scope of EGI.eu, and (b) are the only organisation having the mandate described in (a) for its country and thus provide a single contact point at the national level.
| |
| |-
| |
| ! scope="row" | <div id="Open_ICT_Ecosystem">[[#Open_ICT_Ecosystem|Open ICT Ecosystem]]</div>
| |
| |
| |
| | An ICT ecosystem is open when it is capable of incorporating and sustaining interoperability, collaborative development and transparency, while increasing capacities to create flexible, service-oriented ICT applications that can be taken apart and recombined to meet changing needs more efficiently and effectively.
| |
| |-
| |
| ! scope="row" | <div id="Open_Science">[[#Open_Science|Open Science]]</div>
| |
| |
| |
| | The idea that scientific knowledge of all kinds should be openly shared as early as is practical in the discovery process. Open science comprises areas such as: Transparency in experimental methodology, observation, and collection of data; Public availability and reusability of scientific data; Public accessibility and transparency of scientific communication; Use of web-based tools to facilitate scientific collaboration.
| |
| |-
| |
| ! scope="row" | <div id="Open_Standard">[[#Open_Standard|Open Standard]]</div>
| |
| |
| |
| | A standard is open if meets the following criteria: All stakeholders have the same possibility of contributing to the development of the specification and public review is part of the decision-making process; The specification is available for everybody to study; Intellectual property rights related to the specification are licensed on FRAND (Fair, Reasonable, and Non-Discriminatory) or royalty-free terms in a way that allows implementation in both proprietary and open source software.
| |
| |-
| |
| ! scope="row" | <div id="Operational_Level_Agreement">[[#Operational_Level_Agreement|Operational Level Agreement]]</div>
| |
| | OLA
| |
| | An Agreement between an IT Service Provider and another part of the same Organisation. An OLA supports the IT Service Provider’s delivery of [[#IT_Service|IT Services]] to Customers. The OLA defines the goods or Services to be provided and the responsibilities of both parties.
| |
| |-
| |
| ! scope="row" | <div id="Operations_Centre">[[#Operations_Centre|Operations Centre]]</div>
| |
| |
| |
| | A centre offering operations services on behalf of the [[#Resource_Infrastructure_Provider|Resource Infrastructure Provider]].
| |
| |-
| |
| ! scope="row" | <div id="Package">[[#Package|Package]]</div>
| |
| |
| |
| | A structured software unit suitable for automated installation on a computer. A Package may specify dependencies on other packages, so that either a specific version of that package, or a minimum version of that package may satisfy that dependency.
| |
| |-
| |
| ! scope="row" | <div id="Platform_Integrator">[[#Platform_Integrator|Platform Integrator]]</div>
| |
| |
| |
| | Platform Integrators bring together software components from different technology providers or use external services (e.g. from the Collaboration Platform) to meet the needs of a particular consuming research community.
| |
| |-
| |
| ! scope="row" | <div id="Platform_Operator">[[#Platform_Operator|Platform Operator]]</div>
| |
| |
| |
| | Platform Operators ensure that the services deployed as part of an infrastructure or community platform are operating effectively on the distributed resources for their consuming community.
| |
| |-
| |
| ! scope="row" | <div id="Policy">[[#Policy|Policy]]</div>
| |
| |
| |
| | Clear, formal and mandatory statement and position of general nature adopted by the IT Infrastructure governance bodies.
| |
| |-
| |
| ! scope="row" | <div id="Primary_Package">[[#Primary_Package|Primary Package]]</div>
| |
| |
| |
| | A Product consists of a well-defined set of specific packages, each in a specific version. Different versions (whether major, minor, or revision) of the same Product may share a subset of packages of the same version, that do not change between the compared versions.
| |
| |-
| |
| ! scope="row" | <div id="Procedure">[[#Procedure|Procedure]]</div>
| |
| |
| |
| | Step by step written and approved specification of how to complete a specific task or process.
| |
| |-
| |
| ! scope="row" | <div id="Product">[[#Product|Product]]</div>
| |
| |
| |
| | A solution delivered by Technology Providers to EGI and provides the functionality for one, sometimes more [[#Capability|Capabilities]] as one single, undividable unit. Consequently, a Product may comprise of one or more Appliances.
| |
| |-
| |
| ! scope="row" | <div id="Quality_of_Service">[[#Quality_of_Service|Quality of Service]]</div>
| |
| | QoS
| |
| | The collective effect of service performance that determine the degree of satisfaction of a user of the service. Note that the quality of service is characterized by the combined aspects of service support performance, service operability performance, service integrity and other factors specific to each service. (''Source'': TMF)
| |
| |-
| |
| ! scope="row" | <div id="Resource">[[#Resource|Resource]]</div>
| |
| |
| |
| | A physical or virtual entity that is consumed from an [[#e-Infrastructure|e-Infrastructure]] through [[#IT_Service|IT Services]].
| |
| |-
| |
| ! scope="row" | <div id="Resource_Centre">[[#Resource_Centre|Resource Centre]]</div>
| |
| | RC
| |
| | The smallest resource administration domain in an [[#e-Infrastructure|e-Infrastructure]]. It can be either localised or geographically distributed. It provides a minimum set of local or remote [[#IT_Service|IT Services]] compliant to well-defined [[#IT_Capability|IT Capabilities]] necessary to make resources accessible to [[#User|Users]]. Access is granted by exposing common interfaces to [[#User|Users]].
| |
| |-
| |
| ! scope="row" | <div id="Resource_Centre_Administrator">[[#Resource_Centre_Administrator|Resource Centre Administrator]]</div>
| |
| |
| |
| | An individual who is responsible for installing, operating, maintaining and supporting one or more resources or [[#IT_Service|IT Services]] in a [[#Resource_Centre|Resource Centre]].
| |
| |-
| |
| ! scope="row" | <div id="Resource_Centre_Operations_Manager">[[#Resource_Centre_Operations_Manager|Resource Centre Operations Manager]]</div>
| |
| |
| |
| | An individual who leads the Resource Centre operations, and is the official technical contact person in the connected organisation. He/she is locally supported by a team of Resource Centre administrators.
| |
| |-
| |
| ! scope="row" | <div id="Resource_Infrastructure">[[#Resource_Infrastructure|Resource Infrastructure]]</div>
| |
| | RI
| |
| | A Resource Infrastructure is a federation of [[#Resource_Centre|Resource Centres]].
| |
| |-
| |
| ! scope="row" | <div id="Resource_Infrastructure_Provider">[[#Resource_Infrastructure_Provider|Resource infrastructure Provider]]</div>
| |
| | RP
| |
| | The legal organisation responsible for any matter that concerns the respective [[#Resource_Infrastructure|Resource Infrastructure]]. It provides, manages and operates (directly or indirectly) all the operational services required to an agreed level of quality as required by the [[#Resource_Centre|Resource Centres]] and their user community. It holds the responsibility of integrating these operational services into EGI in order to enable uniform resource access and sharing for the benefit of their [[#User|Users]]. The Resource infrastructure Provider liaises locally with the Resource Centre Operations Managers, and represents the [[#Resource_Centre|Resource Centres]] at an international level. Examples of a Resource infrastructure Provider are the [[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisations(EIRO)]] and the [[#National_Grid_Initiative|National Grid Initiatives (NGIs)]]
| |
| |-
| |
| ! scope="row" | <div id="Service">[[#Service|Service]]</div>
| |
| |
| |
| | Means of delivering value to [[#User|Users]] by facilitating outcomes they want to achieve without the ownership of specific costs and risks (''Source'': ITIL V3, adapted)
| |
| |-
| |
| ! scope="row" | <div id="Service_Catalogue">[[#Service_Catalogue|Service Catalogue]]</div>
| |
| |
| |
| | A Document listing all IT Services, with summary information about their SLAs and Customers. The Service Catalogue is created and maintained by the IT Service Provider and is used by all IT Service Management Processes. (''Source'': ITIL)
| |
| |-
| |
| ! scope="row" | <div id="Service_Delivery">[[#Service_Delivery|Service Delivery]]</div>
| |
| |
| |
| | The core IT Service Management Processes that have a Tactical or Strategic focus. In ITIL these are Service Level Management and Capacity Management. Service Delivery is also used to mean the delivery of IT Services to Customers. (''Source'': ITIL)<br>The supplier activities necessary to provide the service. (''Source'': TMF)
| |
| |-
| |
| ! scope="row" | <div id="Service_Delivery_Management">[[#Service_Delivery_Management|Service Delivery Management]]</div>
| |
| | SDM
| |
| | Service Delivery Management provides guidelines for managing the delivery of SLA-aware IT services through their lifecycle including: planning; monitoring and reporting on capacity, availability, continuity, and security; managing changes and releases in a controlled manner; maintaining accurate information on the infrastructure and its configuration; and handling incidents and user requests, and resolving and avoiding problems.
| |
| |-
| |
| ! scope="row" | <div id="Service_Element">[[#Service_Element|Service Element]]</div>
| |
| |
| |
| | A service element comprises one or more network or service resources that are combined with other service elements to provide a service. (''Source'': TMF)
| |
| |-
| |
| ! scope="row" | <div id="Service_Instance">[[#Service_Instance|Service Instance]]</div>
| |
| |
| |
| | A service that has been instantiated for a Customer. (''Source'': TMF)
| |
| |-
| |
| ! scope="row" | <div id="Site">[[#Site|Site]]</div>
| |
| |
| |
| | See [[#Resource_Centre|Resource Centre]]
| |
| |-
| |
| ! scope="row" | <div id="Secondary_Package">[[#Secondary_Package|Secondary Package]]</div>
| |
| |
| |
| | A package that is resolved from dependency declarations within a [[#Package|Package]], that sources either from the Technology Provider's own Repository, or from any additional repository except OS distribution repositories. (Note: EPEL is an example of such a repository that is not an OS repository.)
| |
| |-
| |
| ! scope="row" | <div id="Service_Level_Agreement">[[#Service_Level_Agreement|Service Level Agreement]]</div>
| |
| | SLA
| |
| | An Agreement between an IT Service Provider and a Customer. The SLA describes the [[#IT_Service|IT Service]], documents Service Level Targets and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple [[#IT_Service|IT Services]] or multiple Customers.
| |
| |-
| |
| ! scope="row" | <div id="Service_Level_Management">[[#Service_Level_Management|Service Level Management]]</div>
| |
| | SLM
| |
| | The Process responsible for negotiating Service Level Agreements, and ensuring that these are met. SLM is responsible for ensuring that all IT Service Management Processes, Operational Level Agreements, and Underpinning Contracts, are appropriate for the agreed Service Level Targets. SLM monitors and reports on Service Levels, and holds regular Customer reviews. (''Source'': ITIL)
| |
| |-
| |
| ! scope="row" | <div id="Standard">[[#Standard|Standard]]</div>
| |
| |
| |
| | A document, established by consensus and approved by an SDO, which provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context. Compliance is not compulsory
| |
| |-
| |
| ! scope="row" | <div id="Standard_Organization_Body">[[#Standard_Organization_Body|Standard Organization Body]]</div>
| |
| | SDO
| |
| | A chartered organisation tasked with producing standards and specifications, according to specific, strictly defined requirements, procedures and rules.
| |
| Standards developing organisations include: 1) recognised standardisation bodies such as international standardisation committees such as the International Organisation for Standardisation (ISO), the three European Standard Organisations: the European Committee for Standardisation (CEN), the European Committee for Electrotechnical Standardisation (CENELEC) or the European Telecommunications Standards Institute (ETSI), national standardisation organisations such as ANSI; 2) fora and consortia initiatives for standardisation such as the Open Grid Forum (OGF) or the Organisation for the Advancement of Structured Information Standards (OASIS).
| |
| |-
| |
| ! scope="row" | <div id="UMD_Capability">[[#UMD_Capability|UMD Capability]]</div>
| |
| |
| |
| | An [[#IT_Capability|IT Capability]] defined in the [https://documents.egi.eu/document/272 UMD Roadmap].
| |
| |-
| |
| ! scope="row" | <div id="Unified_Middleware_Distribution">[[#Unified_Middleware_Distribution|Unified Middleware Distribution]]</div>
| |
| | UMD
| |
| | The integrated set of software components contributed by technology providers and packaged for deployment as production-quality services in EGI.
| |
| |-
| |
| ! scope="row" | <div id="User">[[#User|User]]</div>
| |
| |
| |
| | A person who uses the [[#IT_Service|IT Service]] on day-to-day basis. (''Source'': ITIL V3)
| |
| |-
| |
| ! scope="row" | <div id="Value_Propositon">[[#Value_Propositon|Value Propositon]]</div>
| |
| |
| |
| | A promise of value to be delivered and a belief from the client of value that will be experienced. A value proposition can apply to an entire organisation, or parts thereof, or client accounts, or products or services.
| |
| |-
| |
| ! scope="row" | <div id="Virtual_Organisation">[[#Virtual_Organisation|Virtual Organisation]]</div>
| |
| | VO
| |
| | A group of people (e.g. scientists, researchers) with common interests and requirements, who need to work collaboratively and/or share resources (e.g. data, software, expertise, CPU, storage space) regardless of geographical location. They join a VO in order to access resources to meet these needs, after agreeing to a set of rules and [[#Policy|Policies]] that govern their access and security rights (to users, resources and data).
| |
| |-
| |
| ! scope="row" | <div id="Virtual_Organisation_Manager">[[#Virtual_Organisation_Manager|Virtual Organisation Manager]]</div>
| |
| |
| |
| | An individual responsible for the membership registry of a [[#Virtual_Organisation|VO]] including its accuracy and integrity.
| |
| |-
| |
| ! scope="row" | <div id="Virtual_Research_Community">[[#Virtual_Research_Community|Virtual Research Community]]</div>
| |
| | VRC
| |
| | A group of large-scale research collaborations, or a number of separate [[#Virtual_Organisation|VOs]] grouped according to research domain or computational technique. The group shares information and experience in achieving their goals through the usage of an [[#e-Infrastructure|e-Infrastructure]] (e.g., best practices, applications, training material).
| |
| |}
| |
| | |
| === Concept Map ===
| |
| | |
| [[Image:EGI-Glossary.jpg|1400px|EGI Glossary]]
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.