Comments on: Namespaces in XML http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/ The act of making love, tenderly. Wed, 01 Feb 2012 18:16:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Liz Trojan http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-127430 Liz Trojan Wed, 15 Dec 2010 00:40:11 +0000 http://tenderlovemaking.com/?p=237#comment-127430 I have a namespace issue that I don't know how to resolve. I know you were thinking(hoping?) that this thread would die a quiet death but no such luck. I'm attempting to merge an XML fragment into a larger XML doc. Below is my source. require 'rubygems # Here is how I generate the fragment VEfragDoc = Nokogiri::XML::Builder.new do |xml| xml.root('xmlns' => 'http://www.scte.org/schemas/130-3/2008a/adm', 'xmlns:core' => 'http://www.scte.org/schemas/130-2/2008a/core', 'xmlns:xsi' => 'http://www.w3.org/XMLSchema-instance', 'xsi:schemaLocation' => 'http://www.scte.org/schemas/130-3/2008/adm SCTE130-3_2008.xsd', 'messageId' => @messageId, 'version' => '1.0', 'identity' => 'adm', 'system' => 'adm'){ xml.ViewerEvent(:type => "fast-forward", :time => "2010-06-29T19:59:50.337+00:00"){ xml.Spot { xml['core'].Content { xml['core'].AssetRef(:assetID => "CCDN2008010100090008", :providerID => "adcontent.test.com") xml['core'].Tracking "07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19" } xml.SpotNPT "22.865", :scale => "10.0" } } } end.doc VEfragment = VEfragDoc.root.children # Then I create the main document: PSEdoc = Nokogiri::XML::Builder.new do |xml| xml.root('xmlns' => 'http://www.scte.org/schemas/130-3/2008a/adm', 'xmlns:core' => 'http://www.scte.org/schemas/130-2/2008a/core', 'xmlns:xsi' => 'http://www.w3.org/XMLSchema-instance', 'xsi:schemaLocation' => 'http://www.scte.org/schemas/130-3/2008/adm SCTE130-3_2008.xsd', 'messageId' => @messageId, 'version' => '1.0', 'identity' => 'adm', 'system' => 'adm'){ xml.PlacementStatusEvent(:type => "startPlacement", :time => "2010-06-29T19:59:50.337+00:00"){ xml.Spot { xml['core'].Content { xml['core'].AssetRef(:assetID => "XPTL2008010100090104", :providerID => "adcontent.test.com") xml['core'].Tracking "07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19" } xml.SpotNPT "0.0", :scale => "1.0" } } xml.PlacementStatusEvent(:type => "endPlacement", :time => "2010-06-29T20:59:50.340+00:00"){ xml.Spot { xml['core'].Content { xml['core'].AssetRef(:assetID => "XPTL2008010100090104", :providerID => "adcontent.test.com") xml['core'].Tracking "07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19" } xml.SpotNPT "15.694", :scale => "0.0" } } } end.doc # Insert the fragment into the main doc PSEdoc.xpath("//xmlns:PlacementStatusEvent[@type = 'startPlacement']").after VEfragment puts PSEdoc.to_xml 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 0.0 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 22.865 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 15.694 I had hoped for a merged file that looked like the following. Unfortunately some namespace stuff has been tacked on to the . 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 0.0 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 22.865 07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19 15.694 Any help with figuring out how to deal with namespaces when merging xml files would be greatly appreciated. Liz I have a namespace issue that I don’t know how to resolve. I know you were thinking(hoping?) that this thread would die a quiet death but no such luck. I’m attempting to merge an XML fragment into a larger XML doc. Below is my source.

require ‘rubygems

# Here is how I generate the fragment
VEfragDoc = Nokogiri::XML::Builder.new do |xml|
xml.root(‘xmlns’ => ‘http://www.scte.org/schemas/130-3/2008a/adm',
‘xmlns:core’ => ‘http://www.scte.org/schemas/130-2/2008a/core',
‘xmlns:xsi’ => ‘http://www.w3.org/XMLSchema-instance',
‘xsi:schemaLocation’ => ‘http://www.scte.org/schemas/130-3/2008/adm SCTE130-3_2008.xsd’,
‘messageId’ => @messageId,
‘version’ => ’1.0′,
‘identity’ => ‘adm’,
‘system’ => ‘adm’){
xml.ViewerEvent(:type => “fast-forward”, :time => “2010-06-29T19:59:50.337+00:00″){
xml.Spot {
xml['core'].Content {
xml['core'].AssetRef(:assetID => “CCDN2008010100090008″, :providerID => “adcontent.test.com”)
xml['core'].Tracking “07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19″
}
xml.SpotNPT “22.865″, :scale => “10.0″
}
}
}
end.doc
VEfragment = VEfragDoc.root.children

# Then I create the main document:
PSEdoc = Nokogiri::XML::Builder.new do |xml|
xml.root(‘xmlns’ => ‘http://www.scte.org/schemas/130-3/2008a/adm',
‘xmlns:core’ => ‘http://www.scte.org/schemas/130-2/2008a/core',
‘xmlns:xsi’ => ‘http://www.w3.org/XMLSchema-instance',
‘xsi:schemaLocation’ => ‘http://www.scte.org/schemas/130-3/2008/adm SCTE130-3_2008.xsd’,
‘messageId’ => @messageId,
‘version’ => ’1.0′,
‘identity’ => ‘adm’,
‘system’ => ‘adm’){
xml.PlacementStatusEvent(:type => “startPlacement”, :time => “2010-06-29T19:59:50.337+00:00″){
xml.Spot {
xml['core'].Content {
xml['core'].AssetRef(:assetID => “XPTL2008010100090104″, :providerID => “adcontent.test.com”)
xml['core'].Tracking “07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19″
}
xml.SpotNPT “0.0″, :scale => “1.0″
}
}
xml.PlacementStatusEvent(:type => “endPlacement”, :time => “2010-06-29T20:59:50.340+00:00″){
xml.Spot {
xml['core'].Content {
xml['core'].AssetRef(:assetID => “XPTL2008010100090104″, :providerID => “adcontent.test.com”)
xml['core'].Tracking “07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19″
}
xml.SpotNPT “15.694″, :scale => “0.0″
}
}
}
end.doc

