Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upClarify where table 4 applies #975
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
littledan
Aug 17, 2017
Member
Isn't it used by ToPropertyDescriptor?
If this is the only place where it's used, I agree that it would be fine to move that logic into ToPropertyDescriptor, and instead say where Table 4 appears, "either this set of fields must exist, or that set".
|
Isn't it used by ToPropertyDescriptor? If this is the only place where it's used, I agree that it would be fine to move that logic into ToPropertyDescriptor, and instead say where Table 4 appears, "either this set of fields must exist, or that set". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kmiller68 commentedAug 16, 2017
Reading the spec it's very unclear to me where table 4 applies. In fact I find it actively misleading. In sections 18-26 + Annex B.2 table 4 no longer applies since it is overridden by the last couple paragraphs of Section 17. In fact, I can't find any place in the spec where it applies. Although, I may have missed something.
Does it make sense to make an editorial change and move the last couple paragraphs of Section 17 to where table 4 is now (and delete table 4 assuming it doesn't apply anywhere)?