Correctly validate maxInclusive datatypes

[austinmatherne-wk]

Reason for change

The max values used for byte, unsignedByte, short, unsignedShort datatypes were all one too low. The facets for these datatypes are maxInclusive not maxExclusive.

byte

byte is ·derived· from short by setting the value of ·maxInclusive· to be 127 and ·minInclusive· to be -128. The ·base type· of byte is short.

unsignedByte

unsignedByte is ·derived· from unsignedShort by setting the value of ·maxInclusive· to be 255. The ·base type· of unsignedByte is unsignedShort.

short

short is ·derived· from int by setting the value of ·maxInclusive· to be 32767 and ·minInclusive· to be -32768. The ·base type· of short is int.

unsignedShort

unsignedShort is ·derived· from unsignedInt by setting the value of ·maxInclusive· to be 65535. The ·base type· of unsignedShort is unsignedInt.

Description of change

Use maxInclusive checks for byte, unsignedByte, short, and unsignedShort.

Steps to Test

CI

review:
@Arelle/arelle

[aviary3-wk]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[stevenbronson-wk]

Looks like this fixes #929.