Page Tree:

Child pages
  • Person Extant Models - Candidates for Adoption - Delegation to Infrastructure

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


This page documents candidate software related to this service:

  1. as a model of function or interface that might influence or guide design of this service;
  2. candidate software that this service might adopt to deliver service functionality, with or without refactoring, service-wrapping, or other adaptation; and/or
  3. candidate or selected infrastructure that might serve as a delegate that delivers service functionality (e.g., via call to the infrastructure from a wrapper service) if the candidate is integrated into the Bamboo Services Platform

Because overlap between these categories is possible, please indicate in the rightmost column an assessment of which (one or more) categories any given reference fits: model, adopt, and/or delegate.

Models - Adoptions Candidates - Delegated Function:

Unknown macro: {multi-excerpt} Person



Description / Notes

Model - Adopt - Delegate

Keith Hazelton
11 May 2011

Person services base url: http(s)://

Specific person service uris: (with base url prepended)

Url Template



http(s):// (Base url by itself)

List all people (paged)

List GET


Registers new person, returns full person record from bamboo person registry)

Create POST



Read GET




Consolidate two person records under a single BPI

Update PUT



Update PUT


returns BPI or null

Read GET


Keith Hazelton
12 May 2011

Blah blah blah. Worth review for service modeling; if stuff is incorporated into infrastructure and this service delegates to it, functionality to do blah blah blah will need to be added.

Model, Delegate


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