Project Bamboo

Navigation:
Documentation
Archive


Page Tree:

Child pages
  • Person Profile Service Contract Description - v0.9-alpha

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

Skip to end of metadata
Go to start of metadata

Brief description

Version

This page describes the Person Profile service API, v0.9

To discover the version and other metadata about deployed service code that fulfills this API, please utilize the Service Catalog Service.

Overview and Definitions

The Person Profile service manages descriptive information about a Bamboo Person. The descriptive information is largely self-asserted. The entity diagram associated with the Bamboo Person service may be of interest vis-a-vis the information managed by this service; the versioned Bamboo Person schema is authoritative.

A Bamboo Person Profile is sufficiently rich to support search and discovery for users interested in building communities of practice and scholarship. It is not an authoritative, verified, or complete profile of a person. A Bamboo Person Profile may include self-asserted URIs or URLs that identify independently maintained stores of information about the profile's subject (e.g., a VIVO, Zotero, OpenScholar, or Academia.edu profile; or an institutionally-maintained repository of user profile information, such as a web page, an LDAP directory listing, a curriculum vitae (CV), etc.; inclusion of these links permits services that support search and discovery of Bamboo Persons of interest to follow, index, and/or mine the linked data.

The following table (tentatively and approximately) maps elements of a Bamboo Person Profile to some common representations of profile information used in academic contexts.

Bamboo Profile Element

LDAP 

eduPerson

VIVO

Academia.edu 

Interests

(question)

(question)

SubjectArea

Research Interests 

Expertise

(question)

(question)

(question)

(question)

External Affilliations

(question)

eduPersonAffiliation,eduPersonPrimaryAffiliation, etc.

Organization (subclasses of)

(question)

Other Profiles

LDAP search string, e.g., Steve Masover's LDAP URL at UC Berkeley (ldap://ldap.berkeley.edu/uid=18223,ou=people,dc=berkeley,dc=edu)

(question)

URL (e.g., Rakesh Nagarajan at Washington University School of Medicine)

URL (e.g. Paul Krugman at Princeton University) 

Contact Info

postalAddress, telephoneNumber, mail, etc.

postalAddress, mail,telephoneNumber, etc.

Address (subclasses of)

(question)

Assumptions

  • Group memberships are managed via a Groups service.
  • Contact information is be managed by a Contact Service.

References

${REPOSITORY_ROOT} is http://svn.code.sf.net/p/projectbamboo/code/

Known Issues

n/a

ROA Layer API

RESTful service methods performing Create, Read, Update, Delete, and List functions over a Bamboo Person's Profile keyed on a Bamboo Person identity (BPId). For more on the BPId, see Person Service Contract Description.

Base URLs

It is assumed in this documentation that no centrally-run instances of the Bamboo Services Platform will be running after the project ends on 31 March 2013. Therefore, base URLs are assumed to be on a developer's machine, localhost. The base URL with a port number assumes that the BSP is running unsecured; the URL without a port number assumes that security is enforced and Apache Web Server is intercepting and redirecting service calls. Please see the page Identity and Access Management - Authentication and Authorization for context, as well as links to installation and configuration instructions for secured instances of BSP.

Note that ONLY services at v0.9 or greater will run properly in a secured instance of the BSP.

Currently available base URLs:

 

 

Client Responsibilities in Requests to Secured BSP Web Services

This section of the Service API documentation describes a client application's responsibilities when making requests to secured Web Services hosted on the Bamboo Services Platform (including this service).

A secured instance of the Bamboo Services Platform (BSP) implies a significant set of installation and configuration tasks for which the operator of the BSP is responsible. These are described in overview on the wiki page Identity and Access Management - Authentication and Authorization, and in detail on pages linked from that one.

(1) A client must be configured as a Trusted Application if requests are to be treated other than as Anonymous

