Skip to content

Conversation

@matentzn
Copy link
Contributor

@matentzn matentzn commented Oct 4, 2025

No description provided.

Introduces new YAML files under tests/data/valid and tests/data/invalid to provide examples of both valid and invalid MappingSpecification objects. These files can be used for testing schema validation and error handling.
Introduces new classes (Agent, Source, MappingSpecification) and associated slots to the fair_mappings_schema.yaml.
@github-actions
Copy link
Contributor

github-actions bot commented Oct 4, 2025

PR Preview Action v1.6.2

🚀 View preview at
https://mapping-commons.github.io/fair-mappings-schema/pr-preview/pr-6/

Built to branch gh-pages at 2025-10-06 20:30 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Introduced AgentTypeEnum, SourceTypeEnum, and MappingSpecificationTypeEnum to define permissible values for agent, source, and mapping specification types. Updated the Agent, Source, and MappingSpecification classes to use these enums via slot_usage. Added new slots for version, type, and reviewer to relevant classes to enhance schema expressiveness.
Removed AgentTypeEnum and refactored Agent into abstract class with Person, Organization, and Software subclasses. Added new slots for agent subclasses and extended MappingTypeEnum with yarrrml and xslt options.
Replaces 'content' with 'content_url' in Source and MappingSpecification classes and updates all related YAML and test files. Adds 'metadata_url' and 'metadata_type' fields to Source for improved metadata handling.

MappingSpecificationTypeEnum:
description: Types of mapping specifications
permissible_values:
Copy link

@jkesanie jkesanie Oct 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add "shacl-rules" to the enum.

- linkml:types

enums:
SourceTypeEnum:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should either have specific definition languages (e.g. owl, skos etc) in all of the values or none of them. I would prefer this be a high level type i.e. ontology, database, vocabulary etc. We should another field for the specific definition language (or representation technique as ADMS puts it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants