„JRA5Attributes” változatai közötti eltérés
(rubbish) |
(not yet ready) |
||
| 1. sor: | 1. sor: | ||
| − | + | When a Home Bridging Element releases local attributes to a Remote Bridging Element, some attribute transformation and attribute filtering should take place. Similarly, Remote BE has to filter out unnecessary/unwanted attributes and transform the remaining according to its 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. | ||
| − | + | It is worth noting that inside the two federations they can embed | |
| − | + | * the same information into different attribute-value pairs, eg. <code>fooFedHospitalWard: urn:foo:surgery</code> and <code>barFedAbteilung: urn:bar:Chirurgie</code> could carry the same information ("a medical institution has surgical ward"), while | |
| − | + | * the same attribute-value pairs can carry different information, eg. <code>eduPersonAffiliation: student</code> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
A lap 2007. november 26., 09:33-kori változata
When a Home Bridging Element releases local attributes to a Remote Bridging Element, some attribute transformation and attribute filtering should take place. Similarly, Remote BE has to filter out unnecessary/unwanted attributes and transform the remaining according to its 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.
It is worth noting that inside the two federations they can embed
- the same information into different attribute-value pairs, eg.
fooFedHospitalWard: urn:foo:surgeryandbarFedAbteilung: urn:bar:Chirurgiecould carry the same information ("a medical institution has surgical ward"), while - the same attribute-value pairs can carry different information, eg.
eduPersonAffiliation: student
