• From: "Simon St.Laurent" <simonstl@s...>
• To: "'xml-dev@l...'" <xml-dev@l...>
• Date: Sat, 17 Jan 2009 11:36:44 -0500

Robert Koberg wrote:
> 
> On Jan 17, 2009, at 10:45 AM, Simon St.Laurent wrote:
> 
>> I worry that the example is way too simple, which makes the 
>> consequences seem less consequential.
>>
>> However, as a way of introducing the concept to people who can't 
>> imagine it, it's definitely a good thing.
> 
> In addition, I think authentication and authorization would come into 
> play...

For some applications, yes.  For a lot of others, no.

(And even with authentication and authorization, there's still plenty of 
room for people to do unexpected things with your data.)

Thanks,
Simon St.Laurent

• Follow-Ups:
  • Re: Meaning of "Design for the unanticipated user"
    • From: Robert Koberg <rob@k...>

• References:
  • Meaning of "Design for the unanticipated user"
    • From: "Costello, Roger L." <costello@m...>
  • Re: Meaning of "Design for the unanticipated user"
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: Meaning of "Design for the unanticipated user"
    • From: Robert Koberg <rob@k...>