[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dss] Action 05-04-18-05: use of xs:any
Juan Carlos, I vaguely recall that at the last call there was preference for option 1 as this was what is currently used in XML Signature. Am I correct? Nick > -----Original Message----- > From: Juan Carlos Cruellas [mailto:cruellas@ac.upc.edu] > Sent: 29 April 2005 13:07 > To: DSS TC List > Subject: [dss] Action 05-04-18-05: use of xs:any > > > Dear all, > > In the last conf call we were talking about the usage of > <xs:any> within a <xs:choice>... > Currently there are two potential solutions to the Unique > Particle Attribution problem that our current schema does have: > > 1. The approach suggested by Konrad: use > <xs:any namespace="#other" processContents="lax"/> > > This particle stands for any element DEFINED OUTSIDE the > namespace defined for the core. In case that in the future > some of the choices could be another element of the core not > present in the list of choices at that moment, it would be > necessary to change the xml schema and add an explicit > mention to that element. We should also make sure that any > profile profiling the contents of one of this choices by > adding new elements, should have its own namespace. > > 2. To use the <dss:AnyType> already defined in the core. > This avoids any consideration about the namespace of its > contents, but introduces a new level in the xml tree.... > > Does anybody have a special preference for one of them? > > Regards > > Juan Carlos. > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your > TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]