Unexpected OutlineGroup element

AlexeiSo 81 Reputation points
2021-12-07T13:21:57.107+00:00

Hello!
I have a file in OneNote Online format.
This file has unexpected structure: there is a table cell with OutlineGroup node as a child.
But [MS-ONE], 2.2.55 ElementChildNodesOfTableCell states that this situation can't happen: only OutlineElement node can be a child of table cell.

The ElementChildNodesOfTableCell structure is an array of ObjectID structures (section 2.1.6) that specifies outline elements (section 1.3.2.2) in a table cell. The array MUST contain at least one ObjectID structure and each ObjectID structure in the array MUST reference a jcidOutlineElementNode element.
Can I get a clarification regarding this case?
Thanks!
PS I can share a sample file via e-mail.

Office Open Specifications
Office Open Specifications
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Open Specifications: Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
127 questions
{count} votes

Accepted answer
  1. Tom Jebo 1,991 Reputation points Microsoft Employee
    2022-02-04T18:58:45.727+00:00

    Hi @AlexeiSo ,

    I did finally nail down the story on this. OneNote 2010 and later versions (might be in earlier versions as well but MS-ONE only scopes to OneNote 2010) do allow for both jcidOutlineElementNode and jcidOutlineGroup child elements of a jcidTableCellNode. They at least consider the file format valid when this happens. I'm not sure how to accomplish this in OneNote UI. I believe the UI works to remove these in most cases but it is considered technically valid.

    Therefore, I will file a bug against MS-ONE to propose the addition of jcidOutlineGroup as a possible jcidTableCellNode child to the specification so as not to confuse implementers parsing and validating.

    Let me know if you agree with this.

    Best regards,
    Tom Jebo
    Sr Escalation Engineer
    Microsoft Open Specifications Support


0 additional answers

Sort by: Most helpful