[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Improving 7.1
> Then 7.1 implies the following excluded paths: > > attribute//element > attribute//attribute > list//list > list//element > list//attribute > list//text > key//key > key//keyRef > key//list > key//element > key//attribute > key//group > key//interleave > key//oneOrMore > key//text > anyName/except//anyName > nsName/except//nsName > nsName/except//anyName > oneOrMore//group//attribute > oneOrMore//interleave//attribute > > (Have I missed any?) I missed the cases relating to data/except: data/except//group data/except//interleave data/except//oneOrMore data/except//key data/except//keyRef data/except//list data/except//attribute data/except//element data/except//text If we adopt this approach to explaining the restrictions, then we can simplify the spec and improve expressivity by removing the data/except//list restriction. James
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC