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
Well, within reason. I think a tag would be defined as a sequence of at least 2 alphanumerics, and is unique across case folding and numerals of the any digits. So
AB and ab fails the uniqueness requirement
AB1 and AB01 fails the uniqueness requirement
Implications:
identify tags by their presence in config file not by their syntax
tag inventory and audit can no longer assume tag syntax
optionally config has a re pattern to restrict tag formats - used when typing tags and when loading config & datafiles.
tags are case-folded and numeric sequences have leading 0's compressed away
sorting rules: hmmmm. Probably sort based on a canonical/sorting representation which pads all numeric sequences to - i dunno - ten digits or something; after that applies a simple alpha sort
tagid attributes:
mostly as-is, though want a 'sorting' representation
'.simple' -- the tag in its simplest form -- useful for comparing, and this is what would be used in tables like the invetory matrix etc
'.sorting' -- the tag with all its numeric sequences expanded to some long number of digits, so that a simple alpha compare/sort will then work
Tag inventory
tagid tagid tagid tagid tagid tagid tagid
In Out Ret In - Out Out
tagid tagid tagid tagid tagid tagid tagid
In Out Ret In - Out Out
where the layout is determined by the longer of the longest tagid (though at least 2); then
simply run together for the length of a line
Audit matrix
More or less the same - but do not need the statuses
Web reporting
Tag history and such may not have meaning in the same way. Consider the wen reports and recognize
The text was updated successfully, but these errors were encountered:
Current TT tags are alpha-alpha-digit-[digit*]
Want to allow any kind of tag syntax
Well, within reason. I think a tag would be defined as a sequence of at least 2 alphanumerics, and is unique across case folding and numerals of the any digits. So
Implications:
Tag inventory
where the layout is determined by the longer of the longest tagid (though at least 2); then
simply run together for the length of a line
Audit matrix
More or less the same - but do not need the statuses
Web reporting
Tag history and such may not have meaning in the same way. Consider the wen reports and recognize
The text was updated successfully, but these errors were encountered: