>Archive Index
>xml-dev Archive Home
>Recent entries

>Thread Prev - Meaning of "Design for the unanticipated user"
[Thread Next]

Re: [xml-dev] Meaning of "Design for the unanticipated user"

From: "Simon St.Laurent" <simonstl@--------.--->
To: "'xml-dev@-----.---.---'" <-------@-----.---.--->
Date: 1/17/2009 4:37:00 PM

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

>Thread Prev - Meaning of "Design for the unanticipated user"
[Thread Next]

>Archive Index
>xml-dev Archive Home
>Recent entries

Altova Mailing List Archives

Re: [xml-dev] Meaning of "Design for the unanticipated user"