> 7) I saw clear dislike for including more detailed semantics of > matching LLSD payloads against LLIDL descriptions. The combination of > LLIDL's shape semantics, and LLSD's defaulting and conversions was felt > to be the right level of specification. Nonetheless, if anyone would > like a more detailed description of how our open source LLIDL system > performs matching and validation, I can give pointers to the code, or > provide a write-up to the mailing list if people want. Just ask. > Mark, can you point me at the LLIDL handling code? I'm interested in LLIDL's application to unit testing. John
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.