Talk:Web Services Discovery

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Changes[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
Merge UDDI into Web Services Discovery. Klbrain (talk) 09:39, 28 April 2016 (UTC)[reply]

In addition to the clarification just made I'd suggest to note that pubic UDDI has not gained the importance anticipated for public services (e.g. indicate by the shutdown of major uddi repositories http://www.infoworld.com/article/05/12/16/HNuddishut_1.html). — Preceding unsigned comment added by Hollau (talkcontribs) 16:11, 27 December 2007 (UTC)[reply]

This is mentioned and cited at Universal Description Discovery and Integration. At this point, it may be appropriate to consolidate articles. I'll put up some merge banners. --Kvng (talk) 23:33, 6 January 2012 (UTC)[reply]

Moreover a separation into public/private service discovery scenarios might be useful (since UDDI is still pushed by EAI vendors). — Preceding unsigned comment added by Hollau (talkcontribs) 16:11, 27 December 2007 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The extra section on federated discovery seems not to be well motivated. However more details on approaches discussed in academia might be useful such as semantic service discovery (e.g. sketeched here http://webservices.sys-con.com/read/39718.htm) or approaches where discovery is seen as a protocol such as ws-discovery (http://specs.xmlsoap.org/ws/2005/04/discovery/ws-discovery.pdf), as well as pragmatic approaches of vertical search engines or portals that use standard IR techniques for Web Service Discovery. — Preceding unsigned comment added by Hollau (talkcontribs) 16:11, 27 December 2007 (UTC)[reply]

As relates to Federated Web Services, which redirects here, perhaps there's a distinction between the technological back end described here and the user experience of federated services (comparing email with a centralized service like Facebook or Twitter)Jason Green (talk) 19:36, 7 January 2015 (UTC)[reply]
I agree and do not think UDDI should have been merged into this since it can also be accomplished via WS-Discovery (and was stated in the original content before the merge). The merge now conflates and confuses the issues. UDDI and WS-Discovery are both OASIS standards but the general concept of web services discovery is not (and is more closely associated with concept zero-configuration networking). I recommend re-splitting the UDDI content back out. 50.53.1.21 (talk) 16:09, 25 October 2017 (UTC)[reply]

Title caps is so pretentious[edit]

This article can't possibly deserve title caps.

It's this kind of nonsense that made the AP Stylebook update so long overdue. — MaxEnt 21:19, 13 January 2017 (UTC)[reply]

Most network protocols get title caps here on WP. ~Kvng (talk) 15:04, 16 January 2017 (UTC)[reply]

So confusing I misunderstood its purview[edit]

My personal objective was to classify Consul and Zookeeper. They are both consensus-based discovery services. Turns out, the Wikipedia page at service discovery is but a nasty little list that presently doesn't do the topic any justice whatsoever.

Here, because of the generic nature of the first lead sentence, I thought it really was about web service discovery. Only to later realize that Web Services Discovery is some kind of semi-formal UDDI buzzword, of the kind that Microsoft is so good at promulgating (e.g. Active X, where X stands for any damn thing).

The cloud is a thing these days, and it really would be a good idea to have an article devoted to cloud/datacenter fault-tolerant service/micro-service discovery. But I can't even see how to get there until this mess is cleaned up. — MaxEnt 21:49, 13 January 2017 (UTC)[reply]