[MPEG-OTSPEC] [EXTERNAL] Re: Text of ISO/IEC 14496-22/CD is now available for review

Peter Constable pconstable at microsoft.com
Thu Oct 3 01:33:30 CEST 2024


Murata:

The Directives (Part 2, clause 7) are clear about statements regarding requirements (use “shall” or “shall not”), recommendations (use “should” / “should not”) and permission (use “may”). It also describes words to use to describe possibilities: use “can” or “cannot”.

However, the latter doesn’t adequately cover the scenario of possibility of a non-event. “Can” means that an event could occur — >0% possibility; “cannot” means the event will not occur — 0% possibility. But it doesn’t recommend language when you want to advise the reader of <100% possibility, i.e., the possibility the event does not occur. While I haven’t checked all occurrences of “may not”, the occurrences I did check were all attempting to state the possibility of non-occurrence.

If you are aware of terminology guidance in the Directives for that situation, I’d be interested to know where it is.



Regards,
Peter Constable

From: mpeg-otspec <mpeg-otspec-bounces at lists.aau.at> On Behalf Of MURATA via mpeg-otspec
Sent: Friday, July 12, 2024 4:37 PM
To: MPEG OT Spec list (mpeg-otspec at lists.aau.at) <mpeg-otspec at lists.aau.at>
Subject: [EXTERNAL] Re: [MPEG-OTSPEC] Text of ISO/IEC 14496-22/CD is now available for review

To the editors,

I have not read this CD carefully yet, but I am happy to report that neither "MUST" nor "must" appears in this document.

Unfortunately, "may not" is still used.  I will try to make JP raise a comment.

While editing the OOXML specification (ISO/IEC 29500-1, 2, 3, and 4), ISO instructed SC34/WG4 not to use normative modal verbs (such as "shall", "may", and "should") in non-normative descriptions such as examples and notes.  So, I wrote a program for enumerating all such occurrences.  I will modify this program and use it for this document.

Regards,
Makoto

2024年7月12日(金) 5:10 Vladimir Levantovsky via mpeg-otspec <mpeg-otspec at lists.aau.at<mailto:mpeg-otspec at lists.aau.at>>:
Dear all,

The text of the Committee Draft of the 5th edition ISO/IEC 14496-22/CD "Open Font Format" is now available for download and review:
https://www.mpeg.org/wp-content/uploads/mpeg_meetings/146_Rennes/w23797.zip

Once the ballot is open, any changes you wish to make in the current text need to be submitted via your respective National Bodies as comments, using the following ISO commenting template<https://www.iso.org/resources/publicly-available-resources.html?t=MGTmD5TwK496A_y6JsbrKdnDBmIZ6L0rvjNNXYvKmXhIpfLuCJx5JQWQqL5GcGPw&view=documents#section-isodocuments-top>. The CD text is available for download as both "tracked changes" and "clean" versions - when submitting comments, please reference the clean version of the text for clarity and correct page number references.

Please note that if the proposed change requires a substantial amount of text to be replaced, it is allowed to submit a comment referencing a future input contribution document with detailed proposed changes. Any such document would have to be registered and uploaded in advance - to reserve the document number and provide comments prior to ballot closing date (which is yet to be announced).
Please also note that different National Bodies have their own additional processes for comments submission and may impose earlier deadlines than the ballot closing date.

Thank you for your contributions and hard work!
Vladimir

_______________________________________________
mpeg-otspec mailing list
mpeg-otspec at lists.aau.at<mailto:mpeg-otspec at lists.aau.at>
https://lists.aau.at/mailman/listinfo/mpeg-otspec


--
 --
慶應義塾大学政策・メディア研究科特任教授
村田 真
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20241002/a67064d2/attachment-0001.htm>


More information about the mpeg-otspec mailing list