We could do that in the schema. That won't stop people from doing it
though.
There may be a case in XRI resolution that you end up with a single
XRD if you were to resolve a one subsegment XRI.
For XRI applications it may still make sense to use XRDS at the
wrapper if the XRD are 1 or more for consistency.
I would prefer not to enforce it in the schema at this point.
I think what we are after is discouraging people from creating XRD
with XRDS wrappers for no reason.
Not to preclude things like resolvers from using XRDS if it makes sense.
John B.
On 2009-09-01, at 1:42 PM, Will Norris wrote:
>
> On Aug 31, 2009, at 9:54 PM, Drummond Reed wrote:
>
>> IMPORTANT: In past practice, XRDS was often used as the root
>> element even if contained only a single XRD. That practice is now
>> deprecated. The XRDS element SHOULD NOT be used unless it contains
>> a sequence of two or more XRDs.
>
> couldn't we actually enforce this at the schema level with a
> minOccurs="2"? Is there a time when you might actually want to have
> an XRDS with a single XRD? thoughts?
>
> -will
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
