Re: CAP-12-e: Alarms and SEQUENCE

[email protected] wrote:

>
> Doug wrote on 10/21/2003 03:02:57 PM:
> > Yes you do seem to understand why removing SEQUENCE breaks MODIFY
> > of VALARMS. So I too do not want to break MODIFY of VALARMS.
>
> Actually thats not what I said but Ive already pointed that out.   In 
> the interest of resovling this quicker I took time to go reread 
> CAP-12-e, Section 10.9 MODIFY Command again to see if I had just 
> missed something originally.  After doing this I find that I still 
> disagree with Dougs assertion that removing SEQUENCE from VALARMs 
> breaks MODIFY.
>
> Lets take a look at the text and example to see why it does not break 
> MODIFY.  First off, the command says (in part): 


Better yet, an example of when MODIFY breaks.

Take TWO VLARMS that are identical in one component.
Withou a unique identifier  - you can not uniquly identify  the 2nd 
instance.
Now show me an example where you can without a unique identifier
replace the ACTION in the secoond valarm and make it antother value.


-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
[email protected]                 | Office: (208)520-4044
http://Royer.com/People/Doug   |    Fax: (866)594-8574
                               |   Cell: (208)520-4044

               We Do Standards - You Need Standards