1 / 8

OGSA-WG Naming #1 “A Rose by any other name would smell as sweet”

OGSA-WG Naming #1 “A Rose by any other name would smell as sweet”. Proposed OGSA Three Level Scheme. Human -> abstract -> address Addresses represented by WS-Addressing EPR’s Abstract names realized by WS-Naming EPR’s (a profile on WS-Addressing) Human names realized by RNS.

claudia-barrera
Télécharger la présentation

OGSA-WG Naming #1 “A Rose by any other name would smell as sweet”

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. OGSA-WG Naming #1“A Rose by any other name would smell as sweet”

  2. Proposed OGSA Three Level Scheme • Human -> abstract -> address • Addresses represented by WS-Addressing EPR’s • Abstract names realized by WS-Naming EPR’s (a profile on WS-Addressing) • Human names realized by RNS

  3. Abstract Name Desirable Properties • Widely adopted • Unique • Comparable • Location portable • Scalable – high performance • Extensible • Dynamic binding • …

  4. WS-Naming • A profile on WS-Addressing EPR’s • Adds two extensibility elements • Existing tooling that uses EPR’s would also work using WS-naming EPR’s

  5. Two elements • AbstractName • Unique in space and time • Strings • Comparable == only • ReferenceResolver • Must be able to map abstract name to an EPR if it is possible (named entity may no longer exist) • Is also an EPR • EPR resolve(AbstractName) • EPR resolve(EPR)

  6. Simple example <wsa:EndpointReference xmlns:wsa=”http://www.w3.org/2005/02/addressing” xmlns:name=”http://tempuri.org/”> <wsa:Address>http://tempura.org/example</wsa:Address> <wsa:Policies> <name:AbstractName>urn:guid:B94C4186-0923-4dbb-AD9C-39DFB8B54388</name:AbstractName> </wsa:Policies> </wsa:EndpointReference>

  7. <wsa:EndpointReference xmlns:wsa=”http://www.w3.org/2005/02/addressing” xmlns:name=”http://tempuri.org/”> <wsa:Address>http://tempura.org/example</wsa:Address> <wsa:Policies> <name:AbstractName>urn:guid:B94C4186-0923-4dbb-AD9C-39DFB8B54388</name:AbstractName> <name:ReferenceResolver> <wsa:Address>http://tempura.org/resolver1</wsa:Address> </name:ReferenceResolver> </wsa:Policies> </wsa:EndpointReference> More Complex Example

  8. Most complex example <wsa:EndpointReference xmlns:wsa=”http://www.w3.org/2005/02/addressing” xmlns:name=”http://tempuri.org/”> <wsa:Address>http://tempuri.org/example</wsa:Address> <wsa:Policies> <name:AbstractName>urn:guid:B94C4186-0923-4dbb-AD9C-39DFB8B54388</name:AbstractName> <name:ReferenceResolver> <wsa:Address>http://tempura.org/resolver1</wsa:Address> <wsa:ReferenceParameters> guid:8733111B-84FA-4da8-89FE-417932B3B92C </wsa:ReferenceParameters> <wsa:Policies> <name:AbstractName>urn:guid:55AD06F6-2F35-409a-9DCE-E5F304E557AA</name:AbstractName> <name:ReferenceResolver> <wsa:Address>http://tempura.org/resolve2</wsa:Address> </name:ReferenceResolver> </wsa:Policies> </name:ReferenceResolver> </wsa:Policies> </wsa:EndpointReference>

More Related