You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i've found a handful of times that i need to mark EXT elements with TYPE information to help reader/writer tooling. This will be a single string property that can contain any valid string text. the meaning of that value can be documented when documenting the EXT element itself.
<extid="hatSize"type="enum"value="large medium small really-big" />
If type value range is not defined by the specification then it adds just a little value, because it is expected that a client/processor 'knows' but if a client knows then it has to know an unspecified type attribute as well.
if the type value range is defined then I'm thinking maybe introducing other elements could be more readable.
e.g.
<enumid="hatSize"value="...."/>
I personally like keeping the spec simple. Let's discuss it.
i've found a handful of times that i need to mark EXT elements with TYPE information to help reader/writer tooling. This will be a single string property that can contain any valid string text. the meaning of that value can be documented when documenting the EXT element itself.
this may also help with issue #8
The text was updated successfully, but these errors were encountered: