According When a Home Bridging Element releases local attributes to the bridged model of EduGAINa Remote Bridging Element, some attribute transformation and attribute filtering should take place. Similarly, SPs treat Remote Bridging Elements as ordinary IdPs of the federation they belong BE has to filter out unnecessary/unwanted attributes and transform the same applies remaining according to the relation between RBE <-> HBE and HBE <-> IdPits federation's rules.
== Conversion ==
Regardless of attribute representation of each federation (eg. Attribute Certificates or simple string values), users want to transport the ''information'' included in attribute values. The aim of attribute conversion is to let BE administrators be able to define rules for including and extracting information into/from attributes that can be handled by both federations.
When a Home Bridging Element releases local attributes to a remote federationIt is worth noting that inside the two federations they can embed* the same information into different attribute-value pairs, some attribute transformation and attribute filtering must take placeeg. Similarly, Remote BE has to filter out unnecessary<code>fooFedHospitalWard: urn:foo:surgery</unwanted attributes code> and transform <code>barFedAbteilung: urn:bar:Chirurgie</code> could carry the remaining according to its federation's rules.same information ("a medical institution has surgical ward"), while == Conversion ===== Approaches ===Ways of solving * the same attribute conversion problem from simple to advanced=== Limited set of common attributes ====== Customized attribute conversion done BE's ====== Metadata-based attribute conversion service ===value pairs can carry different information, eg. <code>eduPersonAffiliation: student</code>
