• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

PROCESSING ATTRIBUTES

 
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic