Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

60-81-identifiers #84

Merged
merged 6 commits into from
Jan 12, 2022
Merged

60-81-identifiers #84

merged 6 commits into from
Jan 12, 2022

Conversation

pvdbosch
Copy link
Contributor

Pull request for #60 and #81 .

New section "Identifier" under document archetype.

I moved some paragraphs from the "API specifications" chapter to avoid duplication, and put a reference in its place.

@pvdbosch
Copy link
Contributor Author

pvdbosch commented Oct 21, 2021

REST WG reviewed PR.

One comment from Bert in WG, on designing new identifiers:

  • identifiers may get widespread usage outside of the initial API where it was defined, e.g. in client's system, document administration, ...
  • think about governance and lifecycle of the identifiers
  • Designing identifiers in a URI structure (cfr ICEG URI standard) is useful because it makes the identifier context-independent and more self-descriptive. A REST API may choose to use a shorter API-local form of a URI identifier because of practical considerations.

I'll add this to the PR and submit to review to Bert.

@pvdbosch
Copy link
Contributor Author

Updated the PR based on Bert's feedback; in the "choice of identifier" section

@pvdbosch
Copy link
Contributor Author

reviewed and approved by WG

@pvdbosch pvdbosch merged commit b2e329f into master Jan 12, 2022
@pvdbosch pvdbosch deleted the 60-81-identifiers branch May 27, 2024 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

guidelines on new resource identifiers
1 participant