[Web Services]repository vs. registry 

在Web服务领域中,这两个词常常交换使用,不过还是稍有区别: (1)repository译为仓库;registry译为注册库 (2)registry通常是简单的service列表——即一种提供了各个服务可以在其上注册,以被发现的机制。 repository则不仅仅是一个服务注册库(registry),还包含相应的服务元数据(metadata)。  

阅读全文(3939) | 回复(0) | 编辑 | 精华 | 删除

[Web Services]"Web Services Definition Language" 是如何诞生的

WSDL的全称应该是:Web Services Description Language 不过也许大家已经发现了,有些web pages甚至papers,books中时而提到WSDL(Web Services Definition Language),Description和Definition不仅长得比较“像”,读音,含义也颇为类似,因此误用是很容易发生的。 相信许多发现同时存在**Definition*与**Description*两种说法的人,都会通过Google进行确认,不过搜索结果是令人迷惑的,因为搜索Web Services Definition Language,返回的第1条记录是W3C。搜索Web Services Description Language第一条记录也是W3C。那么究竟是Definition 还是Description 呢? 原因是W3C在发布Web Services Description Language (WSDL) 1.1 W3C Note 15 March 2001(http://www.w3.org/TR/2001/NOTE-wsdl-20010315)时,把网页的title错写成Web Services Definition Language了。 附W3C对此事的说明:  http://lists.w3.org/Archives/Public/site-comments/2002May/0017.html

[Web Services]微软声称不会支持SAML 2.0; SAML 2 vs. WS-Federation

转载自: http://xml.coverpages.org/saml.html

[November 17, 2005] "Microsoft Says It Won't Support SAML 2.0. Microsoft Backs WS-Federation Protocols for Next Generation of Message-Based Apps." By Jeremy Kirk. From InfoWorld (November 17, 2005). "Microsoft will stick by the set of protocols it has picked for identity federation, a concept that includes single sign-on (SSO) for several different Web portals and secure transfers of data between partnered businesses. Microsoft has backed WS-Federation protocols for the next generation of message-based applications because it offers a full suite of security, message, and transaction protocols, said Don Schmidt, senior program manager for Microsoft's Identity and Access group. The company's stance is not about which protocol set is necessarily better but rather which offers a wider flexibility in accommodating federated identity... The WS-Federation protocols compete with the SAML (Security Assertion Markup Language) 2.0 specification, which so far has strong footing in the race to create secured identity federation across organizations. SAML 2.0 is backed by consortiums such as the Liberty Alliance and the Organization for the Advancement of Structu

[Web Services][收藏]了解 WS-Security -- 作者:admin

本文转载自W3CHINA.ORG讨论区(BBS.W3CHINA.ORG)   原文链接

了解 WS-Security Scott Seely
Microsoft Corporation
Web 服务规范(WS-Security、WS-Security Addendum) 摘要:本文介绍如何使用 WS-Security 在 SOAP 消息中嵌入安全机制,并介绍 WS-Security 所涉及的三个方面:身份验证、签名和加密。 目录
对 SOAP 消息应用现有概念
WS-Security SOAP 标头

[Web Services]Data on the Outside versus Data on the Inside ( 2005 )

* web services仅仅通过消息(message)与其他web services通信。 * 相互通信的web services,只了解通信的 消息格式 和 消息顺序,而对于web services的实现则不关心。

[Web Services]一些著名的 Service Classification

UNSPSC RosettaNet EMBOSS(生物信息学方面的)  

[Web Services]A java based API for OWL-S 1.1 by SemWebCentral.org

转载自: http://projects.semwebcentral.org/projects/owl-s-api/

A java based API for OWL-S
Environment: Console (Text Based) Interface: API Programming Language: Java Semantic Web Tool Categories: API

[Web Services]MindSwap OWL-S API

转载自: http://www.mindswap.org/2004/owl-s/api/

OWL-S API OWL-S API provides a Java API for programmatic access to read, execute and write OWL-S (formerly known as DAML-S) service descriptions. The API supports to read different versions of OWL-S (OWL-S 1.0, OWL-S 0.9, DAML-S 0.7) descriptions. The API provides an ExecutionEngine that can invoke AtomicProcesses that has WSDL or UPnP groundings, and CompositeProcecesses that uses control constructs Sequence, Unordered, and Split. Executing processes that relies on conditionals such as If-Then-else and RepeatUntil is not supported in the default implementation. But this implementation can be extended to handle these constructs if the application that uses the OWL-S descriptions has a custom syntax and evaluation procedure for the c

[Web Services]Critics Say Web Services Need a REST

转载自: http://dsonline.computer.org/0412/d/oz001a.htm

Critics Say Web Services Need a REST Greg Goth Just as Web Services’ allure appears to have reached critical mass with developers and enterprise customers, a passionate debate about the efficiency of the technologies underlying the much-ballyhooed distributive infrastructure has rekindled. A vocal group of developers critical of the orthodox Web Services stack is touting the use of a technology called REST, or Representational State Transfer Web Services. REST eschews the orthodox SOAP Web Services stack for a more streamlined (and familiar) XML-over-HTTP approach for exposing software functionality. While researchers had explored ad hoc REST implementations in the 1990s, the comprehensive theoretical underpinning for REST first appeared in 2000 in a doctoral dissertation written by Roy Fielding, chief scientist for Day Software and a cofounder of the Apache Software Foundation. Developers involved in the early days of writing Web Services specifications debated REST’s principles, which posited(提出) that using the World Wide Web’s protocols for a distributed environment wou

[Web Services]SOAP yes, SOA, no?

转载自: http://www.orablogs.com/pavlik/archives/000654.html

SOAP yes, SOA, no? In a number of private and in sometimes public exchanges on what's going on with WS-Resource Framework, I keep getting bogged down in very fine grained arguments. These tend to be about nuances in WSDL, whether such a thing as a normal model for services exists, and models for communicating session information in the Web services environment. While these conversations are important and fundamental, I fear that the really big issue is lost in the details: what is the real design center for service-oriented systems in general and for Web services in particular? A high level point of distinction between service orientation and resource orientation: SOA-based WSDL advertises what messages a service will accept and (potentially) how that service may respond. Resource oriented services have WSDL that specifically deals with operations that effect referenced resources. Though there is supposed to be a distinction between services and resources they manage, it's really a facade: the interface described in WSDL is the interface of the resource. The reference that clients have is a reference to a resource (hence, the WS-Addressing embodiment in WS-Resource: formally known as the Implied

« 1 2 »


blog名称:World Wide Web Watch
站点首页 | 联系我们 | 博客注册 | 博客登陆

Sponsored By W3CHINA
W3CHINA Blog 0.8 Processed in 0.047 second(s), page refreshed 144516795 times.
《全国人大常委会关于维护互联网安全的决定》  《计算机信息网络国际联网安全保护管理办法》