Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Use of URNs in SCRAPI #50

Open
OR13 opened this issue Dec 3, 2024 · 2 comments
Open

Use of URNs in SCRAPI #50

OR13 opened this issue Dec 3, 2024 · 2 comments
Milestone

Comments

@OR13
Copy link
Collaborator

OR13 commented Dec 3, 2024

https://mailarchive.ietf.org/arch/msg/scitt/u0HJWX7gPVIQ_Ix05iOk4vVT3FA/

TLDR; Remove all the URNs from the examples, and follow modern Open API Specification guidance for resource identifiers.

@JAG-UK
Copy link
Contributor

JAG-UK commented Dec 5, 2024

Grand, so boiling down the Open API guidance for us that seems to be human readable resource names and uuids for specific locators.

I guess in principle since they only need to be unique for a given TS, some of the identifiers could be simple numeric counters (as was the case for 'entries' in Maik's old emulator) but that just seems fragile and uuids are cheap.

@JAG-UK
Copy link
Contributor

JAG-UK commented Dec 5, 2024

Would this also apply to the instance in the Concise Problem Details? For instance:

{
  / title /         -1: "Not Found",
  / detail /        -2: "No Signed Statement found with the specified ID",
  / instance /      -3: "urn:ietf:params:scitt:error:notFound",
  / response-code / -4: 404,
}

This is the only serious place where URNs are left

@SteveLasker SteveLasker added this to the Draft 03 milestone Dec 31, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants