kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/schemas/20251121/linkml/modules/classes/FundingRequirement.yaml
kempersc 69a22e2b5a Refactor and expand LinkML slot definitions 
- Deleted the `rights_statement_url` slot definition as it is no longer needed.
- Added multiple new slots including `has_legal_basis`, `has_statement`, `impose`, `pose_condition`, and `reviewed_through` with detailed descriptions and ontology alignments.
- Updated existing slots to improve clarity and consistency, including renaming `close_mappings` to `related_mappings` in several definitions.
- Enhanced the `require` slot with additional aliases for better usability.
- Improved documentation and comments across all slot definitions to clarify their purpose and usage.
2026-02-08 23:37:44 +01:00

218 lines
15 KiB
YAML
Raw Blame History

id: https://nde.nl/ontology/hc/class/FundingRequirement
name: FundingRequirement
title: FundingRequirement Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
prov: http://www.w3.org/ns/prov#
pav: http://purl.org/pav/
skos: http://www.w3.org/2004/02/skos/core#
imports:
- linkml:types
- ../enums/FundingRequirementTypeEnum
- ../slots/20260202_matang/apply_to
- ../slots/20260202_matang/has_note
- ../slots/20260202_matang/has_score
- ../slots/20260202_matang/has_type
- ../slots/20260202_matang/new/is_mandatory
- ../slots/20260202_matang/new/observed_in
- ../slots/20260202_matang/new/requirement_id
- ../slots/20260202_matang/new/requirement_text
- ../slots/20260202_matang/new/requirement_type
- ../slots/20260202_matang/new/requirement_unit
- ../slots/20260202_matang/new/requirement_value
- ../slots/20260202_matang/new/source_section
- ../slots/20260202_matang/supersede
- ../slots/20260202_matang/temporal_extent
default_prefix: hc
classes:
FundingRequirement:
class_uri: dcterms:Standard
description: "A requirement or criterion that applicants must meet to be eligible for\na funding call. Each requirement is tracked with provenance linking to\nthe source document where it was stated.\n\n**PURPOSE**:\n\nFundingRequirement provides structured, machine-readable representation\nof funding call eligibility criteria. Instead of storing requirements as\nfree-text lists in CallForApplication, each requirement becomes a\ntrackable entity with:\n\n- **Classification**: Categorized by FundingRequirementTypeEnum\n- **Provenance**: Linked to WebObservation documenting source\n- **Values**: Machine-readable value + human-readable text\n- **Temporality**: Valid date range for time-scoped requirements\n\n**PROVENANCE CHAIN**:\n\n```\nCallForApplication\n \u2502\n \u251C\u2500\u2500 requirements \u2500\u2500\u2192 FundingRequirement[]\n \u2502 \u2502\n \u2502 \u251C\u2500\u2500 requirement_type: PARTNERSHIP_MINIMUM_PARTNERS\n\
\ \u2502 \u251C\u2500\u2500 requirement_text: \"At least 3 partners from 3 EU countries\"\n \u2502 \u251C\u2500\u2500 requirement_value: \"3\"\n \u2502 \u251C\u2500\u2500 requirement_unit: \"partners\"\n \u2502 \u2502\n \u2502 \u2514\u2500\u2500 observed_in \u2500\u2500\u2192 WebObservation\n \u2502 \u2502\n \u2502 \u251C\u2500\u2500 source_url: https://ec.europa.eu/...\n \u2502 \u251C\u2500\u2500 retrieved_on: 2025-11-29T10:30:00Z\n \u2502 \u2514\u2500\u2500 extraction_confidence: 0.95\n \u2502\n \u2514\u2500\u2500 web_observations \u2500\u2500\u2192 WebObservation[] (general call provenance)\n```\n\n**ONTOLOGY\
\ ALIGNMENT**:\n\n- **Dublin Core**: `dcterms:Standard` - \"A reference point against which\n other things can be evaluated\" (requirements are standards for eligibility)\n- **Dublin Core**: `dcterms:requires` - Relates call to requirement\n- **Dublin Core**: `dcterms:conformsTo` - Applicants must conform to requirements\n- **Schema.org**: `schema:eligibleRegion` - For geographic requirements\n- **Schema.org**: `schema:eligibleQuantity` - For numeric constraints\n- **PROV-O**: `prov:wasDerivedFrom` - Links requirement to observation\n\n**REQUIREMENT CATEGORIES**:\n\nRequirements are classified into six main categories via FundingRequirementTypeEnum:\n\n1. **Eligibility** (ELIGIBILITY_*): Who can apply\n - Geographic: EU Member States, Associated Countries\n - Organizational: Non-profit, public body, SME\n - Heritage type: Museums, archives, libraries\n - Experience: Track record, previous projects\n\n2. **Financial** (FINANCIAL_*): Budget and funding\n - Co-funding: Match\
\ funding percentages\n - Budget limits: Minimum/maximum grant size\n - Funding rate: Percentage of eligible costs\n - Eligible costs: What can be funded\n\n3. **Partnership** (PARTNERSHIP_*): Consortium requirements\n - Minimum partners: Number required\n - Country diversity: Geographic spread\n - Sector mix: Organisation types needed\n - Coordinator: Lead partner constraints\n\n4. **Thematic** (THEMATIC_*): Topic and scope\n - Focus area: Required research/action themes\n - Heritage scope: Types of heritage addressed\n - Geographic scope: Where activities occur\n\n5. **Technical** (TECHNICAL_*): Outputs and approach\n - Deliverables: Required outputs\n - Open access: Publication requirements\n - Duration: Project length constraints\n - Methodology: Required approaches\n\n6. **Administrative** (ADMINISTRATIVE_*): Process requirements\n - Registration: Portal accounts needed\n - Documentation: Supporting documents\n - Language: Submission language\n\
\ - Format: Templates and page limits\n\n**TEMPORAL TRACKING**:\n\nRequirements can change between call publications. The `supersedes` field\nlinks to previous versions, and `valid_from`/`valid_to` scope applicability:\n\n```\nFundingRequirement (current)\n \u2502\n \u251C\u2500\u2500 valid_from: 2025-01-15\n \u251C\u2500\u2500 requirement_value: \"3\" (minimum partners)\n \u2502\n \u2514\u2500\u2500 supersedes \u2500\u2500\u2192 FundingRequirement (previous)\n \u2502\n \u251C\u2500\u2500 valid_from: 2024-01-15\n \u251C\u2500\u2500 valid_to: 2025-01-14\n \u2514\u2500\u2500 requirement_value: \"4\" (was 4 partners)\n```\n\n**EXTRACTION PATTERN**:\n\nWhen extracting requirements from web sources:\n\n1. Create WebObservation for the source page\n2. For each requirement found:\n - Create FundingRequirement with observed_in \u2192 WebObservation\n\
\ - Classify using FundingRequirementTypeEnum\n - Extract machine-readable value and unit\n - Record source_section for traceability\n - Assign extraction_confidence based on clarity\n\n**EXAMPLES**:\n\n1. **Partnership Requirement**\n - requirement_type: PARTNERSHIP_MINIMUM_PARTNERS\n - requirement_text: \"Minimum 3 independent legal entities from 3 different EU Member States\"\n - requirement_value: \"3\"\n - requirement_unit: \"partners\"\n - is_mandatory: true\n \n2. **Financial Requirement**\n - requirement_type: FINANCIAL_COFUNDING\n - requirement_text: \"Co-funding of minimum 25% from non-EU sources required\"\n - requirement_value: \"25\"\n - requirement_unit: \"percent\"\n - is_mandatory: true\n \n3. **Open Access Requirement**\n - requirement_type: TECHNICAL_OPEN_ACCESS\n - requirement_text: \"All peer-reviewed publications must be open access (Plan S compliant)\"\n - requirement_value: \"immediate\"\n - is_mandatory: true\n"
exact_mappings:
- dcterms:Standard
close_mappings:
- schema:QuantitativeValue
- skos:Concept
related_mappings:
- dcterms:requires
- dcterms:conformsTo
- schema:eligibleRegion
- schema:eligibleQuantity
- prov:wasDerivedFrom
slots:
- apply_to
- has_note
- is_mandatory
- observed_in
- requirement_id
- requirement_text
- requirement_type
- has_type
- requirement_unit
- requirement_value
- source_section
- supersedes_or_superseded
- has_score
- temporal_extent
slot_usage:
requirement_id:
identifier: true
required: true
# range: string # uriorcurie
pattern: ^https://nde\.nl/ontology/hc/requirement/[a-z0-9-]+/[a-z0-9-]+$
examples:
- value: https://nde.nl/ontology/hc/requirement/ec-cl2-2025-heritage-01/min-partners-3
- value: https://nde.nl/ontology/hc/requirement/nlhf-medium-2025/cofunding-25pct
requirement_type:
required: false
range: FundingRequirementTypeEnum
deprecated: 'DEPRECATED 2026-01-13: Use has_type with RequirementType class instead'
examples:
- value: PARTNERSHIP_MINIMUM_PARTNERS
- value: FINANCIAL_COFUNDING
- value: ELIGIBILITY_GEOGRAPHIC
has_type:
required: true
range: RequirementType
examples:
- value:
has_code: PARTNERSHIP_MINIMUM_PARTNERS
has_label:
- Minimum partners requirement@en
- value:
has_code: FINANCIAL_COFUNDING
has_label:
- Co-funding requirement@en
requirement_text:
required: true
# range: string
examples:
- value: Minimum 3 independent legal entities from 3 different EU Member States or Horizon Europe Associated Countries
- value: Applications must demonstrate at least 25% co-funding from non-EU sources
requirement_value:
# range: string
examples:
- value: '3'
- value: '25'
- value: eu-member-states
- value: immediate
requirement_unit:
# range: string
examples:
- value: partners
- value: percent
- value: EUR
- value: months
- value: countries
is_mandatory:
range: boolean
ifabsent: 'true'
examples:
- value: true
description: 'Mandatory: must meet to be eligible'
- value: false
description: 'Optional: preferred but not required'
observed_in:
required: true
# range: string # uriorcurie
examples:
- value: https://nde.nl/ontology/hc/observation/web/2025-11-29/eu-horizon-cl2-heritage
source_section:
# range: string
examples:
- value: Section 2.1 - Eligibility Criteria
- value: 'FAQ #7 - Consortium composition'
- value: Work Programme page 45
supersedes_or_superseded:
# range: string # uriorcurie
examples:
- value: https://nde.nl/ontology/hc/requirement/ec-cl2-2024-heritage-01/min-partners-4
comments:
- Each requirement links to WebObservation for full provenance chain
- requirement_value + requirement_unit enable structured queries
- is_mandatory defaults to true; explicitly set false for optional requirements
- supersedes_or_superseded creates version chain for requirement changes
- extraction_confidence can differ from observation confidence
see_also:
- https://dublincore.org/specifications/dublin-core/dcmi-terms/#Standard
- https://schema.org/QuantitativeValue
- https://www.w3.org/TR/prov-o/#Entity
- http://purl.org/pav/
examples:
- value:
requirement_id: https://nde.nl/ontology/hc/requirement/ec-cl2-2025-heritage-01/min-partners-3-countries
requirement_type: PARTNERSHIP_MINIMUM_PARTNERS
requirement_text: Proposals must be submitted by a consortium of at least 3 independent legal entities established in 3 different EU Member States or Horizon Europe Associated Countries.
requirement_value: '3'
requirement_unit: partners
is_mandatory: true
apply_to: https://nde.nl/ontology/hc/call/ec/cl2-2025-heritage-01
observed_in: https://nde.nl/ontology/hc/observation/web/2025-11-29/eu-horizon-cl2-heritage
source_section: Section 2 - Eligibility Conditions
has_score:
has_score: 0.98
has_note: Clear statement in eligibility section. Standard Horizon Europe RIA requirement.
- value:
requirement_id: https://nde.nl/ontology/hc/requirement/ec-cl2-2025-heritage-01/cofunding-for-profit
requirement_type: FINANCIAL_COFUNDING
requirement_text: For-profit entities receive 70% funding rate. The remaining 30% must be covered by co-funding or own resources.
requirement_value: '30'
requirement_unit: percent
is_mandatory: true
apply_to: https://nde.nl/ontology/hc/call/ec/cl2-2025-heritage-01
observed_in: https://nde.nl/ontology/hc/observation/web/2025-11-29/eu-horizon-cl2-heritage
source_section: Section 3 - Financial Conditions
has_score:
has_score: 0.95
has_note: Applies only to for-profit partners. Non-profits receive 100% funding.
- value:
requirement_id: https://nde.nl/ontology/hc/requirement/ec-cl2-2025-heritage-01/open-access
requirement_type: TECHNICAL_OPEN_ACCESS
requirement_text: Beneficiaries must ensure open access to peer-reviewed scientific publications under the conditions required by the Grant Agreement. Immediate open access is mandatory (no embargo period).
requirement_value: immediate
requirement_unit: null
is_mandatory: true
apply_to: https://nde.nl/ontology/hc/call/ec/cl2-2025-heritage-01
observed_in: https://nde.nl/ontology/hc/observation/web/2025-11-29/eu-horizon-cl2-heritage
source_section: Section 4.2 - Open Science
has_score:
has_score: 0.99
has_note: Standard Horizon Europe open access requirement. Plan S compliant.
- value:
requirement_id: https://nde.nl/ontology/hc/requirement/nlhf-medium-2025/uk-based
requirement_type: ELIGIBILITY_GEOGRAPHIC
requirement_text: Your organisation must be based in the UK (England, Northern Ireland, Scotland or Wales). Projects must take place in the UK.
requirement_value: UK
requirement_unit: country
is_mandatory: true
apply_to: https://nde.nl/ontology/hc/call/nlhf/medium-grants-2025-q4
observed_in: https://nde.nl/ontology/hc/observation/web/2025-11-28/nlhf-medium-grants
source_section: Eligibility
has_score:
has_score: 0.99
has_note: Clear UK-only restriction. Devolved nations explicitly included.
- value:
requirement_id: https://nde.nl/ontology/hc/requirement/nlhf-medium-2025/non-profit
requirement_type: ELIGIBILITY_ORGANIZATIONAL
requirement_text: We can fund not-for-profit organisations, including charities, community groups, local authorities, and social enterprises. Private individuals and for-profit companies are not eligible.
requirement_value: non-profit
requirement_unit: organization-type
is_mandatory: true
apply_to: https://nde.nl/ontology/hc/call/nlhf/medium-grants-2025-q4
observed_in: https://nde.nl/ontology/hc/observation/web/2025-11-28/nlhf-medium-grants
source_section: Who can apply
has_score:
has_score: 0.95
has_note: Explicitly excludes for-profit. Social enterprises may need verification.
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"
Reference in a new issue View git blame Copy permalink