中文XML论坛--语义web服务中本体的作用

贴子主题：语义web服务中本体的作用

本主题类别: Ontology Engineering | RDF/RDFS | Web Services

从axis构建web服务到转换成owl-s以后，感觉了一下这个本体的作用，但不知道理解的对不对，请高手指教，owl-s是web服务的本体语言，owl是知识库的本体语言（自己的理解），用owl构造一个领域本体（owl结构上类似于rdfs），然后在生成的owl-s的服务本体文件中就可以使用owl构造的领域本体里面的概念和属性来描述自己的服务了，举个例子：
现在有一个关于旅游的知识库的本体owl
<?xml version="1.0"?>
<rdf:RDF
    xmlns="http://keg.cs.tsinghua.edu.cn/ontology/travel#"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
    xmlns:owl="http://www.w3.org/2002/07/owl#"
  xml:base="http://keg.cs.tsinghua.edu.cn/ontology/travel">
  <owl:Ontology rdf:about=""/>
  <owl:Class rdf:ID="CarNum">
    <rdfs:subClassOf>
      <owl:Class rdf:ID="CarDomain"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:ID="Date">
    <rdfs:subClassOf>
      <owl:Class rdf:ID="DomainIndependent"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:about="#CarDomain">
    <rdfs:subClassOf>
      <owl:Class rdf:ID="SubDomain"/>
    </rdfs:subClassOf>
  </owl:Class>
  <owl:Class rdf:ID="ReserveConfirm">
    <rdfs:subClassOf>
      <owl:Class rdf:ID="ConfirmInfo"/>
    </rdfs:subClassOf>
  </owl:Class>
.....................................................
(这个不是我小气，是因为这是实验室的资料，所以不方便说太多)
接着我做了一个旅游方面的服务（checkhotel.owl这个服务文件）这里贴出主要的部分：
<grounding:wsdlInputMessageParts rdf:parseType="Collection">
                  <grounding:wsdlMessageMap>
                    <grounding:wsdlMessagePart>hotelarea</grounding:wsdlMessagePart>
                    <grounding:owlsParameter>
                      <process:Input rdf:ID="in0">
                        <rdfs:label>hotelarea</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#Address"/>
                      </process:Input>
                    </grounding:owlsParameter>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:wsdlMessagePart>entrancedate</grounding:wsdlMessagePart>
                    <grounding:owlsParameter>
                      <process:Input rdf:ID="in1">
                        <rdfs:label>entrancedate</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#Date"/>
                      </process:Input>
                    </grounding:owlsParameter>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:owlsParameter>
                      <process:Input rdf:ID="in2">
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#HotelType"/>
                        <rdfs:label>hotelgrade</rdfs:label>
                      </process:Input>
                    </grounding:owlsParameter>
                    <grounding:wsdlMessagePart>hotelgrade</grounding:wsdlMessagePart>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:owlsParameter>
                      <process:Input rdf:ID="in3">
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#RoomType"/>
                        <rdfs:label>roomgrade</rdfs:label>
                      </process:Input>
                    </grounding:owlsParameter>
                    <grounding:wsdlMessagePart>roomgrade</grounding:wsdlMessagePart>
                  </grounding:wsdlMessageMap>
                </grounding:wsdlInputMessageParts>
                <grounding:wsdlOperation>
                  <grounding:WsdlOperationRef>
                    <grounding:portType>CheckHotelPort</grounding:portType>
                    <grounding:operation>CheckHotel</grounding:operation>
                  </grounding:WsdlOperationRef>
                </grounding:wsdlOperation>
                <grounding:wsdlOutputMessageParts rdf:parseType="Collection">
                  <grounding:wsdlMessageMap>
                    <grounding:owlsParameter>
                      <process:Output rdf:ID="out0">
                        <rdfs:label>hotelname</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#HotelName"/>
                      </process:Output>
                    </grounding:owlsParameter>
                    <grounding:wsdlMessagePart>hotelname</grounding:wsdlMessagePart>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:wsdlMessagePart>hoteladdress</grounding:wsdlMessagePart>
                    <grounding:owlsParameter>
                      <process:Output rdf:ID="out1">
                        <rdfs:label>hoteladdress</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#Address"/>
                      </process:Output>
                    </grounding:owlsParameter>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:wsdlMessagePart>hoteltel</grounding:wsdlMessagePart>
                    <grounding:owlsParameter>
                      <process:Output rdf:ID="out2">
                        <rdfs:label>hoteltel</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#Phone"/>
                      </process:Output>
                    </grounding:owlsParameter>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:owlsParameter>
                      <process:Output rdf:ID="out3">
                        <rdfs:label>leftroom</rdfs:label>
                        <process:parameterType rdf:resource="http://www.w3.org/2001/XMLSchema#int"/>
                      </process:Output>
                    </grounding:owlsParameter>
                    <grounding:wsdlMessagePart>leftroom</grounding:wsdlMessagePart>
                  </grounding:wsdlMessageMap>
                  <grounding:wsdlMessageMap>
                    <grounding:wsdlMessagePart>roomprice</grounding:wsdlMessagePart>
                    <grounding:owlsParameter>
                      <process:Output rdf:ID="out4">
                        <rdfs:label>roomprice</rdfs:label>
                        <process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#Fare"/>
                      </process:Output>
                    </grounding:owlsParameter>
                  </grounding:wsdlMessageMap>
                </grounding:wsdlOutputMessageParts>
里面关于输入和输出部分的参数类型
<process:parameterType rdf:resource="http://localhost:8080/travelontology/travel#.../>
通过这个我对本体在语义web服务中的理解：
我觉得本体在语义web服务中的作用应该是用本体中定义的一些概念来描述我们服务的本体，比如说例子中是用旅游的知识库本体中的概念Address,HotelType等概念来描述它的输入参数类型的，可能在Address这种参数类型中包含城市，街道，房门号等信息，而这些信息的类型都是String类型的，这里是不是应该使用jena对旅游本体操作来推理出Address类型所包含的信息的类型，然后从用户输入的数据来提取相关的信息数据，这里比较晕，希望各位可以指教指教


	W 3 C h i n a ( since 2003 ) 旗下站点苏ICP备05006046号《全国人大常委会关于维护互联网安全的决定》《计算机信息网络国际联网安全保护管理办法》	125.000ms