META-SHARE Members
All organisations wishing to become META-SHARE members, by signing the META-SHARE Memorandum of Understanding (MoU) undertake the following obligations:
- to follow the META-SHARE metadata schema, as defined in the META-SHARE Metadata specifications document;
- to clear all rights before conferring an LR to the network;
- to store the LRs and metadata in their repositories OR use one of the META-SHARE hosting Repositories;
- to maintain an inventory (a local inventory) with all the metadata records of their LR OR use one of the META-SHARE hosting Repositories;
- to keep identifiers for all their LRs;
- to adhere to the META-SHARE Notice and Take Down policy
- to export the metadata records of their LRs and allow their harvesting and synchronization by the META-SHARE Managing Nodes
Members can:
- search the central inventory using multifaceted search facilities;
- access the actual resources by visiting the local and/or hosting Repositories for browsing and downloading them;
- get information about the usage of specific resources, their relation (e.g. compatibility, suitability, etc) to other resources as well as recommendations;
- get statistics on number of downloads, types of consumers, etc.
META-SHARE Repositories
META-SHARE Repositories are set up, operated and maintained by META-SHARE Members, acting as META-SHARE Repository Service Providers. META-SHARE Repositories can have a local or hosting (non-local) role.
Local repositories are set up and maintained by organisations participating in the META-SHARE network, storing their own resources.
Hosting repositories are also set up and maintained by organisations participating in the META-SHARE network acting as storage and documentation facilities for resources either developed in organisations not wishing to set up their own repository, or donated or considered orphan resources, i.e. resources without an owner. A hosting repository may also store its own resources.
Every LR in META-SHARE has to be primarily assigned to one of the network's repositories, with the member maintaining that repository undertaking the curation of the resource.
META-SHARE Members maintaining repositories are responsible for providing to the Managing Nodes all the information necessary for them to fulfill their mission.
META-SHARE Members depositing their language resources to a META-SHARE hosting repository will take all reasonable steps so that the META-SHARE Managing Nodes and repositories are able to perform their respective tasks and obligations.
META-SHARE Managing Nodes: Core Service and User Support Service Providers
A number of members with certain technical and organisational characteristics undertake the role of META-SHARE Managing Node acting as Core Service and User Support Service Providers with the obligation to provide one or more of the Core Services critical to the whole of the META-SHARE network.
META-SHARE Managing Nodes harvest and store metadata records from the META-SHARE Nodes of the entire META-SHARE Network. META-SHARE Managing Nodes share metadata, create, host and maintain a central inventory which includes metadata-based descriptions of all language resources available in the distributed network. Each META-SHARE Managing Node effectively hosts a copy of the central inventory.
META-SHARE Members meeting the organizational and technical standards necessary to provide Core Services and User Support Services can be invited and introduced as new Managing Nodes, in accordance to the procedures of the META-SHARE network.
META-SHARE Managing Nodes do not have any additional privileges with respect to access to LRs.
The following Members initially assume the role of META-SHARE Managing Node and act as Core Service and User Support Service Providers: CNR, DFKI, ELDA, FBK, ILSP
META-SHARE Core Services
The following services are considered as Core Services:
- Metadata and other data harvesting and synchronisation
- User and repository registration, authentication and authorisation
- Search, browsing and viewing
- Uploading and downloading of language resources
- Documentation of language resources
- Reporting on the use of language resources
- (Electronic) licensing
- Billing and payment (available in the future)
META-SHARE User Support Services
The following services are considered as User Support Services offered to META-SHARE Members:
- META-SHARE User Forum enabling META-SHARE Members to ask questions, get and view answers to questions.
- META-SHARE Knowledge Base providing information about the use of META-SHARE and its components and services in a structured way
- Legal helpdesk enabling META-SHARE Members to ask questions concerning the use of licences, rights of use, IPR issues, etc. - [javascript protected email address];
- Technical helpdesk enabling META-SHARE Members to ask questions concerning the META-SHARE software platform installation and use - [javascript protected email address];
- Metadata helpdesk enabling META-SHARE Members to ask questions concerning the META-SHARE metadata based LR documentation - [javascript protected email address].
LR Sharing within the META-SHARE Network
All META-SHARE members have full access to the META-SHARE infrastructure and the META-SHARE Commons licensed LRs for as long as they retain their membership status, as well as all other LRs in accordance to the LRs relevant licensing terms.
META-SHARE metadata are licenced under the Creative Commons Attribution Unported (CC-BY) version 3.0 or higher, or the EU Open Metadata Licence. All META-SHARE members and associate members are obliged to allow the harvesting of their meta-data.
META-SHARE members are encouraged, when they publish or distribute a Resource or any Derivative, to redeposit the Derivative work in the META-SHARE network.
LRs available under a licence allowing redistribution may be replicated and flow in the META-SHARE network according to the terms and conditions specified in the respective licence.
Members maintaining repositories are responsible for all LRs entering the META-SHARE network through their repositories:
- If the LR comes with a 3rd party licence, this member is responsible for properly documenting the licence in the metadata and ensuring its terms and conditions are clearly available to all members of the network;
- If the LR comes with a Share-alike licence, this member should take all necessary and reasonable measures, so that any subsequent derivative works and their authors may be identified;
- If this member has all IPR over the LR, then this member is encouraged to use one of the licences recommended by META-SHARE, i.e. a Creative Commons (CC), or a CC-compatible, licence, or a META-SHARE Commons, or a META-SHARE No Redistribution licence, or an Open Source Software licence.
Licensing LRs through META-SHARE
Any grant of access to LRs through META-SHARE should include not only the right to read the relevant content but also to allow transformative uses, dissemination and distribution of such resources and their derivatives, according to the needs and policies of LR owners and users. To limit the complexity of licensing, a range of recommended license setups are provided by META-SHARE in the form of templates or ready-made licences for the members to choose from.
The META-SHARE model licensing scheme, with a firm orientation towards the creation of an openness culture and the relevant ecosystem for LRs, is organised on the following axes, further described in the paragraphs to follow:
- Creative Commons licences (starting with Creative Commons Zero (CC-0) and all possible combinations along the CC differentiation of rights of use) are the first level of legal machinery applied.
- A second layer includes META-SHARE Commons Licences, a fully developed CC-based licensing tool that allows META-SHARE members and Extraneous Depositors to make their resources available to other network members only.
- The third legal layer is a set of licenses that allow use and exploitation of the Resources while permitting the LR Owner to have full control over the Resource distribution. These “No Redistribution” licences will effectively help get “closed” resources safely out to the community. These licenses also come with a Commercial flavour and are accompanied by their for-a-fee counterparts.
- Software tools and network services are either provided though one of the standard Open Source licenses or under a custom commercial license. Open Source Licenses proposed by META-SHARE include BSD, GPL, LGPL, Apache and AGPL. Other open licences are not excluded, but LR owners are being advised to always keep in mind certain selection criteria that will allow their LRs to be legally easy and straightforward to share.
These ready-to-use licensing schemes are as quick and easy to apply as possible, in particular for new resources. A META-SHARE helpdesk facility ([javascript protected email address]