1 / 9

SCIM and vCard mapping draft- greevenbosch - scim - vcard -mapping-00

SCIM and vCard mapping draft- greevenbosch - scim - vcard -mapping-00. Bert Greevenbosch. Scope. The document draft- greevenbosch - vcard -mapping-00 defines a mapping from SCIM to vCard and vice versa. The mapping has several purposes:

axelle
Download Presentation

SCIM and vCard mapping draft- greevenbosch - scim - vcard -mapping-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCIM and vCard mappingdraft-greevenbosch-scim-vcard-mapping-00 Bert Greevenbosch

  2. Scope • The document draft-greevenbosch-vcard-mapping-00 defines a mapping from SCIM to vCard and vice versa. • The mapping has several purposes: • Provide a unified conversion mechanism between SCIM and vCard. • Identify properties that are defined in vCard, but are missing in SCIM. • Identify SCIM attributes that may be useful in vCard too. • Serve as guidance to consider whether vCard can be used as a basis for SCIM. • Provide discussion material on whether vCard could replace the SCIM schema completely. • V01 will be uploaded soon after the meeting.

  3. Overview • The draft contains two main sections: • Mapping from SCIM to vCard; • Mapping from vCard to SCIM. • Reason: some fields in SCIM may not be available in vCard, whereas others may be available in vCard but not in SCIM. • Two tables allow easy identification of those missing fields from both sides.

  4. Updates coming in v01 • SCIM “organization”, “division” and “department” are mapped to a single vCard “ORG” field. • SCIM “addr/formatted” are mapped to vCard “LABEL” field. • Note to the “N” property is removed, as “N” field can be unambiguously dissected into family, given, additional, prefixes and suffixes components. • Typos fixed. • Added references to RFC 6473, 6474 and 6715. • Added related fields to vCard -> SCIM table.

  5. New fields fromRFCs 6473, 6474 and 6715 • RFC 6473 adds vCard KIND property value “application”. • RFC 6474 adds BIRTHPLACE, DEATHPLACE and DEATHDATE. • RFC 6715 adds EXPERTISE, HOBBY, INTEREST, ORG-DIRECTORY properties, as well as INDEX and LEVEL parameters.

  6. Mappings of IDs: SCIM -> vCard • The SCIM ID and vCard ID could be generated from each other. • Since they are pointing to different entities, they should be different. • vCard IDs should be globally unique, whereas SCIM IDs must only be unique among a service provider. • Proposal for conversion of IDs from SCIM to vCard: • UID:scim:serviceProviderID:scimID • e.g. For the service provider “IndentityServe” and SCIM ID “12345” the vCard ID would be “UID:scim:IdentityServe:12345”.

  7. Mappings of IDs: vCard -> SCIM • From vCard ID to SCIM ID could be done by adding a vCard prefix. • e.g. The vCard ID“UID:urn:uuid:dd418720-c754-4631-a869-db89d02b831b”could become “vCard:UID:urn:uuid:dd418720-c754-4631-a869-db89d02b831b” • This manner allows circular mapping from vCard -> SCIM -> vCard without confusion of the versions.

  8. Open issues • Proposal to map SCIM “manager/managerID” to vCard “RELATED”. • This would require registration of the TYPE “manager” for vCard with IANA. • In general, what to do with unmappable fields? • The relationship between vCard and SCIM?

  9. Thank you!Questions?

More Related