Add BT01 schemas #28
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,155 @@ | ||
| id: https://framework.regen.network/schema/BTCreditClass | ||
| name: BTCreditClass | ||
| prefixes: | ||
| linkml: https://w3id.org/linkml/ | ||
| rfs: https://framework.regen.network/schema/ | ||
| schema: http://schema.org/ | ||
| imports: | ||
| - linkml:types | ||
| default_curi_maps: | ||
| - semweb_context | ||
| default_prefix: rfs | ||
| default_range: string | ||
|
There was a problem hiding this comment. If the default range is |
||
|
|
||
| classes: | ||
| BT01CreditClass: | ||
| class_uri: rfs:BT01CreditClass | ||
| slots: | ||
| - approvedMethodologies | ||
| - coBenefits | ||
| - creditGenerationMethod | ||
| - creditingTerm | ||
| - description | ||
| - ecosystemType | ||
| - eligibleActivities | ||
| - geographicApplicability | ||
| - name | ||
| - permanencePeriod | ||
| - primaryImpact | ||
| - sourceRegistry | ||
| - url | ||
| Methodology: | ||
| class_uri: rfs:Methodology | ||
| description: Details about a specific methodology. | ||
| attributes: | ||
| identifier: | ||
| description: Unique identifier for the methodology. | ||
| name: | ||
| description: Name of the methodology. | ||
| url: | ||
| description: URL to the methodology document. | ||
| version: | ||
| description: Version number of the methodology. | ||
| MethodologyList: | ||
| class_uri: rfs:MethodologyList | ||
| description: List of methodologies for credit generation. | ||
| attributes: | ||
| itemListElement: | ||
| range: Methodology | ||
| multivalued: true | ||
| description: "List of methodology items." | ||
| PrimaryImpact: | ||
| class_uri: rfs:PrimaryImpact | ||
| description: Primary impact of the biodiversity project. | ||
| attributes: | ||
| id: | ||
| slot_uri: rfs:id | ||
| name: | ||
| slot_uri: schema:name | ||
| SDGs: | ||
| description: List of relevant Sustainable Development Goals for this impact. | ||
| range: SDG | ||
| multivalued: true | ||
|
Comment on lines
+59
to
+62
There was a problem hiding this comment. @S4mmyb currently In the past I have tried to avoid using plural wording for technical properties and just stick with singular words everywhere, knowing that some singular properties might indeed have mutliple values, thinking that the schema will specify if they are multi-valued, not the naming itself. Curious what you think about this more generally. |
||
| ProjectBenefit: | ||
| class_uri: rfs:ProjectBenefit | ||
| description: Benefits delivered by the biodiversity project. | ||
| attributes: | ||
| id: | ||
| description: Unique identifier for the project benefit. | ||
| required: true | ||
| name: | ||
| description: Name of the project benefit. | ||
| required: true | ||
| SDGs: | ||
| description: List of relevant Sustainable Development Goals. | ||
| range: SDG | ||
| multivalued: true | ||
| SDG: | ||
| class_uri: rfs:SDG | ||
| description: Represents a Sustainable Development Goal (SDG). | ||
| attributes: | ||
| id: | ||
| description: Unique identifier for the SDG. | ||
| required: true | ||
| name: | ||
| description: Name of the SDG. | ||
| required: true | ||
| description: | ||
| description: Detailed description of the SDG. | ||
| SourceRegistry: | ||
| class_uri: rfs:SourceRegistry | ||
| description: Details of the registry where the credits are tracked. | ||
| attributes: | ||
| name: | ||
| description: Name of the source registry. | ||
| url: | ||
| description: URL of the source registry. | ||
|
|
||
| slots: | ||
| approvedMethodologies: | ||
| description: Approved methodologies list for credit generation. | ||
| range: MethodologyList | ||
| slot_uri: rfs:approvedMethodologies | ||
| coBenefits: | ||
| description: List of co-benefits associated with the project. | ||
| multivalued: true | ||
| range: ProjectBenefit | ||
| slot_uri: rfs:coBenefits | ||
| creditGenerationMethod: | ||
| description: Method for generating biodiversity credits. | ||
| multivalued: true | ||
| slot_uri: rfs:creditGenerationMethod | ||
| creditingTerm: | ||
| description: Crediting term duration for the project. An ISO 8601 duration. | ||
| slot_uri: rfs:creditingTerm | ||
| description: | ||
| description: Description of the credit class. | ||
| required: true | ||
| slot_uri: schema:description | ||
| ecosystemType: | ||
| description: Type of ecosystem the project focuses on. | ||
| multivalued: true | ||
| slot_uri: rfs:ecosystemType | ||
| eligibleActivities: | ||
| description: Eligible activities for registered projects. | ||
| multivalued: true | ||
| slot_uri: rfs:eligibleActivities | ||
| geographicApplicability: | ||
| description: Geographic applicability of the credit class. | ||
| slot_uri: rfs:geographicApplicability | ||
| itemListElement: | ||
| description: List of methodologies in the methodology list. | ||
| multivalued: true | ||
| range: Methodology | ||
| name: | ||
| description: Name of the entity. | ||
| slot_uri: schema:name | ||
| permanencePeriod: | ||
| description: Permanence period of the credits. An ISO 8601 duration. | ||
| slot_uri: rfs:permanencePeriod | ||
| primaryImpact: | ||
| description: Primary impact of the project. | ||
| range: PrimaryImpact | ||
| slot_uri: rfs:primaryImpact | ||
| SDGs: | ||
| description: List of relevant Sustainable Development Goals. | ||
| multivalued: true | ||
| range: SDG | ||
| slot_uri: rfs:SDGs | ||
| sourceRegistry: | ||
| description: Source registry details including name and URL. | ||
| range: SourceRegistry | ||
| slot_uri: rfs:sourceRegistry | ||
| url: | ||
| description: Link to the Terrasos Biodiversity Credit documentation. | ||
| slot_uri: schema:url | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,6 +12,8 @@ imports: | |
| - ProjectPost | ||
| - TerrasosProjectInfo | ||
| - taxonomy | ||
| - BT01/BT01CreditClass | ||
| - BT01/BT01ProjectInfo | ||
| default_curi_maps: | ||
| - semweb_context | ||
| default_prefix: rfs | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@S4mmyb right now this is the BT01 credit class file you had started, except I have modified the ranges to be valid and work with linkml. The issue was we had ranges like
schema:DurationandURL, but ranges need to be proper data types that linkml understands OR custom data classes.I'm still not sure what our best option is for specifying a ISO 8601 Duration datatype. I wonder if this might be an easy contribution to LinkML core data types (they have other 8601 date/time types). Or, for now I have specified this in the description eg "Crediting term duration for the project. An ISO 8601 duration.".