Larry,
I'll probably regret this, but I can't
resist the opportunity to stir the pot. Your example (see below) seems
contrary to your position that information such as OSPF interface metrics and
dead intervals should be attributes, not elements.
Keith
Allen
SBC
Technology Resources
9505
Arboretum Blvd.
Austin, TX 78759
(512)
372-5741
kallen@tri.sbc.com
-----Original Message-----
From: Larry Menten
[mailto:lmenten@lucent.com]
Sent: Tuesday, May
13, 2003 3:08 PM
To: netconf
Subject: Re: Is DOM vs SAX a red
herring?
Keith,
To represent the transaction in multiple parts the target has to be identified.
We have used XPath expressions for this purpose as in the following example:
<transaction
id="29">
<deleteRequest
opId="2"
select="/root/configuration/protocol/ospf/area[@id='0']" />
<deleteRequest opId="1"
select="/root/configuration/protocol/ospf/area[@id='3']" />
<addRequest opId="3"
select="/root/configuration/protocol/ospf">
<area id="4">
<interface id="ge-2/2">
<authentication-key>
<keyname>gargoyle</keyname>
<key-id>3</key-id>
</authentication-key>
<metric>1</metric>
<hello-interval>10</hello-interval>
<dead-interval>40</dead-interval>
<retransmit-interval>10</retransmit-interval>
<transit-delay>5</transit-delay>
</interface>
</area>
</addRequest>
<addRequest opId="4"
select="/root/configuration/protocol/ospf/area[@id='2']/interface[@id='ge-1/5']">
<dead-interval>40</dead-interval>
</addRequest>
<addRequest
opId="5" select="/root/configuration/protocol/is-is">
<area id="5"></area>
</addRequest>
<addRequest opId="6"
select="/root/configuration/protocol/ospf/area[@id='1']">
<label-switched-path id="to-SFO">
<metric>15</metric>
</label-switched-path>
</addRequest>
<replaceRequest opId="7"
select="/root/configuration/protocol/ospf/area[@id='6']/label-switched-path[@id='to-SFO']">
<metric>20</metric>
</replaceRequest>
</transaction>
Larry
Larry Menten Lucent Technologies/Bell Laboratories
Phone: 908 582-4467 600 Mountain Avenue, Murray Hill, NJ 07974 USA