Thanks for the ideas Anton, I'm happy with using the word cookie. It works for me. :-)
To me, there doesn't seem to be a good reason to lean towards using XML or pseudo XML. I would prefer to avoid any possibility of nested tags etc. We could use [] or <> for tagging, just something to show opening and closing would be good. Escape characters need to be defined. I also like the idea of a vendor tag. It would make for simple parsing and identifying of log files. Maybe a vendor tag and a sub vendor tag. i.e. [vendor=Cisco] [vendor.sub=pix6.3(1)] If we allow duplicate tags, then we need to discuss which tag takes priority. Is the last tag or first tag the one we use? What about tag naming conventions? Do we use VendorSub or vendor_sub or Vendor_Sub or vendor.sub? If all tags are US ASCII then we can convert the case easily for string matches. If they are Unicode and not easily convertible to US ASCII then how to we convert case? Cheers Andrew
