Updates triggered by APKP discussions
@MartinKasp is already working on this.
Since May 7, 2024.
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
TF-2 Sections B.4
Priority
Martin's list
Issue 1
We agreed in the Alert-PKP working group that we need a unique alert event identifier from the alert source. This shall be a GUID. OBR requirements have to be updated accordingly.
Some background information on the unique identifier from the current APKP draft:
○ Extension pm:AlertConditionState/@apkp:AlertOccurrenceIdentifier --> type = GUID
○ Alert Provider: When AlertConditionState/@Presence is changed to true , set @apkp:AlertOccurrenceIdentifier in the same State version.
○ Extension pm:AlertConditionState/@apkp:OnsetStateVersion
○ Alert Provider: When AlertConditionState/@Presence is changed to true, set @apkp:OnsetStateVersion to the current State version in the same State version.
○ Alert Provider: While AlertConditionState/@Presence does not change to true, @apkp:AlertOccurrenceIdentifier and @apkp:OnsetStateVersion SHALL NOT be removed or modified.
Issue 2
Table TF-2:B.4.4.7.8-128. Alert Types Value Set Mapping need to be updated due to the APKP decision: advisories are no longer limited to @kind = Other, but to @priority / @ActualPriority = None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.