XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Meaning of "Design for the unanticipated user"


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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS