It's unclear whether the second part of that sentence means that the concept of application-specific directives needn't be supported, or that particular application-specific directives needn't be supported, although the latter seems more reasonable to me.
I propose removing noodles::gff::directive::ParseError::InvalidName, and instead introduce something like noodles::gff::directive::ApplicationSpecific(ApplicationSpecificDirective), where ApplicationSpecificDirective holds the (custom) name of the directive, and a free-form String value.
According to the GFF spec, "Application specific directives are allowed, but are not required to be supported by parsers".
It's unclear whether the second part of that sentence means that the concept of application-specific directives needn't be supported, or that particular application-specific directives needn't be supported, although the latter seems more reasonable to me.
I propose removing
noodles::gff::directive::ParseError::InvalidName
, and instead introduce something likenoodles::gff::directive::ApplicationSpecific(ApplicationSpecificDirective)
, whereApplicationSpecificDirective
holds the (custom) name of the directive, and a free-formString
value.