Golang XML marshal两个相同的属性

huangapple
go评论122阅读模式
英文:

Golang XML marshal two identical attributes

问题

我被迫使用一些设计不良的 XML，我正在尝试将这个 XML 读入到一个 Go 结构中。这里是一些示例数据：

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <dictionary>
  3.     
  4.     <direction from="lojban" to="English">
  5.         <valsi word="cipni" type="gismo">
  6.             <rafsi>cpi</rafsi>
  7.             <definition>x1 is a bird of species x2</definition>
  8.             <notes></notes>
  9.         </valsi>
  10.         ...
  11.     </direction>
  13.     <direction from="English" to="lojban">
  14.         <nlword word="eagle" valsi="atkuila" />
  15.         <nlword word="hawk" sense="bird" valsi="aksiptrina" />
  16.         ...
  17.     </direction>
  18.     
  19. </dictionary>

我的问题是，我无法同时读取 <valsi> 节点和 <nlword> 节点，因为它们都包含属性 "word"：

  1. main.NLWord 字段 "Word" 的标签 "word,attr" 与字段 "Valsi" 的标签 "word,attr" 冲突

我开始觉得解组可能不是正确的方法，因为我理想情况下会以不同的方式组织数据。我应该使用其他方法读取 XML 并手动构建数据结构吗？

  1. type Valsi struct {
  2.     Word  string   `xml:"word,attr"`
  3.     Type  string   `xml:"type,attr"`
  4.     Def   string   `xml:"definition"`
  5.     Notes string   `xml:"notes"`
  6.     Class string   `xml:"selmaho"`
  7.     Rafsi []string `xml:"rafsi"`
  8. }
  10. // 制作这个 XML 结构的人需要受到痛苦的教训...
  11. type Collection struct {
  12.     From  string  `xml:"from"`
  13.     To    string  `xml:"to"`
  14.     Valsi []Valsi `xml:"valsi"`
  15. }
  17. type Vlaste struct {
  18.     Direction []Collection `xml:"direction"`
  19. }
  21. var httpc = &http.Client{}
  23. func parseXML(data []byte) Vlaste {
  24.     vlaste := Vlaste{}
  25.     err := xml.Unmarshal(data, &vlaste)
  26.     if err != nil {
  27.         fmt.Println("Problem Decoding!")
  28.         log.Fatal(err)
  29.     }
  30.     return vlaste
  31. }

希望这可以帮助到你。

英文:

I'm forced to work with some poorly designed XML, I'm trying to read this XML into a Go structure. Here's some sample data:

  1. &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
  2. &lt;dictionary&gt;
  3.     
  4.     &lt;direction from=&quot;lojban&quot; to=&quot;English&quot;&gt;
  5.         &lt;valsi word=&quot;cipni&quot; type=&quot;gismo&quot;&gt;
  6.             &lt;rafsi&gt;cpi&lt;/rafsi&gt;
  7.             &lt;definition&gt;x1 is a bird of species x2&lt;/definition&gt;
  8.             &lt;notes&gt;&lt;/notes&gt;
  9.         &lt;/valsi&gt;
  10.         ...
  11.     &lt;/direction&gt;
  13.     &lt;direction from=&quot;English&quot; to=&quot;lojban&quot;&gt;
  14.         &lt;nlword word=&quot;eagle&quot; valsi=&quot;atkuila&quot; /&gt;
  15.         &lt;nlword word=&quot;hawk&quot; sense=&quot;bird&quot; valsi=&quot;aksiptrina&quot; /&gt;
  16.         ...
  17.     &lt;/direction&gt;
  18.     
  19. &lt;/dictionary&gt;

My issue is I can either read in <valsi> nodes or <nlword> because they both contain the attribute "word":

  1. main.NLWord field &quot;Word&quot; with tag &quot;word,attr&quot; conflicts with field &quot;Valsi&quot; with tag &quot;word,attr&quot;

