xmg-hhu / xmg-webgui Goto Github PK

This has many benefits, e.g., the undo history of codemirror is not deleted.

Scenario: Parsing a sentence in the XMG WebGUI parser that is supposed to be blocked by the frame type hierarchy, e.g. "the fence jumped".
Behavior: The viewer shows a frame for this sentence where the subject has two types that are specified in the frame type hierarchy to be incompatible.
Expected behavior: The parser should not generate a tree and frame for this sentence because the types "physical_object" and "animate" are specified in the frame type hierarchy to be incompatible.

The same grammar files and type hierarchy lead to the correct behavior in the XMG Ubuntu VM - the sentence is blocked, with the output:

Incompatible types: [physical_object-fence] and [animate-entity]
Frame unification failed, tree discarded

Included:

• Screenshot from XMG WebGUI output for "the fence jumped"
• Screenshot from Tulipa output in XMG Ubuntu VM for "the fence jumped"
• .mg files and .xml files with a minimal working example metagrammar illustrating the issue (renamed to .mg.txt and .xml.txt to circumvent GitHub's restriction for file uploads...)

frame_dimension.mg.txt
frame_dimension.xml.txt
lemma.mg.txt
lemma.xml.txt
morph.mg.txt
morph.xml.txt
syn_dimension.mg.txt
syn_dimension.xml.txt

I realised that the viewer crashes when seeing atomic disjunctions as values of features, as in the following feat for example:

               <f name="mode">
                  <vAlt coref="@AD4">
                    <sym value="ind"/>
                    <sym value="subj"/>
                  </vAlt>
                </f>

The error is apparently in xmgview.js, line 423:

value.setAttribute("x", maxlengthFeatures + 10); //padding

The dimension is not displayed yet by the viewer. It would just be an additional feature structure, but I am not sure where it should be shown (directly next to the tree or in its own screen section).

--> https://github.com/spetitjean/TuLiPA-frames

In a grammar with trees and frames, if some of the entries contain no frame, their selection cause the frames of the other entries to be ignored.
As long as entries with tree+frame are selected, the display works fine, it is only when a tree-no_frame entry is selected that frames stopped being displayed.

Files are stored in folders with random name. Their name can be used as permanent identifier of projects.
This also enables one to upload and edit larger projects consisting of several files.

When no frame description is given, the viewer does not display the entry.
To be more precise, an xml with:

...
</tree>
<frame/>
<interface>
...

displays an empty frame while one with the following crashes:

...
</tree>
<interface>
...

Fixing this should allow to see all the grammars created with XMG1 (the syntactic part at least).

Before clicking on a button on the left pane in order to view the corresponding solution, information about the metagrammar should be included within the content frame, if available.

It would be nice to have a page where all publicly available metagrammars are listed. It could be only a list of links to repositories or the actual grammars directly viewable/editable through the WebGUI (a bit like what is now done for XTAG).

Prints the predicate semantics when provided (in the frame box). Example:

    <semantics>
      <literal negated="no">
        <label>
          <sym value="@V18"/>
        </label>
        <predicate>
          <sym varname="@V19"/>
        </predicate>
        <arg>
          <sym varname="@V4"/>
        </arg>
        <arg>
          <sym varname="@V17"/>
        </arg>
      </literal>
    </semantics>

Prints the name (property) of nodes when provided:
<node type="foot" name="Sf">