Make output properties TRAPI compliant about answercoalesce HOT 5 CLOSED

i will correct.

from answercoalesce.

The TRAPI 1.1 spec does not specify the "attributes" property for result node bindings. the spec is generous in this case and will allow basically anything you put in there.

however, node normalization currently fails when a non-hashable type (in this case the attributes dict) is encountered while merging node data. in addition, node norm does not normalize any curie values in the results. Node normalization will have to be modified if this change is implemented.

it is not known at this time if any other downstream components would have an issue here as well.

from answercoalesce.

I think it makes sense to robustify nn to handle properties of this type, and to update the binding properties to match other trapi properties, even if it is not required.

from answercoalesce.

understood, thanks!

from answercoalesce.

What we're doing is TRAPI compliant, but we would like to make TRAPI require us to include standards around this part of the message. Phil is creating an issue in the TRAPI repo to add standards around attributes in this part of the message.

from answercoalesce.