Page Tree:

Child pages
  • Person Service Questions

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

Person pages: Home | Description | Use Cases | Questions | Models/Adoption/Delegation | Entity Diagrams | Contract


Unknown macro: {multi-excerpt} Person


Should this service be named differently?

Does this service more properly support a USER rather than a PERSON? Specifically, might Bamboo services model PERSONs who are authors or artists (Shakespeare, Rembrandt); subjects in paintings or written texts (Rembrandt, Hamlet); scholars of interest who may not utilize Bamboo services or environments (Harold Bloom, M. H. Abrams, Stephen Greenblatt); or mythological or historical figures (Odin, King Arthur, Anne Boleyn) – and create identifiers for them too – and model users with Bamboo Identifiers (modeled by this service) as a "subclass" of Person? (contributed by Patrick Schmitz, UC Berkeley, 4 Jan 2011)

What processes and technologies should be used to verify assertions of identity made by multiple identity providers, such as Shibboleth/InCommon and OpenID?

Cf. ongoing discussion in the Internet2 OpenID wiki space; and on this wiki's Platform Person-Profile-AuthN-AuthZ Requirements family of pages.

What about search for Bamboo Persons using search terms maintained in a person's Profile?

As initially conceived, the Person service (this service) will offer thin functionality. What are the downsides or risks of exposing only thin functionality – query and return using identifiers that will, in some or many cases, be opaque to humans – from this service, and offering richer search functionality is a service other than "Person," i.e., in Person Profile?

Person pages: Home | Description | Use Cases | Questions | Models/Adoption/Delegation | Entity Diagrams | Contract