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

Add workaround for missing content types in response fields, use correct affordance keys #14

Merged
merged 8 commits into from
Nov 29, 2024

Conversation

JKRhb
Copy link
Member

@JKRhb JKRhb commented Nov 26, 2024

This PR includes the workaround needed to resolve #13. It is based on a similar PR (vaimee/zion#52) I submitted to ZION dealing with the same issue.

While working on this issue, I noticed that the TDD's TD did not use the correct affordance keys to be compliant with the Discovery specification (c.f. the Thing Model in section 7.3.2.4). Therefore, I also adjusted the keys to improve the directory's interoperability.

@JKRhb JKRhb force-pushed the fix-td-validation branch 2 times, most recently from fdfcf95 to 1ebf4eb Compare November 26, 2024 10:27
@JKRhb JKRhb marked this pull request as ready for review November 26, 2024 10:49
@JKRhb
Copy link
Member Author

JKRhb commented Nov 26, 2024

This PR now also contains the changes made by @Murloc6 in their PR and should only be merged afterward.

@wiresio wiresio merged commit 5e2f4c1 into main Nov 29, 2024
1 of 3 checks passed
@wiresio wiresio deleted the fix-td-validation branch November 29, 2024 07:43
@wiresio
Copy link
Member

wiresio commented Nov 29, 2024

Thanks Jan!

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.

Implement workaround for mandatory response contentType
2 participants