Ticket #136 (new enhancement)

Opened 3 years ago

Last modified 2 years ago

OMFOREIGN support in default.ntn

Reported by: clange Owned by: vzholudev
Priority: major Milestone: Release v1.3.1
Component: Presentation Version: v0.1.4
Keywords: Cc: kohlhase
Blocked By: Blocking:
Due to close: Include in GanttChart: no
Dependencies: Due to assign:

Description

At the moment, OMFOREIGN is not supported properly.

I don't exactly know how a proper rendering of OMFOREIGN should look, but I think it should simply be a copy of the child nodes. For example, whenever an application expects OpenMath? but gets something (XML or text) that is not OpenMath?, it can report an error like this:

<OME>
  <OMS cd="error" name="unexpected_..."/> <!-- the "error" symbol -->
  <OMFOREIGN>
    <!-- the unexpected content -->
  </OMFOREIGN>
</OME>

Particularly in the case of unexpected XML, OMFOREIGN must be used, as non-OpenMath? XML is not allowed inside OME. A practical scenario where this is needed is e.g. error handling in the integration of the formula editor with SWiM.

Change History

Changed 3 years ago by kohlhase

I think that the OMFOREIGN should not be presented at all. If we want to present it (e.g. in an error) then it should be presented verbatim as pre-formatted CDATA section.

Changed 3 years ago by clange

  • milestone set to Release v0.1.2

Changed 3 years ago by nmueller

  • due_assign YYYY/MM/DD deleted
  • version set to v0.1.3
  • due_close YYYY/MM/DD deleted
  • milestone changed from Release v0.1.2 to Release v0.1.3

Changed 3 years ago by nmueller

  • version changed from v0.1.3 to v0.1.4
  • milestone changed from Release v0.1.3 to Release v0.1.4

Changed 2 years ago by nmueller

  • owner changed from nmueller to vzholudev

Changed 2 years ago by dmisev

  • milestone changed from Release v0.1.4 to Release v0.1.5
Note: See TracTickets for help on using tickets.