Altova Mailing List Archives>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"To: "Simon St.Laurent" <simonstl@--------.---> Date: 1/17/2009 5:14:00 PM 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 best, -Rob | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