I'm starting to think unmarshalling may be the wrong approach as I'd ideally structure the data differently. Should I read the XML in using some other method and build up data structures manually?

  1. type Valsi struct {
  2. 	Word  string   `xml:&quot;word,attr&quot;`
  3. 	Type  string   `xml:&quot;type,attr&quot;`
  4. 	Def   string   `xml:&quot;definition&quot;`
  5. 	Notes string   `xml:&quot;notes&quot;`
  6. 	Class string   `xml:&quot;selmaho&quot;`
  7. 	Rafsi []string `xml:&quot;rafsi&quot;`
  8. }
  10. //Whoever made this XML structure needs to be painfully taught a lesson...
  11. type Collection struct {
  12. 	From  string  `xml:&quot;from&quot;`
  13. 	To    string  `xml:&quot;to&quot;`
  14. 	Valsi []Valsi `xml:&quot;valsi&quot;`
  15. }
  17. type Vlaste struct {
  18. 	Direction []Collection `xml:&quot;direction&quot;`
  19. }
  21. var httpc = &amp;http.Client{}
  23. func parseXML(data []byte) Vlaste {
  24. 	vlaste := Vlaste{}
  25. 	err := xml.Unmarshal(data, &amp;vlaste)
  26. 	if err != nil {
  27. 		fmt.Println(&quot;Problem Decoding!&quot;)
  28. 		log.Fatal(err)
  29. 	}
  30. 	return vlaste
  31. }

答案1

得分: 2

我可能没有完全理解你的问题，但是对于我来说，以下结构在我这里运行良好（根据你修改的示例）：

  1. type Valsi struct {
  2.     Word  string   `xml:"word,attr"`
  3.     Type  string   `xml:"type,attr"`
  4.     Def   string   `xml:"definition"`
  5.     Notes string   `xml:"notes"`
  6.     Class string   `xml:"selmaho"`
  7.     Rafsi []string `xml:"rafsi"`
  8. }
  10. type NLWord struct {
  11.     Word  string   `xml:"word,attr"`
  12.     Sense string   `xml:"sense,attr"`
  13.     Valsi string   `xml:"valsi,attr"`
  14. }
  16. type Collection struct {
  17.     From    string    `xml:"from,attr"`
  18.     To      string    `xml:"to,attr"`
  19.     Valsi   []Valsi   `xml:"valsi"`
  20.     NLWord  []NLWord  `xml:"nlword"`
  21. }
  23. type Vlaste struct {
  24.     Direction []Collection `xml:"direction"`
  25. }

在这个结构中，Collection 可以有 Valsi 值和 NLWord 值。
然后，你可以根据 From/To 或 Valsi 或 NLWord 的长度来决定如何处理数据。

英文:

I may not have grasped what your problem is but the following structure works fine for me
(your modified example on play):

  1. type Valsi struct {
  2.     Word  string   `xml:&quot;word,attr&quot;`
  3.     Type  string   `xml:&quot;type,attr&quot;`
  4.     Def   string   `xml:&quot;definition&quot;`
  5.     Notes string   `xml:&quot;notes&quot;`
  6.     Class string   `xml:&quot;selmaho&quot;`
  7.     Rafsi []string `xml:&quot;rafsi&quot;`
  8. }
  10. type NLWord struct {
  11.     Word  string   `xml:&quot;word,attr&quot;`
  12.     Sense string   `xml:&quot;sense,attr&quot;`
  13.     Valsi string   `xml:&quot;valsi,attr&quot;`
  14. }
  16. type Collection struct {
  17.     From  string    `xml:&quot;from,attr&quot;`
  18.     To    string    `xml:&quot;to,attr&quot;`
  19.     Valsi []Valsi   `xml:&quot;valsi&quot;`
  20.     NLWord []NLWord `xml:&quot;nlword&quot;`
  21. }
  23. type Vlaste struct {
  24.     Direction []Collection `xml:&quot;direction&quot;`
  25. }

In this structure, Collection can have Valsi values as well as NLWord values.
You can then decide, depending on From/To or the length of either Valsi or NLWord how to handle the data.

huangapple
  • 本文由 发表于 2013年10月18日 06:36:09
  • 转载请务必保留本文链接：https://go.coder-hub.com/19438495.html
  • go
  • unmarshalling
  • xml
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定