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

cleaning up http spec #370

Merged
merged 8 commits into from
Aug 15, 2024
Merged

cleaning up http spec #370

merged 8 commits into from
Aug 15, 2024

Conversation

jiyoonie9
Copy link
Contributor

@jiyoonie9 jiyoonie9 commented Aug 14, 2024

changes

  • removed Exceptions as we're not conforming to exception types in tbdex error message struct
  • removed Authentication and Authorization headers for each protected endpoint description and added reference to top level Authentication heading that explains how bearer did authn works
  • Cleaning up tables
  • Removed wording in discoverability section about how serviceEndpoint should resolve to either API or DID, which implied that one must recursively resolve til they get a publicly addressable API URL. It is confusing and probably not something required by DID spec
  • Added example around idempotency key
  • Added explanation around serviceEndpoint

@jiyoonie9 jiyoonie9 changed the title cleaning up http spec [dnm] cleaning up http spec Aug 14, 2024
| ----------------- | ------------------------------------------------------------- |
| `id` | see [DID-CORE spec](https://www.w3.org/TR/did-core/#services) |
| `type` | `PFI` |
| `serviceEndpoint` | PFI's publicly addressable API endpoint |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we link this API endpoint to something?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 like to a spec?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done 766aba6

"createdAt": "2023-09-13T20:28:40.345Z",
"protocol": "1.0"
},
"data": {},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is data present even if it's a null value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep! order's data is empty.

"kind": "order",
"id": "order_01ha83pkgsfk6t1kxg7q42s48j",
"createdAt": "2023-09-13T20:28:40.345Z",
"protocol": "1.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this now be 2.0?

@jiyoonie9 jiyoonie9 changed the title [dnm] cleaning up http spec cleaning up http spec Aug 15, 2024
@jiyoonie9 jiyoonie9 merged commit a15e1be into main Aug 15, 2024
@jiyoonie9 jiyoonie9 deleted the http-spec-cleanup branch August 15, 2024 17:07
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.

5 participants