A client application – whether a web app or a simple testing client such as Firefox Poster or curl – may make requests anonymously or as a "Trusted Application." Only a Trusted Application may assert the identity of a user on behalf of whom the request is made, and scoped roles to be assigned to that user; Bamboo Services trust such clients to assert the identity and assigned-roles only of users who have authenticated in the current session of application activity. (A special-case type of client application, termed Innovation Licensed applications, are trusted to assert the identity of and roles assigned to a fixed set of special-case users without those users having to authenticate in the current session.)

Configuration of client applications are described in detail in this wiki page: Configure Apache Web Server for Client Auth. It is assumed in #2, below, that this configuration has been performed.

(2) A Trusted client is expected to pass HTTP Request Headers to identify itself and an authenticated user

A client application that is Trusted in the security context of the Bamboo Trust Federation (cf. Identity and Access Management - Authentication and Authorization) must augment each request to a service hosted by a secured instance of the Bamboo Services Platform (BSP) with a set of HTTP headers, as follows:

  • X-Bamboo-AppID: A UUID that identifies the client research environment, application, tool, or service; this UUID is issued as part of the process of registering a trusted client in the Bamboo Trust Federation as described in overview on the page Identity and Access Management - Authentication and Authorization; and in detail with respect to physical establishment of trust on the page Configure Apache Web Server for Client Auth. The value of this header is linked to the X.509 certificate by which the application establishes an SSL connection to the BSP host in the registration process, and a match between this Application ID and the linked X.509 certificate is checked by the BSP on receipt of every request.

  • X-Bamboo-BPID: A UUID that identifies the logged-in user on whose behalf the request is being sent; this value, a Bamboo Person Identifier, or BPId, is obtained via a call to the Person Service that occurs in time between user login and any other service request. See the Read a BambooPersonId method of the Person Service API for details. [†]
  • X-Bamboo-Roles: A pipe-delimited (|) set of scoped roles asserted by the trusted client to belong to the logged-in user, of the form role@domain, which are to be evaluated as factors in the determination of whether the request satisfies policies (access restrictions) that apply to the requested resource. If a user is authenticated, the client is expected to include the role undefined@domain where domain identifies the organization that authenticated the user (example: undefined@google.com is a client app's assertion that the user authenticated to Google). This header is otherwise optional (depending on policies governing the requested resource that may require one or more scoped roles for access to be permitted). Example of multiple roles asserted in this header: roleA@domainOne.xxx|roleB@domainTwo [‡]

[†] The value of X-Bamboo-BPID is set to the identifier for the application itself (X-Bamboo-AppID) when a client application calls the Person Service to create a new Bamboo Person Identifier; or to retrieve the BPId for a user based on the identifier of the IdP with which she has logged in and an SHA-256 hash of that IdP's user identifier for the logged-in person.

[‡] Policies and policy evaluation are described on the page Authorization and Policy. Also see Conventions for representing Identity Providers in the Bamboo Trust Federation.

Schema

${REPOSITORY_ROOT} is http://svn.code.sf.net/p/projectbamboo/code/

  • ${REPOSITORY_ROOT}/platform-services/bsp/trunk/bsp/core-services/person-service/person-service-domain/src/main/resources/BambooPerson.xsd

Person Profile

A Person Profile service is descriptive information about a Bamboo Person.

Create a Person Profile

A client creates a Bamboo Person Profile by supplying a minimum of personal information relating to a specific person as identified by their unique identifier (i.e. bambooPersonId).

Preconditions:

  1. Existing Bamboo Person
  2. Existing Bamboo Contact

Calling Method and Arguments

Invoked as an HTTP POST method with a BambooPerson XML document in the body of the HTTP request. Send an HTTP request of the form:

POST <url root>/bsp/persons/{bambooPersonId}/profiles HTTP/1.1

Parameter

Meaning

bambooPersonId

The unique identifier for a Bamboo Person

HTTP Body

An instance of a bambooPerson XML document containing the profile to be added

Example:

POST <url root>/bsp/persons/urn:uuid:570a60f3-1ac7-48c3-8984-0d48bdb38923/profiles

Example BambooPerson XML document:

<?xml version="1.0" encoding="UTF-8"?>
<person:bambooPerson xmlns:person="http://projectbamboo.org/bsp/BambooPerson" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <person:bambooProfile person:confidential="false" person:primary="true" 
    xmlns:contacts="http://projectbamboo.org/bsp/services/core/contact" 
    xmlns:person="http://projectbamboo.org/bsp/BambooPerson">
  <person:profileInformation>A new profile</person:profileInformation>
  <contacts:bambooContact>
    <contacts:contactId>urn:uuid:28ae4ba0-40f2-4ccc-86f9-8577c29005a8</contacts:contactId>
  </contacts:bambooContact>
  <person:interests person:confidential="false">
    <person:interest>An interest</person:interest>
  </person:interests>
  <person:expertises person:confidential="false">
    <person:expertise>An expertise</person:expertise>
  </person:expertises>
  <person:externalAffiliations>http://berkeley.org</person:externalAffiliations>
  <person:preferredLanguage>spa</person:preferredLanguage>
  <person:languageUsedInScholarships>eng</person:languageUsedInScholarships>
  <person:otherProfiles person:confidential="false">
    <person:profileName>Some other profile</person:profileName>
    <person:profileUrl>http://tempuri.org</person:profileUrl>
  </person:otherProfiles>
  <person:authorizedPublisher>true</person:authorizedPublisher>
</person:bambooProfile>
</person:bambooPerson>

Response

On success, a response with a "201 Created" HTTP status code will be returned:

Parameter

Meaning

HTTP Header Location

A URL of the form "http://services.projectbamboo.org/bsp/persons/bambooPersonId/profile/bambooProfileId" where "bambooPersonId" is the Bamboo Person identifier  and "bambooProfileId" is the Bamboo Profile identifier

Exceptions

If an error occurred, some non-2xx code will be returned. Check the HTTP Status Code that is returned in the response's HTTP headers for the specific error. The following errors may be returned in response to the Post request:

Error Status Code

Meaning

Returned when

401

Unauthorized

The resource could not be created because the client submitting the request either has not provided authentication credentials, or authentication failed, or authorization has been refused for those credentials

405

Method Not Allowed

The resource already exists

500

Internal Server Error

A service error prevented the resource from being returned

Read a Person Profile

A client requests a Bamboo Person's profile by submitting the person's unique identifier (i.e. BPId) and the profile's unique identifier (BPPId).

Calling Method and Arguments

Invoked as an HTTP GET method. Send an HTTP request of the form:

GET <url root>/bsp/persons/{bambooPersonId}/profiles/{bambooProfileId} HTTP/1.1

Parameter

Meaning

bambooPersonId

The unique identifier for a Bamboo Person

bambooProfileId

The unique identifier for a Bamboo Profile

Accept Header

application/xml

Example:

GET <url root>/bsp/persons/urn:uuid:9e69b775-7fae-4da7-a66e-2fc61b0bfeab/profiles/urn:uuid:d4fd618e-f430-4776-8dcb-e05c14cf70ea

Response

On success, a response with a "200 OK" HTTP status code will be returned.

Parameter

Meaning

HTTP Body

An instance of a BambooPerson XML document

Example BambooPerson XML document:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<person:bambooPerson xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:bsp="http://projectbamboo.org/bsp/resource" xmlns:contacts="http://projectbamboo.org/bsp/services/core/contact" xmlns:person="http://projectbamboo.org/bsp/BambooPerson" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dcterms:subject/>
    <dcterms:creator xsi:type="dcterms:URI">urn:uuid:99999999-9999-9999-9999-999999999999</dcterms:creator>
    <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-24T09:48:56.307-07:00</dcterms:created>
    <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
    <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-24T09:48:56.323-07:00</dcterms:modified>
    <person:bambooPersonId>urn:uuid:9e69b775-7fae-4da7-a66e-2fc61b0bfeab</person:bambooPersonId>
    <person:bambooProfile person:confidential="false" person:primary="true">
        <dcterms:subject/>
        <dcterms:creator xsi:type="dcterms:URI">urn:uuid:9e69b775-7fae-4da7-a66e-2fc61b0bfeab</dcterms:creator>
        <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-24T09:48:56.323-07:00</dcterms:created>
        <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
        <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-24T09:48:56.323-07:00</dcterms:modified>
        <person:profileId>urn:uuid:d4fd618e-f430-4776-8dcb-e05c14cf70ea</person:profileId>
        <person:profileInformation>A new profile</person:profileInformation>
        <person:bambooPersonId>urn:uuid:9e69b775-7fae-4da7-a66e-2fc61b0bfeab</person:bambooPersonId>
        <contacts:bambooContact>
            <dcterms:subject/>
            <dcterms:creator xsi:type="dcterms:URI">urn:uuid:99999999-9999-9999-9999-999999999999</dcterms:creator>
            <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-24T09:26:01.275-07:00</dcterms:created>
            <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
            <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-24T09:28:40.115-07:00</dcterms:modified>
            <contacts:contactId>urn:uuid:28ae4ba0-40f2-4ccc-86f9-8577c29005a8</contacts:contactId>
            <contacts:contactNote>A modified Poster tested contact</contacts:contactNote>
            <contacts:emails>
                <email>falvarez@berkeley.edu</email>
                <contacts:email>falvarez@berkeley.edu</contacts:email>
            </contacts:emails>
            <contacts:emails>
                <email>falvarez@berkeley.edu</email>
                <contacts:email>falvarez@berkeley.edu</contacts:email>
            </contacts:emails>
            <contacts:displayName></contacts:displayName>
            <contacts:partNames>
                <contacts:partNameType>HONORIFIC_PREFIX</contacts:partNameType>
                <contacts:partNameContent>Mr.</contacts:partNameContent>
                <contacts:partNameLang>eng</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_GIVEN</contacts:partNameType>
                <contacts:partNameContent>Fernando</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_FAMILY_PATERNAL</contacts:partNameType>
                <contacts:partNameContent>Alvarez</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_FAMILY_MATERNAL</contacts:partNameType>
                <contacts:partNameContent>Cadena</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>HONORIFIC_SUFFIX</contacts:partNameType>
                <contacts:partNameContent>PMP</contacts:partNameContent>
                <contacts:partNameLang>eng</contacts:partNameLang>
            </contacts:partNames>
            <contacts:telephones>
                <contacts:telephoneType>VOICE</contacts:telephoneType>
                <contacts:telephoneNumber>415-555-1212</contacts:telephoneNumber>
                <contacts:locationType>HOME</contacts:locationType>
            </contacts:telephones>
            <contacts:telephones>
                <contacts:telephoneType>SMS</contacts:telephoneType>
                <contacts:telephoneNumber>650-555-1212</contacts:telephoneNumber>
                <contacts:locationType>SABBATICAL</contacts:locationType>
            </contacts:telephones>
            <contacts:iMs>
                <contacts:instantMessagingType>SKYPE</contacts:instantMessagingType>
                <contacts:account>falvarez@berkeley.edu</contacts:account>
                <contacts:locationType>WORK</contacts:locationType>
            </contacts:iMs>
            <contacts:addresses>
                <contacts:streetAddress1>123 Main St.</contacts:streetAddress1>
                <contacts:streetAddress2>2nd fl</contacts:streetAddress2>
                <contacts:streetAddress3>By the south window</contacts:streetAddress3>
                <contacts:locality>Berkeley</contacts:locality>
                <contacts:region>CA</contacts:region>
                <contacts:postalCode>94105</contacts:postalCode>
                <contacts:country>USA</contacts:country>
                <contacts:locationType>WORK</contacts:locationType>
            </contacts:addresses>
        </contacts:bambooContact>
        <person:interests person:confidential="false">
            <person:interest>An interest</person:interest>
        </person:interests>
        <person:expertises person:confidential="false">
            <person:expertise>An expertise</person:expertise>
        </person:expertises>
        <person:externalAffiliations>http://berkeley.org</person:externalAffiliations>
        <person:preferredLanguage>spa</person:preferredLanguage>
        <person:languageUsedInScholarships>eng</person:languageUsedInScholarships>
        <person:otherProfiles person:confidential="false">
            <person:profileName>Some other profile</person:profileName>
            <person:profileUrl>http://tempuri.org</person:profileUrl>
        </person:otherProfiles>
        <person:authorizedPublisher>true</person:authorizedPublisher>
    </person:bambooProfile>
</person:bambooPerson>

Exceptions

If an error occurred, some non-2xx code will be returned. Check the HTTP Status Code that is returned in the response's HTTP headers for the specific error. The following errors may be returned in response to the request:

Error (Status Code)

Meaning

Returned When

401

Unauthorized

The resource could not be created because the client submitting the request either has not provided authentication credentials, or authentication failed, or authorization has been refused for those credentials

404

Not Found

The resource requested for reading does not exist

500

Internal Server Error

A service error prevented the resource from being returned

Update a Person Profile

A client updates a Bamboo Person's profile by submitting the person's unique identifier (i.e. bambooPersonId) and an instance of a BambooPerson XML document.

Calling Method and Arguments

Invoked as an HTTP PUT method. Send an HTTP request of the form:

PUT <url root>/bsp/persons/{bambooPersonId}/profiles/{bambooProfileId} HTTP/1.1

Parameter

Meaning

bambooPersonId

The unique identifier for a Bamboo Person

bambooProfileId

The unique identifier for a Bamboo Person's Profile

HTTP Body

An instance of a BambooPerson XML document

Example:

PUT <url root>/bsp/persons/urn:uuid:07da999c-ce38-467a-81ba-9d333b16d080/profiles/urn:uuid:abe0b11e-28c4-4c8a-b590-2c186857388d

Example BambooPerson XML document:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<person:bambooPerson xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:contacts="http://projectbamboo.org/bsp/services/core/contact" xmlns:person="http://projectbamboo.org/bsp/BambooPerson" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <person:bambooPersonId>urn:uuid:07da999c-ce38-467a-81ba-9d333b16d080</person:bambooPersonId>
    <person:bambooProfile person:confidential="false" person:primary="true">
        <person:profileId>urn:uuid:abe0b11e-28c4-4c8a-b590-2c186857388d</person:profileId>
        <person:profileInformation>A newly modified profile</person:profileInformation>
        <person:bambooPersonId>urn:uuid:07da999c-ce38-467a-81ba-9d333b16d080</person:bambooPersonId>
        <contacts:bambooContact>
             <contacts:contactId>urn:uuid:5e58d12c-c012-4ca6-bd2a-de1619948785</contacts:contactId>
        </contacts:bambooContact>
        <person:interests person:confidential="false">
            <person:interest>An interest</person:interest>
        </person:interests>
        <person:expertises person:confidential="false">
            <person:expertise>An expertise</person:expertise>
        </person:expertises>
        <person:externalAffiliations>http://berkeley.org</person:externalAffiliations>
        <person:preferredLanguage>spa</person:preferredLanguage>
        <person:languageUsedInScholarships>eng</person:languageUsedInScholarships>
        <person:otherProfiles person:confidential="false">
            <person:profileName>Some other profile</person:profileName>
            <person:profileUrl>http://tempuri.org</person:profileUrl>
        </person:otherProfiles>
        <person:authorizedPublisher>true</person:authorizedPublisher>
    </person:bambooProfile>
</person:bambooPerson>

 

Response

On success, a response with a "204 No Content" HTTP status code will be returned.

Exceptions

If an error occurred, some non-2xx code will be returned. Check the HTTP Status Code that is returned in the response's HTTP headers for the specific error. The following errors may be returned in response to the request:

Error (Status Code)

Meaning

Returned When

401

Unauthorized

The resource could not be created because the client submitting the request either has not provided authentication credentials, or authentication failed, or authorization has been refused for those credentials

404

Not Found

The resource requested for reading does not exist

500

Internal Server Error

A service error prevented the resource from being returned

Delete a Person Profile

A client deletes a Bamboo Person's profile by submitting the person's unique identifier (i.e. BPId) and the profile's unique identifier (i.e. BPPId).

Calling Method and Arguments

Invoked as an HTTP DELETE method. Send an HTTP request of the form:

DELETE <url root>/bsp/persons/{bambooPersonId}/profiles/{bambooProfileId} HTTP/1.1

Parameter

Meaning

bambooPersonId

The unique identifier for a Bamboo Person

bambooProfileId

The unique identifier for a Bamboo Profile

Accept Header

application/xml

Response

On success, a response with a "200 OK" HTTP status code will be returned.

Exceptions

If an error occurred, some non-2xx code will be returned. Check the HTTP Status Code that is returned in the response's HTTP headers for the specific error. The following errors may be returned in response to the Get request:

Error (Status Code)

Meaning

Returned When

401

Unauthorized

The resource could not be created because the client submitting the request either has not provided authentication credentials, or authentication failed, or authorization has been refused for those credentials

404

Not Found

The resource requested for reading does not exist

500

Internal Server Error

A service error prevented the resource from being returned

List All Profiles for a Bamboo Person

A client requests a list of a Bamboo Person's profiles by submitting the person's unique identifier (i.e. bamboopersonId).

Calling Method and Arguments

Invoked as an HTTP GET method. Send an HTTP request of the form:

GET <url root>/bsp/persons/{bambooPersonId}/profiles HTTP/1.1

Parameter

Meaning

bambooPersonId

The unique identifier for a Bamboo Person

Example:

GET <url root>/bsp/persons/urn:uuid:570a60f3-1ac7-48c3-8984-0d48bdb38923/profiles

Response

On success, a response with a "200 OK" HTTP status code will be returned.

Parameter

Meaning

HTTP Body

An instance of a bambooPerson XML document

XML Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<person:bambooPerson xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:bsp="http://projectbamboo.org/bsp/resource" xmlns:contacts="http://projectbamboo.org/bsp/services/core/contact" xmlns:person="http://projectbamboo.org/bsp/BambooPerson" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dcterms:subject/>
    <dcterms:creator xsi:type="dcterms:URI">urn:uuid:99999999-9999-9999-9999-999999999999</dcterms:creator>
    <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-21T09:41:44.651-07:00</dcterms:created>
    <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
    <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-21T09:41:44.713-07:00</dcterms:modified>
    <person:bambooPersonId>urn:uuid:570a60f3-1ac7-48c3-8984-0d48bdb38923</person:bambooPersonId>
    <person:bambooProfile person:confidential="false" person:primary="false">
        <dcterms:subject/>
        <dcterms:creator xsi:type="dcterms:URI">urn:uuid:570a60f3-1ac7-48c3-8984-0d48bdb38923</dcterms:creator>
        <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-21T09:41:44.713-07:00</dcterms:created>
        <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
        <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-21T09:41:44.713-07:00</dcterms:modified>
        <person:profileId>urn:uuid:5f9a46ed-4840-46be-8ddf-4105da194ff4</person:profileId>
        <person:profileInformation>A new profile</person:profileInformation>
        <person:bambooPersonId>urn:uuid:570a60f3-1ac7-48c3-8984-0d48bdb38923</person:bambooPersonId>
        <contacts:bambooContact>
            <dcterms:subject/>
            <dcterms:creator xsi:type="dcterms:URI">urn:uuid:99999999-9999-9999-9999-999999999999</dcterms:creator>
            <dcterms:created xsi:type="dcterms:W3CDTF">2012-09-21T09:42:49.252-07:00</dcterms:created>
            <bsp:modifier>urn:uuid:99999999-9999-9999-9999-999999999999</bsp:modifier>
            <dcterms:modified xsi:type="dcterms:W3CDTF">2012-09-21T09:42:49.252-07:00</dcterms:modified>
            <contacts:contactId>urn:uuid:412ce852-ed1e-4343-8cab-dd5fd64e8ba3</contacts:contactId>
            <contacts:contactNote>A new Poster tested contact</contacts:contactNote>
            <contacts:emails>
                <email>falvarez@berkeley.edu</email>
                <contacts:email>falvarez@berkeley.edu</contacts:email>
            </contacts:emails>
            <contacts:emails>
                <email>falvarez@berkeley.edu</email>
                <contacts:email>falvarez@berkeley.edu</contacts:email>
            </contacts:emails>
            <contacts:displayName></contacts:displayName>
            <contacts:partNames>
                <contacts:partNameType>HONORIFIC_PREFIX</contacts:partNameType>
                <contacts:partNameContent>Mr.</contacts:partNameContent>
                <contacts:partNameLang>eng</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_GIVEN</contacts:partNameType>
                <contacts:partNameContent>Fernando</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_FAMILY_PATERNAL</contacts:partNameType>
                <contacts:partNameContent>Alvarez</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>NAME_FAMILY_MATERNAL</contacts:partNameType>
                <contacts:partNameContent>Cadena</contacts:partNameContent>
                <contacts:partNameLang>spa</contacts:partNameLang>
            </contacts:partNames>
            <contacts:partNames>
                <contacts:partNameType>HONORIFIC_SUFFIX</contacts:partNameType>
                <contacts:partNameContent>PMP</contacts:partNameContent>
                <contacts:partNameLang>eng</contacts:partNameLang>
            </contacts:partNames>
            <contacts:telephones>
                <contacts:telephoneType>VOICE</contacts:telephoneType>
                <contacts:telephoneNumber>415-555-1212</contacts:telephoneNumber>
                <contacts:locationType>HOME</contacts:locationType>
            </contacts:telephones>
            <contacts:telephones>
                <contacts:telephoneType>SMS</contacts:telephoneType>
                <contacts:telephoneNumber>650-555-1212</contacts:telephoneNumber>
                <contacts:locationType>SABBATICAL</contacts:locationType>
            </contacts:telephones>
            <contacts:iMs>
                <contacts:instantMessagingType>SKYPE</contacts:instantMessagingType>
                <contacts:account>falvarez@berkeley.edu</contacts:account>
                <contacts:locationType>WORK</contacts:locationType>
            </contacts:iMs>
            <contacts:addresses>
                <contacts:streetAddress1>123 Main St.</contacts:streetAddress1>
                <contacts:streetAddress2>2nd fl</contacts:streetAddress2>
                <contacts:streetAddress3>By the south window</contacts:streetAddress3>
                <contacts:locality>Berkeley</contacts:locality>
                <contacts:region>CA</contacts:region>
                <contacts:postalCode>94105</contacts:postalCode>
                <contacts:country>USA</contacts:country>
                <contacts:locationType>WORK</contacts:locationType>
            </contacts:addresses>
        </contacts:bambooContact>
        <person:interests person:confidential="false">
            <person:interest>An interest</person:interest>
        </person:interests>
        <person:expertises person:confidential="false">
            <person:expertise>An expertise</person:expertise>
        </person:expertises>
        <person:externalAffiliations>http://berkeley.org</person:externalAffiliations>
        <person:preferredLanguage>spa</person:preferredLanguage>
        <person:languageUsedInScholarships>eng</person:languageUsedInScholarships>
        <person:otherProfiles person:confidential="false">
            <person:profileName>Some other profile</person:profileName>
            <person:profileUrl>http://tempuri.org</person:profileUrl>
        </person:otherProfiles>
        <person:authorizedPublisher>true</person:authorizedPublisher>
    </person:bambooProfile>
</person:bambooPerson>

Exceptions

If an error occurred, some non-2xx code will be returned. Check the HTTP Status Code that is returned in the response's HTTP headers for the specific error. The following errors may be returned in response to the Get request:

Error (Status Code)

Meaning

Returned When

401

Unauthorized

The resource could not be created because the client submitting the request either has not provided authentication credentials, or authentication failed, or authorization has been refused for those credentials

404

Not Found

The resource requested for reading does not exist

500

Internal Server Error

A service error prevented the resource from being returned

SOA Layer API

See generated Javadoc for this service. Packages are org.projectbamboo.bsp.services.core.person.*.profile.*.