[
Lists Home |
Date Index |
Thread Index
]
- From: roddey@us.ibm.com
- To: xml-dev@ic.ac.uk
- Date: Tue, 1 Dec 1998 15:07:26 -0700
"IMHO the purpose of ID/IDREF is to express non-hierarchical data using
hierarchical notation. Appropriate use of ID and IDREF attributes
allows the representation of any directed graph, whether acyclic or
cyclic."
How can you represent a strictly acyclic graph using ID/IDREF? For
instance, if you have an employee list, and every employee has an ID
attribute which is his/her employee number and an IDREF attribute which
refers to his/her manager, what do you do when you reach Le Gran Fromage
(sp?)? This person has no manager, but the parser will consider it an error
if his/her manager field does not refer to someone else's employee id. Does
not that not imply the insertion of at least a single bogus cycle in the
data just to make the parser happy? Would an application processing this
file otherwise have to try to gleen that the error occured because of this
known problem and not because of some other, real, problem?
Not trying to be accusatory or anything. I just wonder how that is supposed
to work.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|