Arvola, Thanks for taking the initiative to present these ideas to the cpa team. Comments: 1) Personally speaking, I had envisioned an attribute for DuplicateElimination that had the enumerated values: true, false, perMessage. For example, <DuplicateElimination inForce= true /> or <DuplicateElimination inForce= perMessage />. 2) The AckRequested issues could also be simplified with the same enumeration. For example <Ack requested= true signed= perMessage />. 3) Also, am I understanding correctly that you are proposing defaults for AckRequested such that: <AckRequested perMessageCharacteristics= perMessage includeInMessageHeader= false /> ... are these default values at odds with each other? If AckRequested is supposed to be decided on a per message basis, mustn't the info be included in the message header -- or am I misunderstanding the includeInMessageHeader attribute? 4) Also, please consider using another attribute name other than flag . Flag is not a very descriptive name. Dividing the element name AckRequested into an element Ack and an attribute requested like <Ack requested= perMessage /> is one way to get more descriptive attribute names -- perhaps there are others, as well. Once again, thanks for steaming forward with these issues. Bruce ============================================ Bruce Pedretti Hewlett-Packard Company Software Developer 6000 Irwin Road (856) 638-6060 Mt. Laurel, NJ 08054
http://www.hp.com/ ============================================