[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



[Web Services]Greg on WS-RF and SOA

转载自: http://jim.webber.name/2004/11/19/b06b3824-925e-456d-9233-b9e8d11bb821.aspx

Greg on WS-RF and SOA This is a fascinating piece from Greg on WS-RF. It's re-assuring that others also believe that Grid and Management are application domains and are not infrastructure, and that ironically using a pure SOA rather objects with angle-brackets would confer significant benefits. Side note: There is a good discussion going on over at the WS-GAF mailing list on stateful Web Services - the gist is that all useful services are stateful, but if you want to make them scalable, robust, and loosely coupled then you should go SOA not resource/object-oriented.



[Web Services]http://jim.webber.name/

http://jim.webber.name/



[Web Services]A Web Service Matchmaker by TOSHIBA

转载自: http://www.agent-net.com/download/index.htm

Web Service Matchmaker



[Semantic Web]为什么rdf:predicate 的 range 为 rdfs:Resource,而不是rdf:Property

{{ // RDF Schema Recommendation( http://www.w3.org/TR/2004/REC-rdf-schema-20040210/#ch_predicate ) 5.3.3 rdf:predicate rdf:predicate is an instance of rdf:Property that is used to state the predicate of a statement. A triple of the form: S rdf:predicate P states that S is an instance of rdf:Statement, that P is an instance of rdf:Property and that the predicate of S is P. The rdfs:domain of rdf:predicate is rdf:Statement and the rdfs:range is


[Semantic Web]About RACER reasoner

{{ // Description Logics for Matchmaking of Services 4.1.2 RACER Reasoner
RACER [9, 10] is the rst reasoner for TBox and ABox for the SHIQ logic. It is
developed at the Computer Science Department of the University of Hamburg.
Like FaCT, it only provides part of the expressiveness that we need for
our application. It is able to deal with multiple TBoxes, but they are not
interconnected. It does not let us de ne a concept in a TBox in terms of concepts or roles from other Tboxes.
RACER does not provide support for a dynamic knowledge base as it is not
possible to add or remove concepts once the classi cation has been done.
Another interesting feature of RACER is its ability to reason about ABoxes.
With our approach to matchmaking this capability is not strictly necessary, as
we only need to reason about concepts, for which TBoxes provide the necessary
abstraction. However, the ability to reason about ABoxes may prove useful
when extending our framework to cover phases of E-Commerce transaction beyond matchmaking. For example, an agreement struck between two parties
following matchmaking and automated negotiation [2], needs full instantiation
of the parameters that originally appeared in the service descriptions. Support
for ABoxes would enable compliance check of the agreement with the negotiation
proposals and with the original service descriptions in turn.
RACER provides a Java API and allows access to the reason



[Semantic Web]About FaCT reasoner

{{ // Description Logics for Matchmaking of Services 4.1.1 FaCT Reasoner
The FaCT [13] system is a DL classi er being developed by Ian Horrocks from the Department of Computer Science at the University of Manchester. It includes
two reasoners for TBoxes, one of them for the SHIQ logic. Therefore, it cannot
deal with individuals or concrete datatype domains, and a description such as
the one in Figure 1 can not be processed with it.
To cope with the limitation of SHIQ, we tried to model nominals, datatypes,
and datatype values as atomic concepts but this can lead to incorrect inferences
[12], not to mention the need to model one atomic concept for each integer.
DAML+OIL uses namespaces and import statements to provide extensibility
and to deal with the distributed nature of the Web. The support in the reasoner
for multiple interconnected TBoxes would solve this problem as we would model
each DAML+OIL ontology in a di erent TBox. Because FaCT does not support
multiple TBoxes we are using fully quali ed names in a single TBox.
Moreover, the knowledge base of the matchmaker will change over time by
addition of new advertisements as well as deletion or modi cation of existing
ones. FaCT deals with the addition of new classes over time, even after classi -
cation has been done, but doesn't provide a mechanism for removing classes in
the classi cation. This is a requirement for our application.
One of the main bene ts



[Semantic Web]RDF Validation Service

转载自: http://www.w3.org/RDF/Validator/

RDF Validation Service Note: this online service has been updated and now supports the Last Call Working Draft specifications issued by the RDF Core Working Group, including datatypes. Deprecated elements and attributes of the standard RDF Model and Syntax Specification are no longer supported. Online Service Enter a URI or paste an RDF/XML document into the following text field and a 3-tuple (triple) representation of the corresponding data model as well as an optional graphical visualization of the data model will be displayed. <?xml version="1.0"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"> <rdf:Description rdf:about="http://www.w3.org/"> <dc:title>World Wide Web Consortium</dc:title> </rdf:Description> </rdf:RDF>



日历 | CALENDAR

«July 2025»
12345
6789101112
13141516171819
20212223242526
2728293031
blog名称:World Wide Web Watch
日志总数:193
评论数量:665
留言数量:75
访问次数:6081368
建立时间:2004年10月30日
站点首页 | 联系我们 | 博客注册 | 博客登陆

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