RE: [xri] <Type>

[Eran Hammer-Lahav <eran@hueniverse.com>]

I will defer to you on the correct XML syntax. I agree there is a difference between 'no value' and 'empty value'. However, that's up to the protocol defining the property to deal with. We should provide two examples like:

<Property type="http://example.com/some/api"; />
<Property type="http://example.com/protocol/ext";>language</Property>

To inspire protocol authors on how they may use this element. But if they really want empty values as a valid property value, well, who am I to tell them no.

EHL

> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu]
> Sent: Saturday, November 07, 2009 2:13 PM
> To: Eran Hammer-Lahav; 'Drummond Reed'
> Cc: xri@lists.oasis-open.org
> Subject: RE: [xri] <Type>
> 
> Eran Hammer-Lahav wrote on 2009-11-07:
> > I don't think we need to say anything other than explicitly allow
> empty
> > values. A protocol can use a property with empty value to indicate
> type.
> 
> If you mean "no value", that's <Element xsi:nil="true"/>
> 
> I do agree that this is not likely to be common, but it is a mistake to
> use
> empty elements alone because of both correctness, and the ambiguities
> introduced by whitespace.
> 
> -- Scott
>