-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sortinfo in DMRS #33
Comments
In #34 I addressed the issue, but I just checked #21 and in a comment there is this XML-serialization: <dmrs cfrom="-1" cto="-1" top="10003" index="10003">
<node nodeid="10000" cfrom="0" cto="13">
<gpred>udef_q</gpred>
<sortinfo />
</node>
<node nodeid="10001" cfrom="0" cto="6">
<realpred lemma="mask" pos="v" sense="1" />
<sortinfo SF="prop" TENSE="untensed" MOOD="indicative" PROG="bool" PERF="-" cvarsort="e" />
</node>
...
</dmrs> So the "sortinfo" is still being outputted even though there is no information in it. If we want the RDF serialization to be as close as the XML one, I think we should let the code generate this node. |
Let us see what will be the comments in delph-in/docs#27 |
OK, Michael presented some arguments for not changing the XML Schema, but I still believe that RDF needs different decision since it doesn't make sense to have a node without any property besides its type. Moreover. RDF validation and schema are complete different from XML. So this issue is about:
|
we should not produce a node that doesn't have any info besides its type...
The quantifiers seem to not carry sortinfo information. See here
The text was updated successfully, but these errors were encountered: