BC Gov Mines Act Permit Credential #929
Closed
Conversation
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
Signed-off-by: pstlouis <[email protected]>
Signed-off-by: pstlouis <[email protected]>
TallTed
reviewed
Feb 6, 2024
| permit_no: | ||
| title: Permit Number | ||
| description: >- | ||
| (3-digit) Alpha-numeric identifier: M-##- or C-##- Permit Numbers are assigned to a specific mining operation or activity that has been granted permission or authorization. Mines Act Section 10 (1). |
There was a problem hiding this comment.
3-digit, so shouldn't there be 3 numeric placeholders?
Suggested change
| (3-digit) Alpha-numeric identifier: M-##- or C-##- Permit Numbers are assigned to a specific mining operation or activity that has been granted permission or authorization. Mines Act Section 10 (1). | |
| (3-digit) Alpha-numeric identifier: M-###- or C-###- Permit Numbers are assigned to a specific mining operation or activity that has been granted permission or authorization. Mines Act Section 10 (1). |
There was a problem hiding this comment.
I will request an example to find out and confirm the exact form of the value.
TallTed
reviewed
Feb 6, 2024
TallTed
reviewed
Feb 6, 2024
TallTed
reviewed
Feb 6, 2024
TallTed
reviewed
Feb 6, 2024
mkhraisha
requested changes
Feb 6, 2024
| - tsf_operating_count | ||
| - tsf_care_and_maintenance_count | ||
| example: |- | ||
| { |
There was a problem hiding this comment.
Please fill these up with sample values
| type: object | ||
| additionalProperties: false | ||
| example: |- | ||
| { |
There was a problem hiding this comment.
Similar to previous comment about examples
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
nissimsan
requested changes
Mar 8, 2024
| type: string | ||
| enum: | ||
| - MinesActPermit | ||
| permit_no: |
There was a problem hiding this comment.
Can you switch from snake to camel casing, pls, for consistency with all other schemas.
|
has there been any movement on this PR? |
|
@PatStLouis , any updates on this? |
|
@nissimsan we are closing this PR as our efforts with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a draft PR looking to align the BC Gov Energy and Mines Digital Trust framework with the traceability vocab to enable data exchanges. We are looking for feedback from both the traceability group on where these credentials would fit and the BC Gov EMDT governance team.
Here's the reference documentation