CLARIN NL Wiki

Welcome to the CLARIN-NL Wiki

This is a copy of the information available once available at the CLARIN NL helpdesk
In this section, generic information on Clarin topics can be found. Currently, collections of links to relevant documentation are presented with a short description of its content. This information is presented in chapters that reflect the division in Clarin topics made elsewhere: You can also look for the answers to your questions in our FAQ's.

Metadata

  • Metadata Infrastructure for Language Resources and Technology (pdf) (2009-02-04 - Version 5)
    This document gives an overview about how metadata descriptions are used until now, what the deficits of the current infrastructures are and which lessons we as community learned from about a decade of experience. Based on this the requirements for a new CLARIN approach are being worked out. This document will be discussed in the appropriate working groups and in the Executive Board. It will be subject of regular adaptations dependent on the progress in CLARIN.
  • Best Practice Guide for using CLARIN metadata components (2010)
    The Dutch CLARIN project “Creating and using CLARIN metadata components” was the first to actually test the use of components and to try to create metadata descriptions for resources available in two Dutch language resource centers: the Institute for Dutch Lexicology (INL) and the Meertens Institute. This “Best Practice Guide” is the result of this project. It will however in the future be extended with new experiences gained by new projects that will make use of the CMDI.
  • Component Metadata (2009-02)
    In this A4 shortguide, some introductory information is provided on Component Metadata following the generic shortguide layout of "What is it?", "What is it for?", "Who can use it?", "When can it be used?" and "How does it work?".
  • Metadata and DCR (2010-03-25)
    In this presentation given at an ISOcat workshop in Utrecht, shortcomings were discussed in "traditional metadata" and benefits of "component metadata". To guarantee interoperability while using different components, data categories are discussed. Furthermore, a bigger picture is provided through some diagrams and finally, an overview of building and using components in practice is provided.
  • Creating & Testing CLARIN Metadata Components - A CLARIN-NL project (2010-05-18)
    Publication in Language Resources and Evaluation. It features the topics "What is CMDI?", "What is the goal of our project?", "How to go from a resource to harvestable metadata?" and "Findings of the project and future challenges". The presentation on this project, held during LREC 2010, can be found here.
^ UP

Arbil

Arbil can be found here.
  • ARBIL (2009-11)
    This A4 guide features practical information on: "1. Starting ARBIL", "2. Getting your metadata"", "3. Changing your metadata"and "4. Saving and exporting your metadata".
  • Arbil User Guide (2010-02-17)
    This extensive user guide contains user oriented information on Arbil and its usage, featuring lots of details and screenshots.
  • Arbil for creating IMDI-corpora metadata (2009-12)
    This is the official Arbil manual, featuring lots of details and screenshots.
  • ARBIL, the CMDI metadata editor (2010-05-26)
    In this document, information on Arbil and its features is provided and visualized through screenshots. In more detail, the following topics are addressed in this document: "generic information on Arbil and its history", "a description of Arbil as an XML editor", "the specialized functions of Arbil", "profiles in Arbil", "the construction of metadata files", "entering and organizing data", "searching and visualizing the data", ​''the Arbil forum'' and "installing Arbil".
  • Arbil Presentation (2009-10-15)
    This is a nice presentation of Arbil, featuring 20 sheets of information and many screenshots.
^ UP

Component Registry

The Component Registry can be found here.
  • A Data Category Registry- and Component-based Metadata Framework (2010-05-19)
    We describe our computer-supported framework to overcome the rule of metadata schism. It combines the use of controlled vocabularies, managed by a data category registry, with a component-based approach, where the categories can be combined to yield complex metadata structures. A metadata scheme devised in this way will thus be grounded in its use of categories. Schema designers will profit from existing prefabricated larger building blocks, motivating re-use at a larger scale. The common base of any two metadata schemes within this framework will solve, at least to a good extent, the semantic interoperability problem, and consequently, further promote systematic use of metadata for existing resources and tools to be shared.
  • Component Registry and Browser Reference Manual. (d.d. unknown)
    In this manual, features of the Component Registry are highlighted, providing information and screenshots of them. The following features are covered in this manner: "1) Register and store CMDI Components/Profiles?", "2) Enable a user to browse the registered Components/Profiles?" and "3) Enable a user to edit and create Components/Profiles?".
  • CMDI Component Registry (2010)
    This is a presentation of the Component Registry, full of visual information about its characteristics.
^ UP

ISOcat and OpenSKOS

ISOcat was a web-based implementation to store and make accessible concepts (a concept registry), more specifically data categories, that are relevant for the CLARIN infrastructure and for encoding linguistic phenomena. ISOcat has been succeeded by OpenSKOS. ^ UP

