Skip to content

Selection Resources and References descriptions are very similar #833

New issue
New issue
Closed
Feature
#897
Closed
Selection Resources and References descriptions are very similar#833
Feature
#897
Assignees
sei-vsarvepalli
Labels
integrationRelated to integration of SSVC into another framework or systemtech/backendBack-end tools, code, infrastructuretech/dataData implementation (content of /data, data object instances, etc.)
Milestone
2025-09

Description

@ahouseholder
ahouseholder
opened on Jul 28, 2025

The two descriptions are very alike. Can we rephrase them, so that the difference of these fields is show more clearly?

Maybe, clearly state that the resources are about the decision points by stating: decision_point_resources.

And that references are about the decision context by renaming it to decision_context or basis_for_decision or decision_base_references

Originally posted by @tschmidtb51 in #821 (comment)

Activity

  1. ahouseholder
    assigned
    sei-vsarvepalli
    on Jul 29, 2025
  2. ahouseholder
    added
    integrationRelated to integration of SSVC into another framework or system
    on Jul 29, 2025
  3. ahouseholder
    added a parent issue on Jul 29, 2025
  4. ahouseholder
    added the
    Feature
    issue type on Aug 19, 2025
  5. ahouseholder
    added
    tech/backendBack-end tools, code, infrastructure
    tech/dataData implementation (content of /data, data object instances, etc.)
    on Aug 19, 2025

  6. sei-vsarvepalli commented on Aug 20, 2025

    @sei-vsarvepalli
    sei-vsarvepalli
    on Aug 20, 2025
    Contributor

    SSVC/data/schema/v2/Decision_Point_Value_Selection-2-0-0.schema.json

    Line 51 in afecc43

    "resources": {

    VS

    SSVC/data/schema/v2/Decision_Point_Value_Selection-2-0-0.schema.json

    Line 76 in afecc43

    "references": {

  7. sei-vsarvepalli
    added 2 commits that reference this issue on Aug 20, 2025

    Distinguish resource from references in Selections #833

    febcef6

    Distinguish resource from references in Selections #833

    e3b806d
  8. ahouseholder
    added a commit that references this issue on Aug 21, 2025

    Distinguish resource from references in Selections #833 (#897)

    0209e5b

  9. ahouseholder commented on Aug 21, 2025

    @ahouseholder
    ahouseholder
    on Aug 21, 2025
    ContributorAuthor

    Resolved by #833

  10. ahouseholder
    closed this as completedon Aug 21, 2025

  11. tschmidtb51 commented on Aug 25, 2025

    @tschmidtb51
    tschmidtb51
    on Aug 25, 2025
    Contributor

    Thank you for renaming resources to decision_point_resources 😄

  12. tschmidtb51 commented on Aug 25, 2025

    @tschmidtb51
    tschmidtb51
    on Aug 25, 2025
    Contributor

    Was there a specific reason not to rename references?

    (Just wondering - but if we want to change it, we need to do that before Wednesday 13:00 CEST).

  13. sei-vsarvepalli commented on Aug 25, 2025

    @sei-vsarvepalli
    sei-vsarvepalli
    on Aug 25, 2025
    Contributor

    Was there a specific reason not to rename references?

    (Just wondering - but if we want to change it, we need to do that before Wednesday 13:00 CEST).

    My decision was based on this the references is itself broader, it made sense to leave it as it is.

  14. tschmidtb51 commented on Aug 25, 2025

    @tschmidtb51
    tschmidtb51
    on Aug 25, 2025
    Contributor

    Was there a specific reason not to rename references?
    (Just wondering - but if we want to change it, we need to do that before Wednesday 13:00 CEST).

    My decision was based on this the references is itself broader, it made sense to leave it as it is.

    Thank you for the clarification

  15. ahouseholder
    added this to the 2025-09 milestone on Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

integrationRelated to integration of SSVC into another framework or systemtech/backendBack-end tools, code, infrastructuretech/dataData implementation (content of /data, data object instances, etc.)

Type

Feature

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions