Params cannot carry descriptions in VOEvent 1.1

[Matthew Graham]

Hi,

On Mar 26, 2010, at 4:30 PM, Rob Seaman wrote:

>> "A <Description> may be included within any element or sub-element of a VOEvent to add human readable content."
>> 
>> and
>> 
>> "A <Reference> may be included in any element or sub-element of a VOEvent packet to describe an association with external content via a Uniform Resource Identifier [16]."
>> 
>> So which part of the "normative" spec is not?
> 
> As in all prose, specific statements overrule the general.  It would not make it more clear to add "except for cases in which this is specifically excluded" to every sentence.

That's not a normative rule. I think that specific exclusions should be explicitly stated.

> 
>>       <xs:element name="Reference"   type="Reference" *** THIS BIT IS MISSING IN THE SCHEMA *** />
> 
> Ok.  Bob, is this correct in your schema?  Is anybody creating typed references in any event?

Well, it should mean that any Reference should not validate at all since no type is specified but it shows how forgiving most validators are!

	Cheers,

	Matthew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20100326/afa78b03/attachment-0001.html>