PID's

  • EPIC home (regularly updated)
    Since the beginning of 2009 GWDG runs on behalf of the Max Planck Society a PID service, based on the handle system (TM, ​http://www.handle.net/ ), for the allocation and resolution of persistent identifiers. Together with other European partners a consortium was build to provide this services to the European research community.
  • Persistent Identifier Service (2009-02)
    In this A4 shortguide, some introductory information is provided on the Persistent Identifier Service following the generic shortguide layout of "What is it?", "What is it for?", "Who can use it?", "When can it be used?" and "How does it work?".
  • Federation Foundation Persistent and unique Identifiers (2009-02-04 - Version 5)
    This document describes the goals and requirements of a registration and resolution system for persistent and unique resource identifiers that could be used by all CLARIN members and beyond, i.e. a functioning system could be used by other communities as well and there is great interest. Stepwise all CLARIN centers would need to introduce PIDs to come to a proper landscape of resources where various instances can and will be created at various places. This document will be discussed in the appropriate working groups and in the Executive Board. It will be subject of regular adaptations dependent on the progress in CLARIN.
  • Persistent Identifiers for Language Resources (2009-06)
    This presentation was given at the CLARIN Info Day. It discusses the questions "Why the Handle System?" and "What does it mean?" and gives examples.
^ UP

Webservices

  • Requirements Specification Web Services and Workflow Systems (2010-01-12 - Version 2)
    This document describes the goals and requirements of web services and workflow systems that could be used by all CLARIN members and beyond, i.e. a functioning system could be used by other communities as well. Stepwise all CLARIN centers would need to introduce these requirements in their operational environment to come to a proper landscape of resources, services and tools where various instances can and will be created/operated at various places. This document will be discussed in the appropriate working groups and in the Executive Board. It will be subject of regular adaptations dependent on the progress in CLARIN.
  • Service Oriented Infrastructure (2010-02)
    In this A4 shortguide, some introductory information is provided on the Service Oriented Infrastructure following the generic shortguide layout of "What is it?", "What is it for?", "Who can use it?", "When can it be used?" and "How does it work?".
  • Web Services Interoperability (2010-02)
    In this A4 shortguide, some introductory information is provided on Web Services Interoperability following the generic shortguide layout.
  • CLARIN web services and workflow (d.d. unknown)
    This presentation covers topics like the registration and workflow of webservices, the architecture of webservices and formats and the process of standardization.
  • CLAM
    This webpage features information on CLAM (Computational Linguistics Application Mediator). CLAM allows you to quickly and transparently transform your Natural Language Processing application into a RESTful webservice, with which both human end-users as well as automated clients can interact.
^ UP

Formats and standards

  • Stages of the development of International Standards (updated regularly)
    This official ISO website describes the stages involved in standardization.
  • Standards for LRT (2009-01)
    This document is the basis for a joint web-site with recommendations for CLARIN. Each known name of a standard or best-practice guideline will be commented along a few criteria.
  • Standards and Best Practices(2009-02)
    In this A4 shortguide, some introductory information is provided on Standards and Best Practices following the generic shortguide layout.
  • Standards for Text Encoding (2009-05)
    In this A4 shortguide, some introductory information is provided on Standards for Text Encoding following the generic shortguide layout.
  • Formats, interoperability and standards (d.d. unknown)
    This presentation covers format interoperability, the process of standardization, pivot formats and community practices.
^ UP

AAI

  • Federation Foundation for Language Resource and Technology (2009-02-04 - Version 7)
    This document describes the requirements for the Language Resource and Technology Federation that CLARIN wants to build up based on a stable network of centers as described in CLARIN-1-2008 and CLARIN- 3-2008. It is also referring to a detailed discussion of possible solutions for persistent identifiers as described in CLARIN-2/2008. This document will be discussed in the appropriate working groups and in the Executive Board. It will be subject of regular adaptations dependent on the progress in CLARIN. In chapter 1 it is explained why federation technology is an issue for a research infrastructure as CLARIN. In chapter 2 we will discuss various models of federations, distinguish identity and service provider federations and describe a few pillars federations need to have. In chapter 3 we will describe the technologies required to implement a CLARIN federation and in chapter 4 the major middleware components are introduced to establish a distributed authentication and authorization domain. In chapter 5 we summarize the requirements relevant for CLARIN and in chapter 6 we outline the procedural approach.
  • CLARIN SERVICE PROVIDER FEDERATION START-UP AGREEMENT (d.d. unknown)
    This is the formal start-up agreement for the Clarin service provider federation.
  • Authorization and Authentication Infrastructure (2009-07-01)
    This presentation was held at the CLARIN-NL Info Session in Nijmegen. It features "CLARIN and the holy grail", "Traditional Federations", "AAI prototype" and "Planning".
  • Shibboleth home (updated regularly) This is the homepage of Shibboleth 2, a community-maintained repository for deployment, configuration, and production information. Shibboleth allows users to securely send trusted information about themselves to remote resources. This information may then be used for authentication, authorization, content personalization, and enabling single sign-on across a broad range of services from many different providers.
  • SWITCHaai – the key that connects students and the university (updated regularly)
    This is a web page where information on AAI is offered in several layers of complexity. Very useful here are the simple, medium and expert demo that are offered ​here.
  • AAI > Shibboleth (updated regularly)
    This is a web page in Dutch, where information on AAI is offered. In one of its sub pages (​here), a nice diagram is presented to visualize the process of accessing a shibbolized service. Some of this information in English can be found in a presentation (​here).
^ UP

CLARIN complatible

  • What does the term 'CLARIN compatible' mean? (Oct 2013)
    This document describes the meaning of the term “CLARIN-compatible” when applied to resources (data and software). The focus is on the situation in the Netherlands.
^ UP