Win a copy of Succeeding with AI this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Junilu Lacar
Sheriffs:
  • Tim Cooke
  • Jeanne Boyarsky
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • fred rosenberger
  • Frits Walraven

PROCESSING ATTRIBUTES

 
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Arguments over whether it is best to use elements or attributes to store values are common in XML applications. Which questions should an XML developer ask to determine whether it is best to use elements or attributes to store values for a particular situation?
a)Is the data flat or hierarchical?
b)Do multiple values need to be offered?
c)Do child information items need to be ordered? d)Does information need to be distributed over multiple devices?
e)Does information need to be queried?
f)Does the value have one of an enumeration of values?
Given answer is a, b, c, f
I think e should also be in the list, my reason being, that I read somewhere, that processing attributes is faster than elements. Am I right in my assumption?
 
If you were a tree, what sort of tree would you be? This tiny ad is a poop beast.
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic