Provider may need to know requester's profile.

[Gary P Cole <Gary.P.Cole@Sun.COM>]

An SPML profile represents a set of assumptions about how requestor and 
provider will use SPML.  The requestor should probably pass a profile 
identifier in with a listTargetsRequest.  The provider may want to 
expose a different set of targets for each profile.

For example, suppose that a provider can expose the same target (system 
or application) with either native XML schema *or* with the DSMLv2 
schema model.  If the provider knows what the requestor wants or 
expects, the provider can return a target that suits the requestor's 
profile.

Otherwise, I guess the provider could return both targets (even if both 
represent the same underlying system or application) and let the 
requestor decide, based on each target's schema, which target the 
requestor prefers.