1 / 5

Guidelines for Collaborative Project Groups in CLARIN-NL/VL ISOcat Workshop

This document outlines the procedure for participating in the CLARIN-NL/VL group for project collaboration. It details the steps for becoming a member, creating a project group, adding members, and developing Data Categories (DCs) within ISOcat. Members are encouraged to share and edit shared DCs while respecting ownership and permissions. The document also emphasizes the importance of project representation in the group, annotating resources with selected Data Categories, and the need for maturity review of DCs before public release.

kinsey
Télécharger la présentation

Guidelines for Collaborative Project Groups in CLARIN-NL/VL ISOcat Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CLARIN-NL/VL procedure CLARIN-NL ISOcat workshop

  2. Project workspace • Become member of the CLARIN-NL/VL group (You will be invited to join) • Create a group for your project • add members related to your project • Create one or more DCSs • add existing and usable DCs • preferably from the CLARIN-NL/VL view • add new DCs • (When creating a DC => follow the do’s and don’ts guidelines!) cf. CLARIN-NL/VL FORUM CLARIN-NL ISOcat workshop

  3. Share the DCSs with • the project group • can edit shared DCs en DCSs • the CLARIN-NL/VL group • can also edit, so ask permission (!) if you want to change something in a DC owned by another project • changes are logged and attributed • Make one or more DCSs public when the group and Ineke finds the DCs mature (not beforehand!) • the project group becomes visible in the public part of ISOcat • also make the DCs public CLARIN-NL ISOcat workshop

  4. CLARIN-NL/VL workspace • Every project should have a representative in the CLARIN-NL/VL group • this representative should own the project DCS so (s)he can share it with the CLARIN-NL/VL group • Once DCs are mature for CLARIN-NL/VL use add them to the admin-proposed DCS • this is still in the private/shared part of ISOcat • Ineke will • review the (new) DCs • add them to CLARIN-NL/VL thematic DCSs • If a DC is changed add them to the admin-changed DCS • Ineke will review the changed DCs CLARIN-NL ISOcat workshop

  5. Beyond ISOcat • Annotate your project resources with the selected/created Data Categories • preferably annotate a schema • to be stored in SCHEMAcat (under construction) • use @dcr:datcat • for XML (schemata) • for EBNF grammars • ... (contact isocat@mpi.nl) • Remember (ontological) relationships between the selected/created Data Categories and other Data Categories/concepts • to be stored in RELcat (under construction) • there is a spreadsheet template CLARIN-NL ISOcat workshop

More Related