Re: [vwrap] Parsing of invalid LLSD elements in XML

[Mark Lentczner <[e-mail]>]

On Apr 1, 2010, at 9:26 AM, David W Levine wrote:
> I *think* we are talking about a very special case here.

This seems at the core to me. We are asking about cases where the serialization rules have been violated. If, for example, the uuid value was correct but the closing uuid tag misspelled "</wwid>", then XML processing would have required that the whole XML document to be rejected. Seems to me that the case of the text inside the uuid element not conforming to the UUID syntax is the same: The entire LLSD value should be rejected. 

As for error reporting, I note that even though XML processing demands that the whole document be rejected, parsers are still able to report specific and helpful error messages at the receiving side. The same should be true of LLSD processors.

	- Mark

P.S.: Small bit of XML pedantry:

On Mar 31, 2010, at 2:53 PM, Joshua Bell wrote:
> ... this LLSD XML fragment (pretend it has the right prologue and hence is well-formed XML):
> 
> <llsd>
>     <map>
>         <key>test</key>
>         <uuid>this is not a uuid</uuid>
>     </map>
> </llsd>

Actually, that is well-formed XML just as it sits. There is no requirement for an XML prolog where XML doesn't mandate one.



Mark Lentczner
Sr. Systems Architect
Technology Integration
Linden Lab

[e-mail]

Zero Linden
[e-mail]