Keith,
I thought about that, but the problem is that we might, potentially,
want to insert xincluded sub-documents at any point in the XML tree, ie
each of these are potentially legal (I'm simplifying the XML a little):
<dc>
<include href="inc_target.xml">
</dc>
or
<dc>
<target>
<include href="inc_target_device.xml">
</target>
</dc>
or
<dc>
<target>
<target_device>
<include href="inc_disk.xml">
</target_device>
</target>
</dc>
And the new "base" attribute will get added at the point where
the xincluded sub-doc is inserted. Therefore, we'd have to change the
schema to add an optional "base" attribute to almost every element?
Or perhaps I'm misunderstanding how the whole XInclude mechanism
is meant to work? I'm certainly open to correction on this.
- Dermot
On 11/05/10 17:21, Keith Mitchell wrote:
Hi Dermot,
On a higher level, would it perhaps be better to allow this attribute
to pass validation? This would provide an audit trail of sorts for
xincluded elements, which could be valuable.
- Keith
On 11/ 5/10 04:42 AM, Dermot McCluskey wrote:
Hi,
Can I get a review for this fairly simple fix for ManifestParser bug:
http://monaco.sfbay/detail.jsf?cr=6997263
Webrev is at: http://cr.opensolaris.org/~dermot/webrev-6997263/
Thanks,
- Dermot
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
