Navigation path

Asset Description Metadata Schema (ADMS)

(
 
)
3.59/5 | 17 votes
Editor's choice

ADMS: Working Group Virtual Meeting 2011.11.29

(
 
)
1/5 | 1 votes |

Organisation

Tuesday 29 November 2011, 15:00-17:00 CET (UTC+1) (world clock)
Audio connection: Dial Belgium (toll) +32 (0)24015454 Participant PIN: 87198974#
Web connectionhttps://www.anywhereconference.com Web Login: 105379409 Participant PIN: 87198974#

Click here for further instructions on using the conference system.

Agenda

Chair: João Rodrigues Frade
European Commission: Vassilios Peristeras
Scribe: Débora Di Gaciamo
Editor: Makx Dekkers

Agenda Item Owner Subject
0 All from 14:45 conference open for participants to connect and get Web and audio connections set up
1 Joao Roll call, introduction by participants, agreement of agenda,
2 Makx Adoption of minutes of 9 November call  
3 Joao Organisational issues:
  • ISACV-29: Present the formalized statements about IPR, for both the final work and the contributions. 

    Status: In process. 

    Proposed resolution: Retain issue until final proposal received (João).
4

Makx

Use cases:

  • ISACV-61: To provide feedback on use cases
  • ISACV-85: Add EXPLORE user task
  • ISACV-86: List Status in the high importance properties for select use case
  • ISACV-88: Raise the level of importance of the attribute "alternative title" for the finding task to highly important 



    For all issues: 

    Status: In process 

    Proposed resolution: Revise as proposed (Stijn), then close issues. 
5

Makx

Asset type:

  • ISACV-19: Include UML Diagrams in the types
  • ISACV-21: Metadata and Reference Data as first level of taxonomy
  • ISACV-23: Structure asset types around policy products
  • ISACV-24: Ontology libraries, classifications and Creative Commons licenses as asset types
  • ISACV-25: Purpose of taxonomy: a) regulate asset types; b) facilitate search & discovery of assets; c) produce statistics; d) enable automated processing
  • ISACV-26: Can we do with comprehensive list "set in stone", or should it be an open (extensible) list?
  • ISACV-27: Make sure that there is a one-to-one mapping between the ADMS asset types and types in existing repositories
  • ISACV-47: Decide on proposed matrix of asset types
  • ISACV-65: To challenge the list of asset types, hereby concentrating on the semantic layer
  • ISACV-77: Add holders of others that do not belong to the specified types
  • ISACV-95: Maybe Asset types in the table are not a controlled vocabulary of asset types yet

For all issues:  

Status: Discussion not finalised yet, main outstanding issue  

Proposed resolution: Close all issues, create new issue “Verify list of Asset Types in mapping exercise and public comment”, to be revisited in February 2012 after public comment period in January 2012.

6 Makx

ADMS Conceptual Model:

  • ISACV-62: To create new version of ADMS Conceptual model without namespaces. 

    Status: Done. 

    Resolution: Close issue.
  • ISACV-69: To share a sufficiently stable version of the ADMS with indication of what are the core concepts, properties, and relationships. 

    Status: Done. 

    Resolution: Close issue.
7 Makx

Entities/classes:

  • ISACV-3: adms:Asset as subclass of a DataSeries class 

    Status: Several opinions, no clear consensus. 

    Proposed resolution: Drop issue.
  • ISACV-74: ADMS Asset similar to the notion "dataset series" 

    Status: Several opinions, no clear consensus. 

    Proposed resolution: Drop issue.
  • ISACV-79: Maybe the whole resource type is un-applicable? 

    Status: Various comments, emerging consensus that this entity is unnecessary.

    Proposed resolution: Remove entity Resource type (Makx).
  • ISACV-94: Keep adms:subject (or dc:subject) as a relationship 

    Proposed solution: Keep Subject relationship, close issue.
  • ISACV-76: What does "Interoperability Level" mean? 

    Proposed solution: Include short summary of interoperability levels with reference to EIFv2 (Makx), then close issue.
  • ISACV-75: Revise definitions of controlled vocabularies, taxonomies, thesauri and ontologies 

    Proposed solution: Replace text with text proposed by Marcia Zeng (Makx), then close issue.
  • ISACV-78: What is the geographic reference? 

    Proposed solution: Add examples e.g. gazetteers, Geonames, OpenStreetMap (Makx), then close issue.
