RE: targetResource wording

It's also worth considering what would you do if WSDL 1.2 did *not* provide 
a targetResource attribute.  If that were the case, then presumably you 
would have a database for indicating relationships between services, 
containing information like:

PrinterService427 is-a-printer-service-for HPLaserJet6000/SN5654023498.
PrinterService428 is-a-printer-service-for HPLaserJet3200/SN1235654007.
PrinterService429 is-a-printer-service-for HPLaserJet9100/SN5456129834.
...
ManagementService3455 is-a-management-service-for HPLaserJet6000/SN5654023498.
ManagementService3456 is-a-management-service-for HPLaserJet3200/SN1235654007.
ManagementService3457 is-a-management-service-for HPLaserJet9100/SN5456129834.
...

Then, to look for the printer management service that corresponds to 
PrinterService428, you would:

1. Look for a statement of the form
"PrinterService428 is-a-printer-service-for ___."
and find:
PrinterService428 is-a-printer-service-for HPLaserJet3200/SN1235654007.

2.  Then you would look for a statement of the form
"___ is-a-management-service-for HPLaserJet3200/SN1235654007."
and find:
ManagementService3456 is-a-management-service-for HPLaserJet3200/SN1235654007.
Therefore, you conclude that ManagementService3456 is the one you want.

(Of course, each of the terms expressed above should actually be a URI or a 
namespace-qualified name, in order to be unambiguous.)

RDF is ideal for this, but of course you don't have to use RDF.  A 
conventional relational database work fine also.


-- 
David Booth
W3C Fellow / Hewlett-Packard
Telephone: +1.617.253.1273

Received on Friday, 20 June 2003 16:51:20 UTC