Re: [office] Fwd: ISO requirements and edits to consider to ODF

[Jamie Clark <jamie.clark@oasis-open.org>]

Thanks so much to Patrick and the TC for working with us on this. In case it's not obvious, we're proposing to take a fairly assertive posture ... After all, the JTC 1 rules were intentionally changed to remove the formal and formatting (Directives Part 2) requirements, for subsequent versions of previously approved IS PAS submissions.Â

So we expect to leave behind the old practice of massive rewrites and reformatting! As we understand it, your final output will be "sandwiched" between JTC1 front and back pages, as was the case with the first submissions.

Still, we are suggesting making volunteer changes, as a good citizen, that seem appropriate and reasonably easy, to provide JTC 1 and its voting national bodies with semantic harmony and "look and feel" accommodations.

PS I thought I read that MathType is a plug-in to relatively recent versions of Microsoft Word, so maybe that will be easier than it sounds? We're advocating volunteer compliance with elements that probably matter the most to production composition, as promoting global relevance goals. At the risk of Âbelaboring this to experts who have far more experienced people than us, diagrams and formulae fall in that class.  ÂWe are mindful that there's always the possibility that national bodies will choose to transpose an IS into translated editions, according to ISO's own appropriate processes. Obviously we want to do things that make that easier, if they're readily feasible.

cordially ÂJamie

Sent from my mobile

(From RSAc)

On Wed, Jun 8, 2022 at 10:43 Patrick Durusau <patrick@durusau.net> wrote:

Greetings!

Progress on ODF 1.3!

Mostly checking to make sure we meet all the requirements.

Doing a conversion using Word to see how it handles formulas into
MathType, will report on that next Monday.

Agenda for next Monday will follow soon.

Hope everyone is having a great week!

Patrick



-------- Forwarded Message --------
Subject:Â Â Â Â Re: ISO requirements and edits to consider to ODF
Date:Â ÂWed, 8 Jun 2022 11:48:31 -0400
From:Â ÂChet Ensign <chet.ensign@oasis-open.org>
To:Â Â ÂPatrick Durusau <patrick@durusau.net>
CC:Â Â ÂJamie Clark <jamie.clark@oasis-open.org>



Sure - just wanted to start with you.

/chet

On Wed, Jun 8, 2022 at 11:43 AM Patrick Durusau <patrick@durusau.net> wrote:

  I can share this will the TC, yes? Thought I should ask first.
  Thanks guys!

  Chet, Jamie,

  Thanks!

  Tentative responses below:

  On 6/8/22 10:46, Chet Ensign wrote:
  Â> Hi Patrick,
  Â>
  Â> Jamie and I have been reviewing the ISO rules and Part 2
  directives to
  Â> determine what changes we may want to suggest making
  Â> (https://www.iso.org/sites/directives/current/part2/index.xhtml and,
  Â> in particular,
  Â>
  https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor140).

  Â> While Part 2 has a big list of requirements, Annex F now says very
  Â> clearly that PAS and Fast Track submissions are generally exempted
  Â> from Directives Part 2, subject to bargaining with the publications
  Â> office.
  Â>
  Â> In that spirit of bargaining, we'd like to suggest the following
  Â> changes to make submission go smoother and then see if our inside
  Â> mentors and editors at JTC1 believe it's acceptable.
  Â>
  Â> - Submit the documents in MS Word. Would this pose a problem for
  you?
  Â> I realize that, with your extensive use of math expressions and
  Â> cross-references, there might be some glitches from 'save as.' But
  Â> while we've submitted both ODF and DOCX in the past, their
  production
  Â> process relies on DOCX, so providing that format could remove one
  Â> obstacle.
  Â>
  We'll have to test that and compare the results but I suspect that will
  be successful. But that's a suspicion only.
  Â> - Looks to me like you've used ISO keywords throughout already, yes?
  Yes.
  Â>
  Â> - We suggest making some nominal changes to the organization of the
  Â> content to align with ISO's requirements
  Â>
  (https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor140)
  Â>
  Â>  Â-- Modify part titles (if needed) to meet section 11 Title
  requirements
  Â>
  Â>  Â-- Make sure Introductions do not contain any normative
  statements
  Â> (section 13 Introduction)
  Â>
  Â>  Â-- Compare Scope sections with the requirements of section 14
  Scope
  Â>
  Â> - Hanging paragraphs, section 22.3.3 - I know you are ferocious on
  Â> that practice generally and I didn't see any instances of it but
  might
  Â> be worth a fast check
  Â>
  Â> - Table/figure numbering - We ought to comply with tables and
  figures
  Â> numbering as described in Part 2, Secs 28.4 and 29.3-29.4. It looks
  Â> like we do but worth reviewing
  Â>
  Â> - Note Sec 33.1 (conformity assessment) -- is there anything in the
  Â> current ODF v1.3 that does not meet this test?
  Â>
  Â> - Suggest renaming the Non Normative References section to
  Â> 'Bibliography' however not moving it to be the final annex so as not
  Â> to mess up your ToC numbering
  Â>
  Will verify all of the above meets the requirements.
  Â> - Part 2 requires mathematical expressions to be done using MathType
  Â> v6.9 or higher. Expressions done as Images or using LaTex, MathML,
  Â> MathCAD, or Word drawings won't be accepted. Does ODF v1.3 meet that
  Â> requirement? If not, we can ask if we can ship it our way now.
  Â>
  Interesting question and one to which I don't have an immediate answer.
  Here's what one implementation says about converting to and from
  MathType:

  *****

  For formulas, any embedded MathType objects must not exceed the
  MathType
  3.1 specifications to be successfully loaded and converted. Information
  on MathType format can be found at
  https://docs.wiris.com/en/mathtype/office_tools/microsoft_office.

  *****

  What I don't know and will have to test, is whether the import into
  Word
  converts the ODF math formulas into MathType, whatever version. If that
  happens and it happens successfully, this may not be an issue
  because of
  your first request to convert to MS Word. But, that's speculation on my
  part.

  Â> - All graphics must be included as separate files in a revisable
  Â> (vector-drawn) graphics format. I saw only one graphic that looked a
  Â> bit like an I Ching hexagram so that doesn't seem like a big deal.
  Â>
  There are more graphics than one, but I don't have a precise count.
  Will
  have to check on that with the conversion as well.
  Â> - Jamie notes that, as a rule, ISO doesn't like lists of
  contributors.
  Â> So perhaps modify Appendix A to be a link to the OASIS copy. E.g.
  'For
  Â> the list of participants in the creation of the standard, see <link>.
  Â>
  Understood.
  Â> - Consider renaming 'Appendix' to 'Annex', the ISO term.
  Â>
  Sure.
  Â> Have a look and let us know what you think. Unless the math
  Â> requirement causes problems, we should be OK.
  Â>
  I'll try to experiment with the conversion and math stuff this week.

  This should keep me out of trouble for a day or so. ;-)

  Patrick


  Â> /chet
 Â* * *Â
  ÂÂ
  --
  Patrick Durusau
  patrick@durusau.net
  Technical Advisory Board, OASIS (TAB)
  Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
* * *


--



   ChetÂEnsign

Chief Technical Community Steward

OASIS Open



    +1 201-341-1393 <tel:+1+201-341-1393>

    chet.ensign@oasis-open.org

    www.oasis-open.org <https://www.oasis-open.org>

--

James Bryce Clark

General Counsel

OASIS Open

	jamie.clark@oasis-open.org
	Xing  LinkedIn  Twitter
	Setting the standard for open collaboration.Â