Recommended Property Tree Enhancements: Difference between revisions

m
Line 55: Line 55:


== Recommended new 'types'  for nodes ==
== Recommended new 'types'  for nodes ==
Currently, there is no clear distinction taking place between arbitrary strings, filenames, paths, property paths or property nodes - this makes it increasingly complicated to keep track of what sort of data is represented by a particular node/string in the tree and makes it basically impossible to provide validation routines, or even come up with XML schemas that might help validating PropertyList-encoded XML files.
Currently, there is no clear distinction taking place between arbitrary strings, filenames, paths, property paths or property nodes - this makes it increasingly complicated to keep track of what sort of data is represented by a particular node/string in the tree and makes it basically impossible to provide validation routines, or even come up with XML schemas [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21404.html] that might help validating PropertyList-encoded XML files.


Thus, it is suggested to start differentiating clearly between these different types of strings:
Thus, it is suggested to start differentiating clearly between these different types of strings:
2,561

edits