So one looks at Chiusano's Semantic Web Services Initiative (SWSI)
architecture requirements for Semantic Web Services.  If one is 
putting up a service and one wants automagical connections to be 
made based on the service QoS, etc., one will want to do a 
thorough job with the metadata because what one has may not 
be Googleable, and because one wants to stand out on merit.

If a web service isn't a document, what else would you do 
except UDDI?

len


From: Elliotte Rusty Harold [mailto:elharo@m...]

Beyond the issue of lying metadata, there's a much more important 
distinction between metadata based search engines like the semantic 
web and data based engines like Google. Providing metadata requires 
extra effort which is roughly proportional to the quality and amount 
of the metadata to be provided. There is a noticeable cost for a site 
to add metadata. By contrast, there is negligible cost to provide 
data for Google because this is the same data you're providing 
anyway. Metadata isn't free. The semantic web is going to need to 
provide really significant benefits to content authors to justify the 
added costs of supplying useful metadata. Even if it does, I wouldn't 
be surprised if much metadata is created by tools that screenscrape 
the data and thus guess the appropriate metadata.