Re: [higgins-dev] Reorganizing Higgins site/content (another tweak)

[Anthony Nadalin <drsecure@xxxxxxxxxx>]

Not sure they can be branded Higgins since there is no Higgins brand, but they should be labeled as part of the Eclipse Higgins Project

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122

Paul Trevithick ---03/18/2009 08:29:12 AM---All Higgins solutions including the various flavors of the Higgins Selector are (or are supposed to be):

From:	Paul Trevithick <ptrevithick@xxxxxxxxx>
To:	higgins-dev <higgins-dev@xxxxxxxxxxx>
Date:	03/18/2009 08:29 AM
Subject:	Re: [higgins-dev] Reorganizing Higgins site/content (another tweak)

---

All Higgins solutions including the various flavors of the Higgins Selector are (or are supposed to be):

• branded Higgins
• downloadable as a set of components and deployable

In addition for some of these there may be packaged/rebranded versions available (e.g. From Novell as “DigitalMe”). These versions are often better packaged and easier to install than the equivalent Higgins versions.

But you’re right we need to lay this out more clearly. 

--Paul

On 3/18/09 1:29 AM, "Drummond Reed" <drummond.reed@xxxxxxxxxxxx> wrote:

One point: If it stays singular (“Higgins Selector”), the reader is going to expect to be able to download and install and use something branded as the “Higgins Selector”. However if the Higgins Selector is only available as a set of components that are packaged and rebranded for distribution by others (e.g., Azigo, DigitalMe), then the underlying pages should explain that clearly, and provide links to where the branded packages can be downloaded.

=Drummond




---


From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Trevithick
Sent: Tuesday, March 17, 2009 12:13 PM
To: higgins-dev
Subject: Re: [higgins-dev] Reorganizing Higgins site/content (another tweak)

It was a conscious choice in the interest of simplicity. All of the separate selectors we have could be thought of as just different flavors for different platforms. But there’s really only one thing, the Higgins Selector. By contrast, behind the other 2 doors are mixtures of different kinds of things.

Could be wrong. What do others think?

--Paul

On 3/17/09 2:19 PM, "Mary Ruddy" <mary@xxxxxxxxxxxxxxxxx> wrote:
Should door number 1 be called Higgins Selectors (plural) since all three doors point to multiple things?



---



From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Trevithick
Sent: Monday, March 16, 2009 11:58 PM
To: higgins-dev
Subject: Re: [higgins-dev] Reorganizing Higgins site/content (another tweak)

Oops. That was a typo. IDS was supposed to be “Identity Data Service” (see red correction below).

BTW, I’ve implemented tonight these changes in the home page and the top three “overview”/door pages (now as wiki pages) in the staging area here: http://www.eclipse.org/higgins/ver2/index.php

--Paul


On 3/16/09 10:39 PM, "Mary Ruddy" <mary@xxxxxxxxxxxxxxxxx> wrote:
Cleaning this up will be great. It would be nice if we could get even more
differentiation between IDS and IdAS. Both have long names of Identity
Attribute Service. What about IDWS (Identity Attribute Web Service)?

-----Original Message-----
From: higgins-dev-bounces@xxxxxxxxxxx
[mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Trevithick
Sent: Monday, March 16, 2009 6:23 PM
To: higgins-dev
Subject: [higgins-dev] Reorganizing Higgins site/content (another tweak)

Folks,

I’m just back from three days of Higgins meetings in France with the FC2
consortium. The experience prompt the following proposed changes to the
site/wiki content:

TODAY --> PROPOSED
===== ========

Clients Selectors
------- ---------
AIR Client & Server AIR Selector (including ICS)
Web Selector (including ICS)
ICM[missing!] merged into the above
RCP no change
GTK/Cocoa no change
FF-embedded no change

Identity Services Identity Services
----------------- -----------------
WS-Trust IdP no change
SAML IdP no change
RP no change
Web Selector moved up above
XDI4J moved down below

Identity Att. Svcs Attribute Services
------------------ ------------------
IDS - multiprotocol web service
XDI4J - now moved here
IdAS - today's Java framework

Where IDS is short for "Identity Data Service," a multiprotocol
attribute data service (web service) based on IdAS framework.

Advantages/Disadvantages
------------------------
+ All three "doors" are now doors to multiple things (consistency)
+ We differentiate between the IdAS Java interfaces and the IDS
+ We use "selector" instead of "client"
+ so we can include the "web selector" under "selectors"
+ now all selectors are grouped together under "Selectors"
+ XDI4J has a better home
+ The missing WEB (GWT) I-Card Manager now has a home
+ Now IDS can support Plaxo Portable Contacts, XDI, etc. without
being confused with the name of the underlying framework (IdAS)
- The client word was a less bias-proclaiming word than selector.
We switched to client when we thought contributions from
IDIB and/or Liberty (ECP, etc.) folks might be forthcoming.
Now we should just go back to making a "multi-protocol" selector
and be welcoming by our actions (true multi-protocol-ness).

--Paul


_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev



_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev

_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev