When I want to find a "Big" Web service (WS-*/WSDL based) of required functionality I can simply google for ".... filetype:wsdl" because Google indexes also WSDL definitions. Or I can simply use some registries that already crawled the Web for WSDL definitions for me, e.g. SeekDa.com or ServiceFinder.
当我想找到所需功能的“大”Web服务（基于WS - * / WSDL）时，我可以简单地谷歌搜索“.... filetype：wsdl”，因为Google也会索引WSDL定义。或者我可以简单地使用一些已经抓取Web的注册表来为我提供WSDL定义，例如SeekDa.com或ServiceFinder。
When I want to find RESTful Web service (RESTful Web API) I may count only on the community, because it is not possible to distinguish between URI of RESTful Web service and other Web resources (e.g. Web sites URLs) and hence any focused crawler cannot tell for 100% sure: this is URI of RESTful Web service. So, I come e.g. to the ProgrammableWeb.com and I hope someone already used/found the service I'm looking for and registered it there.
当我想找到RESTful Web服务（RESTful Web API）时，我可能只关注社区，因为无法区分RESTful Web服务的URI和其他Web资源（例如Web站点URL），因此任何聚焦的爬虫都不能告诉我100％肯定：这是RESTful Web服务的URI。所以，我来了，例如到ProgrammableWeb.com，我希望有人已经使用/找到我正在寻找的服务并在那里注册。
Recently, I was looking for the Web service for abbreviation expansion. I couldn't find it in portals like ProgrammableWeb, because no-one has put it there. Finally I was forced to browse through several abbreviation dictionaries sites, dig and drill there and I finally found Abbreviations.com Web service API in RESTful form. That took me a lot of time!
最近，我一直在寻找缩写扩展的Web服务。我在ProgrammableWeb这样的门户网站中找不到它，因为没有人把它放在那里。最后，我*浏览了几个缩写词典网站，在那里挖掘和钻取，最后我找到了RESTful形式的Abbreviations.com Web服务API。这花了我很多时间！
Is there any other Way to discover RESTful Web services on the Web?
有没有其他方法可以在网上发现RESTful Web服务？
4 个解决方案
#1
10
The REST ideal is that services are as consumable as Web Pages are, they don't need registries. [Got to admit I don't fully "get" the implications of this RESTful world, no WSDL, no registry feels like riding a bike with no stabilisers.]
REST的理想是服务与Web页面一样可用，它们不需要注册表。 [必须承认我没有完全“了解”这个RESTful世界的含义，没有WSDL，没有注册表感觉就像骑自行车而没有稳定器。]
In the old Web, pre-Google, how did we find pages? Effectively word-of-mouth and a few key starting points. REST services so far as I can see are pretty much in the pre-Google stage.
在旧网站上，谷歌之前，我们是如何找到网页的？有效的口碑和一些关键的起点。据我所知，REST服务几乎都处于谷歌之前的阶段。
I don't agree that "it is not possible to distinguish between URI of RESTful Web service and other Web resources" - if we follow the link we get certain types of content application/xml and application/json would be pretty strong indicators wouldn't they?
我不同意“不可能区分RESTful Web服务的URI和其他Web资源” - 如果我们按照链接我们得到某些类型的内容application / xml和application / json将是非常强大的指标wouldn'他们？
#2
10
There is a convention (recommended in REST API Design Handbook for example) that you expose a /api endpoint at the root of your service. This returns an XML or JSON response containing the "child" resources that your service supports e.g. /api/products
有一个约定（例如，在REST API设计手册中推荐），您可以在服务的根目录中公开/ api端点。这将返回包含您的服务支持的“子”资源的XML或JSON响应，例如/ API /产品
#3
9
There's a WSDL-like file for REST webservices: it's called WADL.
REST webservices有一个类似WSDL的文件：它叫做WADL。
#4
2
SoapUI now can discover the REST services. It works as a proxy, writing down all requests/responses that pass through. Having requests and responses SoapUI recreates descriptions/definitions of the services. Now the definitions can be stored in WADL and WSDL formats (as WSDL and XML-Schema in XML world). It also can be stored in Swagger format. I prefer Swagger. Swagger can be stored in SwaggerHub right from SoapUI, which is like GitHub for source code. SwaggerHub is one of many API management systems.
SoapUI现在可以发现REST服务。它作为代理，写下所有通过的请求/响应。有请求和响应SoapUI重新创建服务的描述/定义。现在，定义可以以WADL和WSDL格式存储（如XML世界中的WSDL和XML-Schema）。它也可以以Swagger格式存储。我更喜欢Swagger。 Swagger可以直接从SoapUI存储在SwaggerHub中，就像GitHub的源代码一样。 SwaggerHub是众多API管理系统中的一种。
#1
10
The REST ideal is that services are as consumable as Web Pages are, they don't need registries. [Got to admit I don't fully "get" the implications of this RESTful world, no WSDL, no registry feels like riding a bike with no stabilisers.]
REST的理想是服务与Web页面一样可用，它们不需要注册表。 [必须承认我没有完全“了解”这个RESTful世界的含义，没有WSDL，没有注册表感觉就像骑自行车而没有稳定器。]
In the old Web, pre-Google, how did we find pages? Effectively word-of-mouth and a few key starting points. REST services so far as I can see are pretty much in the pre-Google stage.
在旧网站上，谷歌之前，我们是如何找到网页的？有效的口碑和一些关键的起点。据我所知，REST服务几乎都处于谷歌之前的阶段。
I don't agree that "it is not possible to distinguish between URI of RESTful Web service and other Web resources" - if we follow the link we get certain types of content application/xml and application/json would be pretty strong indicators wouldn't they?
我不同意“不可能区分RESTful Web服务的URI和其他Web资源” - 如果我们按照链接我们得到某些类型的内容application / xml和application / json将是非常强大的指标wouldn'他们？
#2
10
There is a convention (recommended in REST API Design Handbook for example) that you expose a /api endpoint at the root of your service. This returns an XML or JSON response containing the "child" resources that your service supports e.g. /api/products
有一个约定（例如，在REST API设计手册中推荐），您可以在服务的根目录中公开/ api端点。这将返回包含您的服务支持的“子”资源的XML或JSON响应，例如/ API /产品
#3
9
There's a WSDL-like file for REST webservices: it's called WADL.
REST webservices有一个类似WSDL的文件：它叫做WADL。
#4
2
SoapUI now can discover the REST services. It works as a proxy, writing down all requests/responses that pass through. Having requests and responses SoapUI recreates descriptions/definitions of the services. Now the definitions can be stored in WADL and WSDL formats (as WSDL and XML-Schema in XML world). It also can be stored in Swagger format. I prefer Swagger. Swagger can be stored in SwaggerHub right from SoapUI, which is like GitHub for source code. SwaggerHub is one of many API management systems.
SoapUI现在可以发现REST服务。它作为代理，写下所有通过的请求/响应。有请求和响应SoapUI重新创建服务的描述/定义。现在，定义可以以WADL和WSDL格式存储（如XML世界中的WSDL和XML-Schema）。它也可以以Swagger格式存储。我更喜欢Swagger。 Swagger可以直接从SoapUI存储在SwaggerHub中，就像GitHub的源代码一样。 SwaggerHub是众多API管理系统中的一种。