Tinderbox imports OPML files dropped onto Tinderbox views, and also reads OPML outlines. Note that Omnigroup's apps, e.g. OmniOutliner, popularised OPML use but did so using non-standard additions. So when using OPML, do not assume all OPML is the same: read the OPML specification.
When Tinderbox parses a pasted or drag-dropped OPML, the source OPML filename is used as the name of the container holding the tree of notes parsed from the HTML. The OPML source code is not retained in the TBX document as the data is now imported and the OPML code would simply constitute unwanted file bloat. If the user also witness to store the OPML code, that would need to be pasted into a new note's $Text to avoid triggering the parser.
If an OPML file has extended outline attributes, and if the extensions do not conflict with Tinderbox attributes, then Tinderbox will make a user attribute for each of the extended attributes. The default 'text' attribute is mapped to $Name [sic]. The non-standard '_note' attribute popularised by OmniOutliner is, if found, mapped to $Text with ' ' being parsed as paragraph breaks.
The user attributes will initially be defined as Displayed Attributes as well, allowing for easier inspection of the extended data.
OPML support includes Projekt extensions.
The non-standard but generally used OPML '_status' attribute data is mapped to $Checked which of course can be displayed in outline view as a tick box (good for 'to do' lists).
OmniOutliner exported OPML: see further detail.
Note that the OPML <expansionState> element is not supported. By default, any new container notes created from the imported OPML data are all collapsed in Outline view.
Tinderbox will expect dates to be in RFC 822 form in accordance with the OPML spec: see more.
See also—notes linking to here: