Menu

#10 USR descriptions

open
nobody
4
2005-02-23
2005-02-23
No

It would be useful to put some information into the
output that says where an underspecified description or
solution comes from. For an underspecified description,
this could be a sentence ID; for a solution, it could
be sentence ID + solution number. This would be quite
useful for keeping track of information flow.

There are different places where this information
should be put for different codec formats. In GXL there
is a graph/id attribute that is specifically for this
purpose. In other formats, the information could be put
into a comment.

If the input file for a convert or solve operation
already contains a description, the default should be
that it is passed on into the output file. It should
also be possible to specify the (base) description on
the command line; solution descriptions could still add
the solution number to this description string. When
both the input file and the command line specify a
description, the command line should win.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.