Robert Raszuk wrote: > Just to be clear: I am also OK with free form text with the few well > known and easy to machine parse keywords (in it).
the field should either be fully structured or free-form, and the explicit intent of this draft is free form, utf8. Having a half-way house is in nobody's interest because the discussion will then rat-hole on defining a new ad-hoc quasi-language, and the draft - if it ever gets turned into running code - will end up being a protocol soup which no-one will find satisying. If you feel it should be fully structured, then please feel free to submit an alternative draft to that effect. Nick _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
