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

Inverse context creation: meaning of (might be null) for an optional field #631

Open
ZLghkA opened this issue Feb 2, 2025 · 0 comments
Open

Comments

@ZLghkA
Copy link

ZLghkA commented Feb 2, 2025

Hello,

The inverse context creation indicates that a language and direction mappings of a term definition (both being optional strings) might be present and null, in 4.3.2, steps 3.13), 3.14) and 3.15). In the definition of a term definition, section 4.1, there are optional strings. Should they be documented as optional nullable strings (not present, null, or strings)? Are there other fields that may be null too?

Best regards,

Vivien

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant