emkornfield commented on PR #455: URL: https://github.com/apache/arrow-go/pull/455#issuecomment-3140838383
> I think we can update the wording "When typed_value is omitted, value must be required." => "When typed_value is omitted, value must be present.". both typed_value and value fields should always be optional but we are saying it's required and that is causing the confusion. I think the spec tried to be careful with wording, but there is a lot of semantic overlap between required/missing/optional. Having a glossary for these terms and doing an audit of the spec to make sure they are used consistently would help. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