# Insert the fragment into the main doc
PSEdoc.xpath(“//xmlns:PlacementStatusEvent[@type = 'startPlacement']“).after VEfragment
puts PSEdoc.to_xml

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

0.0

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

22.865

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

15.694

I had hoped for a merged file that looked like the following. Unfortunately some namespace stuff has been tacked on to the .

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

0.0

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

22.865

07ecc860-d4a3-012d-0c3f-005056c00008_1_3_19

15.694

Any help with figuring out how to deal with namespaces when merging xml files would be greatly appreciated.
Liz

]]> By: mario http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-116604 mario Mon, 14 Jun 2010 18:23:48 +0000 http://tenderlovemaking.com/?p=237#comment-116604 Aaron, This article was REALLY helpful for me. Nokogiri is a godsend and i just wanted to thank you for writing in a way that makes it fun/easy to understand while still driving home the key points. Aaron,

This article was REALLY helpful for me. Nokogiri is a godsend and i just wanted to thank you for writing in a way that makes it fun/easy to understand while still driving home the key points.

]]> By: Evan Reeves http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-110639 Evan Reeves Wed, 24 Feb 2010 18:54:43 +0000 http://tenderlovemaking.com/?p=237#comment-110639 I feel like an idiot for not having discovered this explanation earlier (here or anywhere else!). Thanks for this explanation and special thanks for giving Nokogiri examples. My Ruby n00b ass has a much better understanding now! I feel like an idiot for not having discovered this explanation earlier (here or anywhere else!). Thanks for this explanation and special thanks for giving Nokogiri examples. My Ruby n00b ass has a much better understanding now!

]]> By: Aaron Patterson http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-103647 Aaron Patterson Tue, 17 Nov 2009 18:45:02 +0000 http://tenderlovemaking.com/?p=237#comment-103647 @john yes, good catch. I will fix. Thanks! @john yes, good catch. I will fix. Thanks!

]]> By: john http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-103646 john Tue, 17 Nov 2009 18:37:13 +0000 http://tenderlovemaking.com/?p=237#comment-103646 Um, should this be doc.xpath, etc.? doc.xml('//tire') doc.xml('//aliceAuto:tire', 'aliceAuto' => 'http://alicesautosupply.example.com/' ) Um, should this be doc.xpath, etc.?

doc.xml(‘//tire’)
doc.xml(‘//aliceAuto:tire’,
‘aliceAuto’ => ‘http://alicesautosupply.example.com/‘
)

]]> By: Jeff Smick http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-77052 Jeff Smick Sun, 17 May 2009 19:16:44 +0000 http://tenderlovemaking.com/?p=237#comment-77052 <p>How would I find the inventory node for a specific namespace?</p> <p>If we put the two together: </p> <p>What query would I use to find Bob's inventory?</p> How would I find the inventory node for a specific namespace?

If we put the two together:

What query would I use to find Bob’s inventory?

]]> By: Bruce http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-75941 Bruce Thu, 07 May 2009 01:38:53 +0000 http://tenderlovemaking.com/?p=237#comment-75941 <p>Maybe a dumb question, but do you have to declare the bindings on every xpath method call, or can you register them independently (which can be useful, particularly if you're dealing with a lot of content with default namespaces)?</p> Maybe a dumb question, but do you have to declare the bindings on every xpath method call, or can you register them independently (which can be useful, particularly if you’re dealing with a lot of content with default namespaces)?

]]> By: Aaron Patterson http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-74520 Aaron Patterson Fri, 24 Apr 2009 01:27:36 +0000 http://tenderlovemaking.com/?p=237#comment-74520 <p>@Dr Nic: You could, but then you would have to standardize on an attribute name. Everyone would have to agree on one particular attribute name to examine. If you gave me your XML document, you would have to tell me to examine the "type" attribute, where someone else might choose the "class" attribute. The namespace attribute is standardized.</p> <p>Not to mention in your example, the attribute value would have to be unique. I couldn't tell the difference between a car tire from Ford and a car tire from GM. ;-)</p> @Dr Nic: You could, but then you would have to standardize on an attribute name. Everyone would have to agree on one particular attribute name to examine. If you gave me your XML document, you would have to tell me to examine the “type” attribute, where someone else might choose the “class” attribute. The namespace attribute is standardized.

Not to mention in your example, the attribute value would have to be unique. I couldn’t tell the difference between a car tire from Ford and a car tire from GM. ;-)

]]> By: Dr Nic http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-74503 Dr Nic Fri, 24 Apr 2009 00:17:45 +0000 http://tenderlovemaking.com/?p=237#comment-74503 <pre><tire type='car'>...</tire></pre> <tire type='car'>...</tire> ]]> By: Dr Nic http://tenderlovemaking.com/2009/04/23/namespaces-in-xml/comment-page-1/#comment-74499 Dr Nic Thu, 23 Apr 2009 23:54:42 +0000 http://tenderlovemaking.com/?p=237#comment-74499 <p>So why namespacing vs element attributes?</p> <p>e.g. </p> <pre>...</pre> So why namespacing vs element attributes?

e.g. 

...
]]>