8 Makx Properties and relationships:
  • ISACV-48: Decide on ADMS properties related to asset type 

    Status: Currently three relationships (Asset type, Interoperability level, Resource type). According to issue 79, emerging consensus that relationship Resource type is unnecessary. 

    Proposed resolution: Remove relationship Resource type (Makx)
  • ISACV-50: Decide on relationship between asset and its documentation 

    Status: Currently two entities (Documentation and Web page) and two relationships (Documentation and Web page). 

    Proposed resolution: Remove entity Web page and relationship Web page (Makx)
  • ISACV-60: To include property to refer to concepts inside the asset 

    Status: Relationship Included item was added in second WG draft. 

    Proposed resolution: Close issue
  • ISACV-66: To add link to last version to the relationships of an Asset 

    Status: Relationship Last version was added in second WG draft. 

    Proposed resolution: Close issue (but see editorial comment issue 91 proposing to change name of relationship to Current version)
9 Makx Cardinalities:
  • ISACV-59: Share an example from the XRepository of a semantic asset that is of multiple types
  • ISACV-73: Change cardinality of Asset Type 

    Status: Agreed at 9 November meeting. 

    Proposed resolution: Change cardinality in final draft to “at least one” (Makx).
10 Makx Mapping and examples:
  • ISACV-58: Update the mapping template and to invite repository owners to take part in the mapping exercise
  • ISACV-63: To verify in the mapping exercise that everything the existing repositories need is available in the model 



    For all issues: 

    Status: In process 

    Proposed resolution: Close issues; they will be part of the new issue “Verify list of Asset Types in mapping exercise and public comment”, to be revisited in February 2012 after public comment period in January 2012.
11 Phil Selection of namespaces for RDF schema:
  • ISACV-4: Available format could be instance of dcterms:FileFormat class
  • ISACV-51: Use dcat:Catalog for adms:Repository
  • ISACV-52: Use dcat:Distribution for adms:Release
  • ISACV-64: To investigate options for FileFormat / MediaType
  • ISACV-53: Use dcat:keyword for adms:keyword
  • ISACV-54: Make URI property lowercase: adms:uri
  • ISACV-55: Range of dcterms:publisher should be dcterms:Agent 



    For issues 4, 51, 52, 64, 53, 54, 55: 

    Status: Being processed in drafting of schemas 

    Proposed resolution: Close issues, move to small task group as part of two new issues “Create RDF schema” and “Create XML schema” with scheduled completion in early February 2012. 

     
  • ISACV-68: To see how the name space document of the ADMS will be published 

    Status: In process 

    Proposed solution: Retain issue until final proposal received (Phil).
12 Joao Setting up task groups for RDF and XML schemas
13 Makx Editorial issues:
  • ISACV-72: Revise quote from EIFv1 

    Proposed solution: Replace by quote from EIFv2 (Makx), then close issue.
  • ISACV-87: Indicating levels of importance with numbers "1-3" or with "A-C" rather than with symbols 

    Proposed solution: Revise as proposed (Stijn), then close issue.
  • ISACV-84: Rework and enrich semantic statements (definitions) for adms attributes 

    Proposed resolution: Close issue, converted to issues 89 and 90
  • ISACV-89: Replace "implementation" by "version/representation" for Release 

    Proposed solution: Revise as proposed (Makx), then close issue.
  • ISACV-90: Remove "that is being described" from definition of Asset type 

    Proposed solution: Revise as proposed (Makx), then close issue.
  • ISACV-91: Change the name of relations between two Assets from "Last version" into "Current version" 

    Proposed solution: Revise as proposed (Makx), then close issue.
  • ISACV-92: Re-name adms:Concept to something else 

    Proposed solution: Rename entity Concept to IncludedItem (Makx), then close issue.
  • ISACV-93: Re-name adms:Subject as skos:Concept 

    Proposed solution: Retain entity Subject but map to rdfs:Resource (as subject can be anything, not just things that are in class skos:Concept (Makx), then close issue.
  • ISACV-81: Edit section on subject vocabularies 

    Proposed solution: Revise as proposed (Makx), then close issue.
  • ISACV-82: Replace reference to RFC4646 by RFC5646 

    Proposed solution: Revise as proposed (Makx), then close issue.
  • ISACV-70: Correct additional info of Oriol Bausà Peris 

    Proposed solution: Revise as proposed (Makx), then close issue.
14 Vassilios Liaison:
  • ISACV-67: To connect with the Publications Office 

    Status: In process 

    Proposed solution: Vassilios to report, then close issue.
15 Joao Wrap-up, actions

 

Meeting Minutes

ADMS WG Virtual Meeting 2011.11.29 - Minutes - v0.03.pdf

Other documents

D1.1 ADMS Use Case_v0.04_draft.pdf

D1.1-ADMS UML Diagram-v0.06.pdf

ADMS_Section_5_Conceptual_model_v0.03draft3.pdf

 

Information

Publication date:
29 November 2011
Nature of documentation:
Conference-seminar-meeting proceeding
License of document:
Other licenses
Geographic coverage:
Europe
Themes:
Communications
Author:
ADMS

Related Content

Subscribe to newsletter

You will receive news and links to the most interesting developments...