Subject: Re: Dependency Sorting, first of kind From: Paul Prescod <paul@xxxxxxxxxxx> Date: Wed, 03 Nov 1999 09:03:15 -0600 |
Francis Norton wrote: > > Hi, > > This might be a first cut - it feels like the right approach but has two > problems: > > First, I've taken the liberty of simplifying the multiple dependencies > to single dependencies. I think multiple dependencies should be possible > (I assume from the class analogy that they are "and" related) but I > would like to normalise them into a "<depends-on dependee='foo' > dependent='bar'>" element - would that be acceptable, Paul? Okay, but if you normalize them, the input would need to look like this: <a name="foo"/> <a name="bar" depends-on="foo"/> <a name="baz" depends-on="foo"/> <a name="jaz" depends-on="foo"/> <a name="jaz" depends-on="bar"/> <a name="spaz"/> <a name="maz" depends-on="spaz"/> <a name="maz" depends-on="bar"/> I don't think your code would work for this form. This is where I ran into the roadblock. How do you print out jaz only once even though it occurs as a dependent of both "foo" and "bar"? Maybe I can do something with preceding::. I'll pursue that route. Paul Prescod XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Dependency Sorting, first of ki, James Clark | Thread | Re: Dependency Sorting, first of ki, Francis Norton |
Schematron validation based on the , Miloslav Nic | Date | Variable Scoping, Clark C. Evans |
Month |