It is a XML issue with the XSD.
I think keeping the links simpler and wrapping dsig is probably going
to be easier for most people.
I think a lot of protocols using XRD are going to define extensions in
Link
Though I do sort of like calling out the extensions like that.
John B.
On 2009-09-04, at 3:05 PM, Dirk Balfanz wrote:
> On Friday, September 4, 2009, Scott Cantor <> wrote:
>> Will Norris wrote on 2009-09-04:
>>> (this new Extensions wrapper element is necessary to ensure that the
>>> XRD schema's data model is unambiguous. You can find the
>>> conversation
>>> thread on the list)
>>
>> Keep in mind that we should optimize for the common case. If it's
>> going to
>> be common to put extensions inside Link, it may be simpler to just
>> wrap
>> KeyInfo in something and solve the ambiguity that way.
>>
>
>
> This does seem weird. Shouldn't the fact that we're using a different
> name space be enough of a hint that this is an extension?
>
> Dirk.
>
>> -- Scott
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
