This document discusses the development of a metadata profile for protected sites within the NatureSDI+ project. It describes work done so far to draft the metadata specification based on INSPIRE and other requirements. It outlines the current steps, which include reviewing and discussing the draft, analyzing new metadata elements from the Protected Sites data specification version 3.0, and conducting an initial analysis of metadata proposed for Annex III datasets. The document concludes by outlining plans to finalize the metadata specification draft by the next project milestone.
ISO Metadata Improvements - Questions and AnswersTed Habermann
The ISO Standards for describing geospatial data, services, and other resources are changing. These slides describe a few of these changes in terms of documentation needs and how the new standards address these needs. I talked with these slides at a recent webinar that is available at https://www.youtube.com/watch?v=un-PtJLclIM&feature=youtu.be
Part 4 of tutorials at DC2008, Berlin. (International Conference on Dublin Core and Metadata Applications). See also part 1-3 by Jane Greenberg, Pete Johnston, and Mikael Nilsson on DC history, concepts, and other schemas. This part focuses on practical issues.
Presentation by Matt Crundon, Legrand Electric Ltd at the BIM for Manufacturers: Help with the Journey seminar on 28 July 2015
More information at http://bim4m2.co.uk/
ISO Metadata Improvements - Questions and AnswersTed Habermann
The ISO Standards for describing geospatial data, services, and other resources are changing. These slides describe a few of these changes in terms of documentation needs and how the new standards address these needs. I talked with these slides at a recent webinar that is available at https://www.youtube.com/watch?v=un-PtJLclIM&feature=youtu.be
Part 4 of tutorials at DC2008, Berlin. (International Conference on Dublin Core and Metadata Applications). See also part 1-3 by Jane Greenberg, Pete Johnston, and Mikael Nilsson on DC history, concepts, and other schemas. This part focuses on practical issues.
Presentation by Matt Crundon, Legrand Electric Ltd at the BIM for Manufacturers: Help with the Journey seminar on 28 July 2015
More information at http://bim4m2.co.uk/
Over the last 10 years, the status of educational metadata, specifically
as they relate to learning objects, has changed radically. In the heady
days of the turn of the millennium, learning objects and their metadata
were seen as being destined to forever change the shape and form of
learning; by 2007, this approach has been derisively labeled "industrialist", and said to be quickly running "out of steam."
Given such drastic changes, how are metadata to be understood in the context
of different and emerging approaches to online learning resources, above
all those labelled 'open'? This question will be the focus of this presentation by Dr. Norm Friesen, Canada Research Chair in E-Learning Practices at Thompson Rivers University and Director of the CanCore
Initiative. Dr. Friesen will consider a number of alternatives to "learning object metadata." Dr. Friesen will conclude his
presentation by discussing an alternative that incorporates both high tech and ow tech approaches --one that is currently under
development as a multi-part international standard under the auspices of ISO (the
International Organization for Standardization).
Metadata management for data storage spaces :
INDEXATOR is a metadata management tool that addresses the problems of organising, documenting, storing and sharing data in a research unit or infrastructure, and fits perfectly into a data management plan of a collective.
The central idea is that the storage space becomes the data repository, so the metadata should go to the data and not the other way around.
Given the diversity of domains, the approach chosen is to be both as flexible and as pragmatic as possible by allowing each collective to choose its own (controlled) vocabulary corresponding to the reality of its field and activities. The main idea is to be able to "capture" the user's metadata as easily as possible using their vocabulary. It is possible to define the whole terminology using a spreadsheet.
The choice was made for the JSON format, which is very appropriate for describing metadata, readable by both humans and machines.
This tool is built around a web interface coupled with a MongoDB database. The web interface allows you to i) Describe a dataset using metadata of various types (Description), ii) Search datasets by their metadata (Accessibility).
Metadata for Terminology / KOS ResourcesMarcia Zeng
1. Why do we need metadata for terminology resources? 2. What do we need to know about a terminology resource? 3. Is there a standardized set of metadata elements for terminology resources?-- a presentation at the "New Dimensions in Knowledge Organization Systems", a Joint NKOS/ CENDI Workshop, World Bank, Washington, DC. September 11, 2008 http://nkos.slis.kent.edu/2008workshop/NKOS-CENDI2008.htm
This Object Management Group (OMG) RFP solicits submissions identifying and defining mechanisms to achieve integration between DDS infrastructures and TSN networks. The goal is to provide all artifacts needed to support the design, deployment and execution of DDS systems over TSN networks.
The DDS-TSN integration specification sought shall realize the following functionality:
● Define mechanisms that provide the information required for TSN-enabled networks to calculate any network schedules needed to deploy a DDS system.
OMG RFP
● Identify those parts of the set of the IEEE TSN standards that are relevant for a DDS-TSN integration and indicate how the DDS aspects are mapped onto, or related to, the associated TSN aspects. Examples include TSN- standardized information models for calculating system-wide schedules and configuring network equipment.
● Identify and specify necessary extensions to the [DDSI-RTPS] and [DDS- SECURITY] specifications, if any, to allow DDS infrastructures to use TSN- enabled networks as their transport while maintaining interoperability between different DDS implementations.
● Identify and specify necessary extensions to the DDS and DDS- XML specification, if any, to allow declaration of TSN-specific properties or quality of service attributes.
This is an introduction session about Microsoft Entity Framework 4.0 (year 2011), since then the technology has evolved and matured in many ways and some of the limitations had been mitigated.
A brief report on the work of the DCMI/IEEE Task Force on interoperability between the IEEE Learning Object Metadata standard and Dublin Core.
Presentation given to meeting of CETIS Metadata & Digital Repositories Special Interest Group held in Bath on 28 June 2006.
Over the last 10 years, the status of educational metadata, specifically
as they relate to learning objects, has changed radically. In the heady
days of the turn of the millennium, learning objects and their metadata
were seen as being destined to forever change the shape and form of
learning; by 2007, this approach has been derisively labeled "industrialist", and said to be quickly running "out of steam."
Given such drastic changes, how are metadata to be understood in the context
of different and emerging approaches to online learning resources, above
all those labelled 'open'? This question will be the focus of this presentation by Dr. Norm Friesen, Canada Research Chair in E-Learning Practices at Thompson Rivers University and Director of the CanCore
Initiative. Dr. Friesen will consider a number of alternatives to "learning object metadata." Dr. Friesen will conclude his
presentation by discussing an alternative that incorporates both high tech and ow tech approaches --one that is currently under
development as a multi-part international standard under the auspices of ISO (the
International Organization for Standardization).
Metadata management for data storage spaces :
INDEXATOR is a metadata management tool that addresses the problems of organising, documenting, storing and sharing data in a research unit or infrastructure, and fits perfectly into a data management plan of a collective.
The central idea is that the storage space becomes the data repository, so the metadata should go to the data and not the other way around.
Given the diversity of domains, the approach chosen is to be both as flexible and as pragmatic as possible by allowing each collective to choose its own (controlled) vocabulary corresponding to the reality of its field and activities. The main idea is to be able to "capture" the user's metadata as easily as possible using their vocabulary. It is possible to define the whole terminology using a spreadsheet.
The choice was made for the JSON format, which is very appropriate for describing metadata, readable by both humans and machines.
This tool is built around a web interface coupled with a MongoDB database. The web interface allows you to i) Describe a dataset using metadata of various types (Description), ii) Search datasets by their metadata (Accessibility).
Metadata for Terminology / KOS ResourcesMarcia Zeng
1. Why do we need metadata for terminology resources? 2. What do we need to know about a terminology resource? 3. Is there a standardized set of metadata elements for terminology resources?-- a presentation at the "New Dimensions in Knowledge Organization Systems", a Joint NKOS/ CENDI Workshop, World Bank, Washington, DC. September 11, 2008 http://nkos.slis.kent.edu/2008workshop/NKOS-CENDI2008.htm
This Object Management Group (OMG) RFP solicits submissions identifying and defining mechanisms to achieve integration between DDS infrastructures and TSN networks. The goal is to provide all artifacts needed to support the design, deployment and execution of DDS systems over TSN networks.
The DDS-TSN integration specification sought shall realize the following functionality:
● Define mechanisms that provide the information required for TSN-enabled networks to calculate any network schedules needed to deploy a DDS system.
OMG RFP
● Identify those parts of the set of the IEEE TSN standards that are relevant for a DDS-TSN integration and indicate how the DDS aspects are mapped onto, or related to, the associated TSN aspects. Examples include TSN- standardized information models for calculating system-wide schedules and configuring network equipment.
● Identify and specify necessary extensions to the [DDSI-RTPS] and [DDS- SECURITY] specifications, if any, to allow DDS infrastructures to use TSN- enabled networks as their transport while maintaining interoperability between different DDS implementations.
● Identify and specify necessary extensions to the DDS and DDS- XML specification, if any, to allow declaration of TSN-specific properties or quality of service attributes.
This is an introduction session about Microsoft Entity Framework 4.0 (year 2011), since then the technology has evolved and matured in many ways and some of the limitations had been mitigated.
A brief report on the work of the DCMI/IEEE Task Force on interoperability between the IEEE Learning Object Metadata standard and Dublin Core.
Presentation given to meeting of CETIS Metadata & Digital Repositories Special Interest Group held in Bath on 28 June 2006.
An Approach to Detecting Writing Styles Based on Clustering Techniquesambekarshweta25
An Approach to Detecting Writing Styles Based on Clustering Techniques
Authors:
-Devkinandan Jagtap
-Shweta Ambekar
-Harshit Singh
-Nakul Sharma (Assistant Professor)
Institution:
VIIT Pune, India
Abstract:
This paper proposes a system to differentiate between human-generated and AI-generated texts using stylometric analysis. The system analyzes text files and classifies writing styles by employing various clustering algorithms, such as k-means, k-means++, hierarchical, and DBSCAN. The effectiveness of these algorithms is measured using silhouette scores. The system successfully identifies distinct writing styles within documents, demonstrating its potential for plagiarism detection.
Introduction:
Stylometry, the study of linguistic and structural features in texts, is used for tasks like plagiarism detection, genre separation, and author verification. This paper leverages stylometric analysis to identify different writing styles and improve plagiarism detection methods.
Methodology:
The system includes data collection, preprocessing, feature extraction, dimensional reduction, machine learning models for clustering, and performance comparison using silhouette scores. Feature extraction focuses on lexical features, vocabulary richness, and readability scores. The study uses a small dataset of texts from various authors and employs algorithms like k-means, k-means++, hierarchical clustering, and DBSCAN for clustering.
Results:
Experiments show that the system effectively identifies writing styles, with silhouette scores indicating reasonable to strong clustering when k=2. As the number of clusters increases, the silhouette scores decrease, indicating a drop in accuracy. K-means and k-means++ perform similarly, while hierarchical clustering is less optimized.
Conclusion and Future Work:
The system works well for distinguishing writing styles with two clusters but becomes less accurate as the number of clusters increases. Future research could focus on adding more parameters and optimizing the methodology to improve accuracy with higher cluster values. This system can enhance existing plagiarism detection tools, especially in academic settings.
Understanding Inductive Bias in Machine LearningSUTEJAS
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
Saudi Arabia stands as a titan in the global energy landscape, renowned for its abundant oil and gas resources. It's the largest exporter of petroleum and holds some of the world's most significant reserves. Let's delve into the top 10 oil and gas projects shaping Saudi Arabia's energy future in 2024.
Student information management system project report ii.pdfKamal Acharya
Our project explains about the student management. This project mainly explains the various actions related to student details. This project shows some ease in adding, editing and deleting the student details. It also provides a less time consuming process for viewing, adding, editing and deleting the marks of the students.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
HEAP SORT ILLUSTRATED WITH HEAPIFY, BUILD HEAP FOR DYNAMIC ARRAYS.
Heap sort is a comparison-based sorting technique based on Binary Heap data structure. It is similar to the selection sort where we first find the minimum element and place the minimum element at the beginning. Repeat the same process for the remaining elements.
Online aptitude test management system project report.pdfKamal Acharya
The purpose of on-line aptitude test system is to take online test in an efficient manner and no time wasting for checking the paper. The main objective of on-line aptitude test system is to efficiently evaluate the candidate thoroughly through a fully automated system that not only saves lot of time but also gives fast results. For students they give papers according to their convenience and time and there is no need of using extra thing like paper, pen etc. This can be used in educational institutions as well as in corporate world. Can be used anywhere any time as it is a web based application (user Location doesn’t matter). No restriction that examiner has to be present when the candidate takes the test.
Every time when lecturers/professors need to conduct examinations they have to sit down think about the questions and then create a whole new set of questions for each and every exam. In some cases the professor may want to give an open book online exam that is the student can take the exam any time anywhere, but the student might have to answer the questions in a limited time period. The professor may want to change the sequence of questions for every student. The problem that a student has is whenever a date for the exam is declared the student has to take it and there is no way he can take it at some other time. This project will create an interface for the examiner to create and store questions in a repository. It will also create an interface for the student to take examinations at his convenience and the questions and/or exams may be timed. Thereby creating an application which can be used by examiners and examinee’s simultaneously.
Examination System is very useful for Teachers/Professors. As in the teaching profession, you are responsible for writing question papers. In the conventional method, you write the question paper on paper, keep question papers separate from answers and all this information you have to keep in a locker to avoid unauthorized access. Using the Examination System you can create a question paper and everything will be written to a single exam file in encrypted format. You can set the General and Administrator password to avoid unauthorized access to your question paper. Every time you start the examination, the program shuffles all the questions and selects them randomly from the database, which reduces the chances of memorizing the questions.
Sachpazis:Terzaghi Bearing Capacity Estimation in simple terms with Calculati...Dr.Costas Sachpazis
Terzaghi's soil bearing capacity theory, developed by Karl Terzaghi, is a fundamental principle in geotechnical engineering used to determine the bearing capacity of shallow foundations. This theory provides a method to calculate the ultimate bearing capacity of soil, which is the maximum load per unit area that the soil can support without undergoing shear failure. The Calculation HTML Code included.
Technical Drawings introduction to drawing of prisms
metadata profiles for protected sites. analysis and propositions for annex III
1. TASK 3.2
Metadata profile for Protected Sites.
Analysis and propositions for Annex III
Jean Christophe Desconnets
IRD - ESPACE
2. Previous steps (M2 - M7)
Metadata specification draft v0.1 on february 2009 based on :
On metadata INSPIRE requirements
Fill out with the proposition of DS protected Sites V2.0
Review and discussion on 1srt
draft
Review and comments from NatureSDI+ technical commitee
Discussion and decision during the workshop of Pamplona
3. Current step (M7 - M12)
Metadata specification draft v0.2 :
Decision of april 2009 and comment of Technical Comittee
new theme-specific metadata from DS Protected Sites V3.0
early analysis of theme-specific metadata for annex III
4. Current step (M7 - M12)
Review and discussion on 1srt
draft
Discussion and decision during the workshop of Pamplona
The scope of NatureSDI+ metadata profile or level of description of data
Data series
Metadata recordDataset
service
feature
Metadata record1
1
1
1 1
*
*
*
11
5. Current step (M7 - M12)
Review and discussion on 1srt
draft
Review and comments from NatureSDI+ technical commitee
Store URI of the concept related to the keyword
6. Current step (M7 - M12)
Review and discussion on 1srt
draft
Review and comments from NatureSDI+ technical commitee
Extend domain of CI_Citation to have better description of Thesaurus
citation
7. Current step (M7 - M12)
Presentation of Metadata specification Draft
Metadata specification for NatureSDI+ project
Synthesis of metadata elements
Detailed description of metadata elements
INSPIRE IR for metadata
Extension of INSPIRE IR metadata for Protected Sites
Mapping NatureSDI+ D2.3 metadata / ISO 19115/119
8. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules
for metadata or in the Data specification of the data theme considered
Definition
Obligation/Condition
Multiplicity
ISO 19115 Number. Name
ISO/TS 19139 Path
Data type
Domain
INSPIRE conformity
INSPIRE reference
Implementing instructions
Example
Example XML encoding
Comments
Example : Keyword value
9. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms
for describing the metadata
Obligation/Condition
Multiplicity
ISO 19115 Number. Name
ISO/TS 19139 Path
Data type
Domain
INSPIRE conformity
INSPIRE reference
Implementing instructions
Example
Example XML encoding
Comments
Example : Commonly used word(s) or formalised word(s) or phrase(s) used
to describe the subject.
10. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity
ISO 19115 Number. Name
ISO/TS 19139 Path
Data type
Domain
INSPIRE conformity
INSPIRE reference
Implementing instructions
Example
Example XML encoding
Comments
Example : Mandatory.
11. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity The multiplicity of the metadata element.
ISO 19115 Number. Name The number and the name that identifies the metadata element inside
tables in ISO published standard.
ISO/TS 19139 Path
Data type
Domain
INSPIRE conformity
INSPIRE reference
Implementing instructions
Example
Example XML encoding
Comments
Example : 53. keyword.
12. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity The multiplicity of the metadata element.
ISO 19115 Number. Name The number and the name that identifies the metadata element inside tables in ISO published standard.
ISO/TS 19139 Path A ISO/TS 19139 XPath expression indicating the metadata element within the ISO UML model
Data type The data type of the ISO element
Domain The domain of value of the ISO metadata element
INSPIRE conformity INSPIRE conformity regarding INSPIRE implementation rules
for metadata and Data Specification for data theme
considered
INSPIREreference
Implementing instructions
Example
ExampleXML encoding
Comments
Example : true.
13. Current step (M7 - M12)
Description of metadata element and implementing intructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity The multiplicity of the metadata element.
ISO 19115 Number. Name The number and the name that identifies the metadata element inside tables in ISO published standard.
ISO/TS 19139 Path A ISO/TS 19139 XPath expression indicating the metadata element within the ISO UML model
Data type The data type of the ISO element
Domain The domain of value of the ISO metadata element
INSPIRE conformity INSPIRE conformity regarding INSPIRE implementation rules for metadata and Data Specification
for data theme considered
INSPIRE reference INSPIRE reference document used to evaluate the degree of conformity
Implementing instructions Implementinginstructions, which give more warnings about the
implementation in the particular context of the current
metadata element.
Example
ExampleXML encoding
Comments
Example : Each instance of ISO 19115 keyword may originate from a controlled
vocabulary described through the thesaurusName property of the instance of
descriptiveKeywords to which the keyword pertains.
14. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity The multiplicity of the metadata element.
ISO 19115 Number. Name The number and the name that identifies the metadata element inside tables in ISO published standard.
ISO/TS 19139 Path A ISO/TS 19139 XPath expression indicating the metadata element within the ISO UML model
Data type The data type of the ISO element
Domain The domain of value of the ISO metadata element
INSPIRE conformity INSPIRE conformity regarding INSPIRE implementation rules for metadata and Data Specification
for data theme considered
INSPIRE reference INSPIRE reference document used to evaluate the degree of conformity
Implementing instructions Implementing instructions, which give more warnings about the implementation in the particular
context of the current metadata element.
Example An example that illustrates the description of the current
metadata element by providing a concrete case.
Example XML encoding
Comments
Example : espace protégé.
15. Current step (M7 - M12)
Description of metadata element and implementing instructions
Metadata element name The name of the metadata element as used in the implementing rules for metadata or in the Data
specification of the data theme considered
Definition The definition, which gives the current ISO 19115 or ISO 19119 terms for describing the metadata
Obligation/Condition The obligation/condition applicable to the metadata element.
Multiplicity The multiplicity of the metadata element.
ISO 19115 Number. Name The number and the name that identifies the metadata element inside tables in ISO published standard.
ISO/TS 19139 Path A ISO/TS 19139 XPath expression indicating the metadata element within the ISO UML model
Data type The data type of the ISO element
Domain The domain of value of the ISO metadata element
INSPIRE conformity INSPIRE conformity regarding INSPIRE implementation rules for metadata and Data Specification
for data theme considered
INSPIRE reference INSPIRE reference document used to evaluate the degree of conformity
Implementing instructions Implementing instructions, which give more warnings about the implementation in the particular
context of the current metadata element.
Example An examplethat illustrates the description of the current metadata element by providing a concrete
case.
ExampleXML encoding An example of XML encoding , i.e a fragment of the XML of a
metadata record.
Comments
Example :
<gmd:MD_Keywords>
<gmd:keyword>
<gmx:Anchor xlink:href= "http://www.eionet.europa.eu/gemet/concept/6740">espace
protégé</gmx:Anchor>
</gmd:keyword>
…
</gmd:MD_Keywords>
16. Current step (M7 - M12)
New propositions of metadata element from DS Protected Sites V3.0
Reference system information
Coordinate Reference System [1]
Temporal Reference System [1]
Encoding information
Encoding [1..*]
Character encoding [0..*]
Data schema used
Application schema [1]
Data quality
Maintenance Information [0..1]
Completeness – Comission [0..*]
Completeness – Omission [0..*]
Positional accuracy [0..*]
17. Current step (M7 - M12)
Analysis of metadata proposition for annex III dataset
Based on University of Aberdeen results ( T2.3 : Data sets analysis and
systematization)
Method
Crossing analysis with existing specifications (INSPIRE metadata & DS PS
V3)
Mapping T2.3 proposition / ISO 19115/119
18. Current step (M7 - M12)
First Analysis, metadata proposed :
Spatial Representation information
Information about digital mechanism to represent spatial representation and its related properties
Vector data properties
Grid data properties
19. Current step (M7 - M12)
First Analysis, metadata proposed :
Lineage
Information about data source
and process step
Data source Process step
20. Current step (M7 - M12)
First Analysis, metadata proposed :
Species classification (Taxonomy)
Many questions :
Data / metadata ? ??
A commun taxomony to valuate these elements ???
Accuracy of data/measure.
Most of propositions are including in :
INSPIRE IR for metadata
New version of DS PS v3
21. From Montpellier to M16 (deliverable time)
Final draft of Metadata specification for NatureSDI+ :
Discussion and decision on metadata analysis (T2.1, T3.1, T3.3, …)
Analysis of result of T2.1
Mise en cohérence des travaux T3.2 / T3.3
Ma présentation propose de faire un point sur l’état d’avancement des travaux de la tâche 3.2,
Je présenterais les modifications apportées à la nouvelle version du draft du profil de métadonnées dont
celles apportées par le projet et la version 3 des Data specification des sites protégés
je donnerais aussi quelques des éléments sur l’analyse des métadonnées pour les thèmes de l’annexe III
Quelques éléments sur les étapes précédentes.
Un draft a été proposé en février. Il s’agissait d’une compilation des éléments de métadonnées issus
des règles d’implémentation sur les métadonnées et
Des éléments de métadonnées proposés par la Data Specification des sites protégés version 2
Sur cette base, une révision a été réalisée par certain membre du comité technique et
a été complété lors du meeting de pampeluna en avril
Les travaux actuels ont portés sur la rédaction d’une nouvelle version des spécifications des métadonnées.
Cette nouvelle version est le résultat :
Des décisions prises sur le sujet en avril à pampelune lors de l’atelier technique,
Et des commentaires et révisions proposés par les membres du comité technique
L’intégration des modifications apportées par la nouvelle version des spécifications de données pour les sites protégés
Et enfin
Une première analyse des métadonnées spécifique aux thèmes de l’annexe III.
Je vous propose de donner quelques éléments sur chacun des points cités.
La principale décision prise a pampelona concerne la portée d’application des métadonnées
Nous avons réduit la portée d’application des métadonnées à une partie de la hierarchie
Comme cela est montré par le schéma UML,
il a été décidé de décrire les métadonnées seulement pour le niveau jeu de données et service spatial
La description des collections de données ou du niveau des entités est donc hors du champ de notre spécification
Nous donnons ici l’exemple des propositions apportées. Celles qui sont données en exemples
sont relatives aux besoins d’assurer le support multi langue du vocabulaire controlé et
de véhiculer une information plus riche que ce que propose l’ISO et INSPIRE
Notamment permettre le stockage des URI du concept au lieu de stocker la chaîne de caractère d’un terme issu du thésaurus
Ce qui implique une modification du type de l’élément keyword tel que définis dans les règles d’implémentation
des métadonnées INSPIRE.
En terme d’encodage la modification apportée par cette proposition est en vert. Cela permet de conserver l’URI
et de pouvoir par exemple construire des méchanisme de traduction plus facilement
Deuxième proposition lié à la première concerne
le complément d’informations sur l’origine du vocabulaire controlé utilisé
notamment en précisant la version du thésaurus et donnant des informations sur la partie responsable
En terme d’encodage voici en vert la modification apportée par cette proposition
D’autres modifications mineures ont été apportées
Concernant le document de spécification des métadonnées, voici quelques éléments sur son organisation
et son contenu :
La partie principale concerne bien évidemment la specification des métadonnées. Elle comprend une partie
Présentant de manière synthétique les éléments de métadonnées
Et deuxième partie détaillant un à un l’ensemble des éléments.
Dans cette partie, nous avons distingué :
Les éléments venant des règles d’implémentation des métadonnées d’INSPIRE avec nos modifications
Une section proposant les éléments spécifiques au thèmes espace protégé et une dernière section
Proposant la correspondance entre proposition de métadonnées par le WP2 et l’ISO 19115/119 quand cela est possible
Afin de faciliter la compréhénsion de la spécification pour son implémentation dans le cadre du projet.
Chaque élément de métadonnées est décrit à travers un tableau. Je vais donner un aperçu des principales propriétes
présentées dans ce tableau.
La première est bien évident le nom de l’élément de métadonnées.
Pour illustrer, nous donnons un exemple de valeur. Ici, il s’agit de l’élément keyword
La propriété suivante est la définition de l’élément
Pour l’élément keyword value, la définition est
La 3eme propriété
Dans le cas de l’élément keyword value, cette propriété est Mandatory
La 4eme proprieté est …
INSPIRE Conformity est une nouvelle propriété.
Elle qui permet d’évaluer la conformité de notre spécification.
Elle est complétée par un document de référence, la propriété du dessous
Pour le cas de l’élément keyword value, cette propriété a la valeur vraie
The propertie implementing instructions …
Lorsque que cela est nécessaire, elle complété pour tenir compte du contexte du projet
The next propertie is …
Nous donnons ici un terme en français issu du thésaurus gemet
The propertie example of XML encoding
Give an example of encoding of metadata element in XML ISO 19139
Les propositions apportées par la version 3 de la specification des données
des sites protégées sont plus cohérentes que la précédente
Elle propose d’étendre les métadonnées pour assurer la description :
Des référentiels spatiales et temporel
Donner des informations sur l’encodage des données et métadonnées
Des informations sur le schéma de données utilisé (simple, full or natura 2000)
- Apporter des indicateurs de qualité sur
. Excés de données
. Le manque de données
. Et la précision de positionnement
Pour finir la présentation des travaux engagés sur la spécification des métadonnées,
Je vous propose de donner des éléments de discussion sur l’analyse des métadonnées pour les
Thèmes de l’annexe III.
Tout d’abord, ce premier travail porte sur les résultats, les classeurs excel fournis par l’université d’aberdeen
qui synthétisent l’analyse des jeux de données dans le cadre du projet.
Ces synthèses comprennent pour chacun des thèmes une proposition d’élément de métadonnées.
L’analyse s’est passée en trois temps :
Une analyse croisée entre les propositions de la tache 2.3 et les spécifications existantes
Et une mise en correspondance, lorsque c’est possible,
des propositions avec les standards de métadonnées ISO
A partir de cette première analyse, on peut identifier 4 types de métadonnées.
Le premier concerne les informations touchant la répresentation spatiale des données.
La mise en correspondance pour ces métadonnées avec l’ISO est simple.
La classe MD_SpatialRepresentationInformation est spécialisée par la classe MD_GridSpatialRepresentation
qui permet de définir les propriétés des jeux de données de type Grid
Il en est de même pour les données de type vecteur
où la classe MD_VectorSpatialRepresentation propose des informations sur les propriétés des géométries
Il semble, mais c’est à discuter plus précisement qu’une grande majorité des éléments de métadonnées proposés
Concerne la description des procédures d’acquisition sur le terrain, de traitements des jeux de données bruts
ou des jeux de données ayant été utilisé comme support au traitement
Pour ces propositions, la correspondance avec l’ISO est moins évidente et demande un travail d’abstraction des
Propositions.
Mais il me semble que les classes attachées à la description de la généalogie de l’ISO 191115, notamment
Celle décrivant de manière précise les sources de données et
Celle décrivant les étapes de traitements
Pourraient être utilisées dans ce cadre. Des travaux précis avec les personnes de la tache 2.3 sont évidents nécessaires
Enfin, il ressort de cette analyse deux autres types de métadonnées :
Un concernant des indicateurs de qualité des mesures et des jeux de données. Pour cela, mais c’est à vérifier,
Il me semble que la specificition des sites protégés V3 apportent déjà ces éléments sur la qualité des jeux de données
Concernant l’autre type de métadonnées : elles sont relatives aux éléments de classification des espèces.
Je ne suis pas spécialiste de ces questions mais deux questions se posent :
Doit on inclure des informations dans les données ou dans les métadonnées
Et dans les deux cas, comment assure t’on la cohérence de la classification employée ou formuler autrement
Avons nous une classification commune à utiliser pour renseigner ces champs ?
La prochaine et dernière étape pour la tâche 3.2 est d’ici le mois de janvier
la rédaction d’une version finale de la spécification des métadonnées
Pour cela, au moins actions devront être engagées :
Des discussions avec les intervenants des WP 2 & WP3
Une analyse des résultats de la tâche 2.1 user needs
Et une mise en cohérence entre les travaux de spécifications de données et de métadonnées.