>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: Robert Koberg <rob@------.--->
Date: 1/17/2009 10:08:00 PM

Robert Koberg wrote:
> 
> On Jan 17, 2009, at 11:36 AM, Simon St.Laurent wrote:
> 
>> 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.
> 
> Either way, it is a level of authentication/authorization

Maybe - but I think of people like me who do unusual things with the 
data they get once authenticated.  I'm not always beloved for it, really.

Thanks,
Simon

>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"