[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Auth]A comment on terminology
From: |
Norbert Bollow |
Subject: |
Re: [Auth]A comment on terminology |
Date: |
Tue, 8 Jan 2002 16:51:20 +0100 |
Hans Zandbelt <address@hidden> wrote:
> At 10:10 1/8/2002 -0500, you wrote:
> >The term 'Profile Provider' is misleading. I recommend
> >'Profile Host' as a replacement. 'Profile Provider' implies
> >that it is the source of the profile data. But, of course, a
> >Profile Host only hosts the profile, the owner of the data
> >'Provides' the data.
>
> I agree, but I used the "Provider" part to indicate that
> the "Profile ..." is (in my opinion) a slightly more active role
> than the traditional web-hosting; is that true?
> Profile ... needs to offer services to a user to manage his profile
> and access policies remotely. Potentially a Profile ... is able
> to put constraints on the profile information.
> Plus he needs to enforce the user defined access policies on
> profile requesters; especially this is what I wanted to stress.
>
> If you (and others) think that the last aspect is also covered
> by the term "Host", I will conform.
If I'm the host of a meeting of real people in real life, then
it'll also have a role in making sure that unwelcome uninvited
guests won't spoil the party. In doing this, I will pay attention
to the wishes and sensibilities of my guests. So I think,
the scope pe the word "host" is big enough to cover also this
aspect.
> >Profile Host: Hosts profiles to facilitate remote
> >access.
> >Profile Owner: Owns profile data and controls access to
> >it.
> >Service Provider: Creates and delivers Web Services that
> >request profile data.
> >
> >This is the terminology that I intend to use.
>
> I will do so as well from now on.
It's always good when multiple people speak the same
language... :-)
I'll put this as "suggested terminology" on the website.
Greetings, Norbert.
--
A member of FreeDevelopers and the DotGNU Steering Committee: dotgnu.org
Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland)
Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://thinkcoach.com
Your own domain with all your Mailman lists: $15/month http://cisto.com
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), (continued)
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Mike Warren, 2002/01/09
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Rhys Weatherley, 2002/01/09
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Hans Zandbelt, 2002/01/10
- [Auth]A real life case in Identity, Albert Scherbinsky, 2002/01/10
- Re: [Auth]A real life case in Identity, Albert Scherbinsky, 2002/01/11
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Mike Warren, 2002/01/11
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), David Sugar, 2002/01/06
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Hans Zandbelt, 2002/01/07
- [Auth]A comment on terminology, Albert Scherbinsky, 2002/01/08
- Re: [Auth]A comment on terminology, Hans Zandbelt, 2002/01/08
- Re: [Auth]A comment on terminology,
Norbert Bollow <=
- Re: [Auth]A comment on terminology, Albert Scherbinsky, 2002/01/08
- Re: [Auth]A comment on terminology, Hans Zandbelt, 2002/01/08
- Re: [Auth]A comment on terminology, David Sugar, 2002/01/08
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Hans Zandbelt, 2002/01/07
- Re: [Auth]Re: What I percieve is wrong with IDsec (was IDsec specification draft), Hans Zandbelt, 2002/01/07