新书推介:《语义网技术体系》
作者:瞿裕忠,胡伟,程龚
   XML论坛     W3CHINA.ORG讨论区     计算机科学论坛     SOAChina论坛     Blog     开放翻译计划     新浪微博  
 
  • 首页
  • 登录
  • 注册
  • 软件下载
  • 资料下载
  • 核心成员
  • 帮助
  •   Add to Google

    >> 本版讨论Semantic Web(语义Web,语义网或语义万维网, Web 3.0)及相关理论,如:Ontology(本体,本体论), OWL(Web Ontology Langauge,Web本体语言), Description Logic(DL, 描述逻辑),RDFa,Ontology Engineering等。
    [返回] 中文XML论坛 - 专业的XML技术讨论区W3CHINA.ORG讨论区 - Web新技术讨论『 Semantic Web(语义Web)/描述逻辑/本体 』 → 关于启动翻译 W3C RDF Primer 的倡 议(完成初审,欢迎大家Review) 查看新帖用户列表

      发表一个新主题  发表一个新投票  回复主题  (订阅本版) 您是本帖的第 432299 个阅读者浏览上一篇主题  刷新本主题   树形显示贴子 浏览下一篇主题
     * 贴子主题: 关于启动翻译 W3C RDF Primer 的倡 议(完成初审,欢迎大家Review) 举报  打印  推荐  IE收藏夹 
       本主题类别:     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客81
    发贴心情 

    我准备开始翻译4。1;4。2 了,大家不要和我抢 ;-)

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/15 17:13:00
     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客82
    发贴心情 
    【一日一段- 0716】

    4.2 RDF Collections


    A limitation of the containers described in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers]Section 4.1[/URL] is that there is no way to close them, i.e., to say "these are all the members of the container". As noted in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers]Section 4.1[/URL], a container only says that certain identified resources are members; it does not say that other members do not exist. Also, while one graph may describe some of the members, there is no way to exclude the possibility that there is another graph somewhere that describes additional members. RDF provides support for describing groups containing only the specified members, in the form of RDF collections. An RDF collection is a group of things represented as a list structure in the RDF graph. This list structure is constructed using a predefined collection vocabulary consisting of the predefined type rdf:List, the predefined properties rdf:first and rdf:rest, and the predefined resource rdf:nil.
    在[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers]Section 4.1[/URL]中描述的容器的一个缺点是没有办法封闭它,即没有办法说这些是容器的所有成员。一个容器只说一些有标识的资源是它的成员,无法说没有其他的成员了。而且,如果有一个图描述它的一些成员,我们没法排除在其他地方有图也描述这个容器的其它成员的可能。RDF提供了对描述限定成员的组的支持,即RDF集合(collection)。一个RDF集合是用列表结构表示的一组事物,这个列表结构是用一些预定义的集合词汇表示的。RDF的集合词汇包括属性rdf:first 和rdf:rest,和资源rdf:nil.

    To illustrate this, the sentence "The students in course 6.001 are Amy, Mohamed, and Johann" could be represented using the graph shown in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL]:
    为了展示这个,句子“上课程6.001的学生有:Amy, Mohamed, 和Johann”可以用[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL]所示的图表示:


    Figure 16: 一个RDF集合(列表结构)


    In this graph, each member of the collection, such as s:Amy, is the object of an rdf:first property whose subject is a resource (a blank node in this example) that represents a list. This list resource is linked to the rest of the list by an rdf:rest property. The end of the list is indicated by the rdf:rest property having as its object the resource rdf:nil (the resource rdf:nil represents the empty list, and is defined as being of type rdf:List). This structure will be familiar to those who know the Lisp programming language. As in Lisp, the rdf:first and rdf:rest properties allow applications to traverse the structure. Each of the blank nodes forming this list structure is implicitly of type rdf:List (that is, each of these nodes implicitly has an rdf:type property whose value is the predefined type rdf:List), although this is not explicitly shown in the graph. The RDF Schema language [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-vocabulary][RDF-VOCABULARY[/URL]] defines the properties rdf:first and rdf:rest as having subjects of type rdf:List, so the information about these nodes being lists can generally be inferred, rather than the corresponding rdf:type triples being written out all the time.
    在这个图中,集合中的每个成员,如s:Amy,是属性rdf:first的客体,这个属性的主体是表示一个列表的资源(这个例子中是一个匿名节点)。这个列表通过属性rdf:rest链到列表的剩下的元素,列表的结束用一个值为rdf:nil 的属性rdf:rest表示(rdf:nil表示一个空列表,它的类型是rdf:List)。这种结构和Lisp语言很像,像Lisp一样,属性rdf:first 和rdf:rest允许程序遍历这个结构。列表结构中的每个匿名节点的类型都是rdf:List,尽管这没有在图中显示出来。RDF Schema语言[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-vocabulary][RDF-VOCABULARY[/URL]]定义了属性rdf:first 和rdf:rest的主体的类型是rdf:List,因此,这些匿名节点的类型信息可以推导出来,而不用每次都写出来。

    RDF/XML provides a special notation to make it easy to describe collections using graphs of this form. In RDF/XML, a collection can be described by a property element that has the attribute rdf:parseType="Collection", and that contains a group of nested elements representing the members of the collection. RDF/XML provides the rdf:parseType attribute to indicate that the contents of an element are to be interpreted in a special way. In this case, the rdf:parseType="Collection" attribute indicates that the enclosed elements are to be used to create the corresponding list structure in the RDF graph (other values of the rdf:parseType attribute will be described in later sections of the Primer).
    RDF/XML提供了一种使描述集合更为简单的方式。在RDF/XML中,一个集合可以用一个代表属性的元素节点表示,且这个元素节点有个属性节点是rdf:parseType="Collection",这表示元素节点下的内容要以一种特殊的方式解释。在这里,rdf:parseType="Collection"表示包含的元素要用来创建RDF图中。应的列表结构。

    To illustrate how rdf:parseType="Collection" works, the RDF/XML from [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example17]Example 17[/URL] would result in the RDF graph shown in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL]:
    为了展示rdf:parseType="Collection"是怎么工作的,[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example17]Example 17[/URL] 中的RDF/XML写法对应的图如 [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL]说示:

    Example 17: RDF/XML for a Collection of Students


    <?xml version="1.0"?>

    <rdf:RDF xmlns:rdf="[URL=http://www.w3.org/1999/02/22-rdf-syntax-ns#]http://www.w3.org/1999/02/22-rdf-syntax-ns#[/URL]"


             xmlns:s="[URL=http://example.org/students/vocab#]http://example.org/students/vocab#[/URL]">


       <rdf:Description rdf:about="[URL=http://example.org/courses/6.001]http://example.org/courses/6.001[/URL]">
          <s:students rdf:parseType="Collection">
                <rdf:Description rdf:about="[URL=http://example.org/students/Amy]http://example.org/students/Amy[/URL]"/>
                <rdf:Description rdf:about="[URL=http://example.org/students/Mohamed]http://example.org/students/Mohamed[/URL]"/>
                <rdf:Description rdf:about="[URL=http://example.org/students/Johann]http://example.org/students/Johann[/URL]"/>
          </s:students>
       </rdf:Description>

    </rdf:RDF>


    The use of rdf:parseType="Collection" in RDF/XML always defines a list structure like the one shown in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL], i.e., a fixed finite list of items with a given length and terminated by rdf:nil, and which uses "new" blank nodes that are unique to the list structure itself. However, RDF does not enforce this particular way of using the RDF collection vocabulary, and so it is possible to use this vocabulary in other ways, some of which may not describe lists or closed collections. To see why, note that the graph shown in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL] could also be written in RDF/XML by writing out the same triples "in longhand" (without using rdf:parseType="Collection") using the collection vocabulary, as in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example18]Example 18[/URL]:
    在RDF/XML 中用rdf:parseType="Collection" 常定义了一个如 [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]Figure 16[/URL]所示的列表结构:一个固定有限长度的列表,它用rdf:nil表示列表的结束,还用了一些相对于列表唯一的匿名节点。然后,RDF并没有强制集合词汇只能用于这种方式,因此也可以用于其他方式。有些方式可能没有描述列表或者说封闭的集合。为了知道原因,注意到[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16]http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#figure16[/URL] Figure 16]所示的图也可以用集合词汇的普通格式(不用rdf:parseType="Collection")写,如[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example18]Example 18[/URL]所示:

    Example 18: RDF/XML for a Collection of Students in "Longhand"


    <?xml version="1.0"?>

    <rdf:RDF xmlns:rdf="[URL=http://www.w3.org/1999/02/22-rdf-syntax-ns#]http://www.w3.org/1999/02/22-rdf-syntax-ns#[/URL]"

             xmlns:s="[URL=http://example.org/students/vocab#]http://example.org/students/vocab#[/URL]">

    <rdf:Description rdf:about="[URL=http://example.org/courses/6.001]http://example.org/courses/6.001[/URL]">


       <s:students rdf:nodeID="sch1"/>

    </rdf:Description>


    <rdf:Description rdf:nodeID="sch1">


       <rdf:first rdf:resource="[URL=http://example.org/students/Amy]http://example.org/students/Amy[/URL]"/>
       <rdf:rest rdf:nodeID="sch2"/>

    </rdf:Description>


    <rdf:Description rdf:nodeID="sch2">


       <rdf:first rdf:resource="[URL=http://example.org/students/Mohamed]http://example.org/students/Mohamed[/URL]"/>
       <rdf:rest rdf:nodeID="sch3"/>

    </rdf:Description>


    <rdf:Description rdf:nodeID="sch3">


       <rdf:first rdf:resource="[URL=http://example.org/students/Johann]http://example.org/students/Johann[/URL]"/>
       <rdf:rest rdf:resource="[URL=http://www.w3.org/1999/02/22-rdf-syntax-ns#nil]http://www.w3.org/1999/02/22-rdf-syntax-ns#nil[/URL]"/>

    </rdf:Description>

    </rdf:RDF>


    As noted in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-semantics][RDF-SEMANTICS[/URL]] (and as was the case for the container vocabulary described in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers]Section 4.1[/URL]), RDF imposes no "well-formedness" conditions on the use of the collection vocabulary so, when writing triples in longhand, it is possible to define RDF graphs with structures other than the well-structured graphs that would be automatically generated by using rdf:parseType="Collection". For example, it is not illegal to assert that a given node has two distinct values of the rdf:first property, to create structures that have forked or non-list tails, or to simply omit part of the description of a collection. Also, graphs defined by using the collection vocabulary in longhand could use URIrefs to identify the components of the list instead of blank nodes unique to the list structure. In this case, it would be possible to create triples in other graphs that effectively added elements to the collection, making it non-closed.
    注意到在 [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-semantics][RDF-SEMANTICS[/URL]] (和容器词汇相同的情况[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers]Section 4.1[/URL])中, RDF并没有对集合词汇施加格式正确性约束(well-formedness),因此,当用普通格式写时,有可能写出的列表结构并不像由用rdf:parseType=”collection”自动生成的那样正确,如一个节点的rdf:first属性有两个不同的值是合法的,或列表结构的最后的节点不是空列表,或简单地忽略了结合的某些部分。另外,用普通格式写的集合词汇定义的图可以用URIrefs标识列表中的部分节点,而不是在列表中是唯一的匿名节点,这样,有可能在别的图中有三元组为集合添加元素,而使之不封闭。

    As a result, RDF applications that require collections to be well-formed should be written to check that the collection vocabulary is being used appropriately, in order to be fully robust. In addition, languages such as [URL=http://www.w3.org/TR/owl-ref/]OWL[/URL] [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-owl][OWL[/URL]], which can define additional constraints on the structure of RDF graphs, can rule out some of these cases.
    结果是,RDF应用如果需要集合是格式正确的,为了应用的鲁棒性,就应该检查集合词汇时被正确的使用。另外,语言 [URL=http://www.w3.org/TR/owl-ref/]OWL[/URL] [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-owl][OWL[/URL]], 能够对RDF图的结构定义额外的限制,可以避免一些集合格式不正确的情况。

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 0:08:00
     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客83
    发贴心情 
    【一日一段 -0717】

    4.4 More on Structured Values: rdf:value


    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL] noted that the RDF model intrinsically supports only binary relations; that is, a statement specifies a relation between two resources. For example, the statement:
    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL]注意到RDF模型本质上只支持二元关系,也就是说,一个陈述表示了两个资源之间的关系。例如,陈述:

    exstaff:85740 exterms:manager exstaff:62345 .


    states that the relation exterms:manager holds between two employees (presumably one manages the other).
    说两个雇员之间有exterms: manager关系(一个管理另一个)。

    However, in some cases it is necessary to represent information involving higher arity relations (relations between more than two resources) in RDF. [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL] discussed one example of this, where the problem was to represent the relationship between John Smith and his address information, and the value of John's address was a structured value of his street, city, state, and postal code. Writing this as a relation shows that this address is a 5-ary relation of the form:
    然而,有些情况下有必要在RDF中表示多元关系(多于两个资源之间的关系)。[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL] 讨论了一个例子,这个例子的问题是要表示John Smith和他的地址信息,即一个由街道,城市,州,邮政编码组成的结构。可以看出这个地址信息是一个5元关系。

    address(exstaff:85740, "1501 Grant Avenue", "Bedford", "Massachusetts", "01730")


    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL] noted that this kind of structured information can be represented in RDF by considering the aggregate thing be described (here, the group of components representing John's address) as a separate resource, and then making separate statements about that new resource, as in the triples:
    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#structuredproperties]Section 2.3[/URL]注意到这种结构化的信息可以通过聚集一部分信息作为一个单独的资源(这里,John’s的地址信息),然后对这个新资源发表单独的陈述,如下面的三元组所示:

    exstaff:85740 exterms:address _:johnaddress .

    _:johnaddress exterms:street "1501 Grant Avenue" .

    _:johnaddress exterms:city "Bedford" .

    _:johnaddress exterms:state "Massachusetts" .

    _:johnaddress exterms:postalCode "01730" .

    (where _:johnaddress is the blank node identifier of the blank node representing John's address.)


    This is a general way to represent any n-ary relation in RDF: select one of the participants (John in this case) to serve as the subject of the original relation (address in this case), then specify an intermediate resource to represent the rest of the relation (either with or without assigning it a URI), then give that new resource properties representing the remaining components of the relation.
    (其中_:johnaddress是表示John’s的地址的匿名节点的标识)这是在RDF中表示N元关系的一般方法:选出关系中的一个元素(这里是John)作为关系(这里是address)的主体,指定一个中间的资源来表示关系中剩下的部分,然后把关系剩下部分都作为这个中间资源的属性。

    In the case of John's address, none of the individual parts of the structured value could be considered the "main" value of the exterms:address property; all of the parts contribute equally to the value. However, in some cases one of the parts of the structured value is often thought of as the "main" value, with the other parts of the relation providing additional contextual or other information that qualifies the main value. For instance, in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example9]Example 9[/URL] in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#newresources]Section 3.2[/URL], the weight of a particular tent was given as the decimal value 2.4 using a typed literal, i.e.,
    在John 的地址信息中,没有一个部分能够作为属性exterms:address的主值(main value),所有部分对值的贡献是相同的。然后,有时候,结构中的一部分可以作为结构的主值,其他部分提供上下文信息或其他对主值的修饰信息。例如,在[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#newresources]Section 3.2[/URL]的[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example9]Example 9[/URL] 中,一个帐篷的重量的值是小数2.4,也就是,

    exproduct:item10245 exterms:weight "2.4"^^xsd:decimal .

    In fact, a more complete description of the weight would have been 2.4 kilograms rather than just the decimal value 2.4. To state this, the value of the exterms:weight property would need to have two components, the typed literal for the decimal value and an indication of the unit of measure (kilograms). In this situation the decimal value could be considered the "main" value of the exterms:weight property, because frequently the value would be recorded simply as the typed literal (as in the triple above), relying on an understanding of the context to fill in the unstated units information.
    实际上,更为复杂的对重量的描述应该是2.4千克( kilograms),而不是仅仅小数2.4。为了表示这个,属性exterms:weight的值还需要2个部分:作为类型文字的数值和量度的单位(千克)。在这种情况下,数值可以看成属性exterms:weight的主值,因为一般这个值都是一个类型文字,而依赖山下文信息来填充这个值的单位。

    In the RDF model a qualified property value of this kind can be considered as simply another kind of structured value. To represent this, a separate resource could be used to represent the structured value as a whole (the weight, in this case), and to serve as the object of the original statement. That resource could then be given properties representing the individual parts of the structured value. In this case, there should be a property for the typed literal representing the decimal value, and a property for the unit. RDF provides a predefined rdf:value property to describe the main value (if there is one) of a structured value. So in this case, the typed literal could be given as the value of the rdf:value property, and the resource exunits:kilograms as the value of an exterms:units property (assuming the resource exunits:kilograms is defined as part of example.org's vocabulary). The resulting triples would be:
    在RDF模型中,这种类型的带有修饰的属性值可以看成一种简单的结构化值。为了表达这个,一个单独的资源可以用来表示结构化值,且作为原来陈述的客体。这个资源可以有属性表示结构值中的部分。在这里,应该有个属性表示数值,还一个属性表示单位。RDF提供了一个预定义的属性rdf:value来描述结构值中的主值。因此,这里的数值可以作为rdf:value的值,资源exunits:kilograms作为属性exterms:units的值(假设资源exunits:kilograms定义为example.org的词汇集的一部分)。结果,这些三元组为:

    exproduct:item10245 exterms:weight _:weight10245 .

    _:weight10245 rdf:value "2.4"^^xsd:decimal .

    _:weight10245 exterms:units exunits:kilograms .

    which can be expressed using the RDF/XML shown in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL]:
    这可以用RDF/XML表示,如[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL]所示:

    Example 21: RDF/XML using rdf:value


    <?xml version="1.0"?>

    <!DOCTYPE rdf:RDF [<!ENTITY xsd "[URL=http://www.w3.org/2001/XMLSchema#]http://www.w3.org/2001/XMLSchema#[/URL]">]>

    <rdf:RDF xmlns:rdf="[URL=http://www.w3.org/1999/02/22-rdf-syntax-ns#]http://www.w3.org/1999/02/22-rdf-syntax-ns#[/URL]"

                xmlns:exterms="[URL=http://www.example.org/terms/]http://www.example.org/terms/[/URL]">


      <rdf:Description rdf:about="[URL=http://www.example.com/2002/04/products#item10245]http://www.example.com/2002/04/products#item10245[/URL]">
         <exterms:weight rdf:parseType="Resource">
           <rdf:value rdf:datatype="&xsd;decimal">2.4</rdf:value>
           <exterms:units rdf:resource="[URL=http://www.example.org/units/kilograms]http://www.example.org/units/kilograms[/URL]"/>
         </exterms:weight>
      </rdf:Description>

    </rdf:RDF>


    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL] also illustrates a second use of the rdf:parseType attribute introduced in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections]Section 4.2[/URL], in this case, rdf:parseType="Resource". An rdf:parseType="Resource" attribute is used to indicate that the contents of an element are to be interpreted as the description of a new (blank node) resource, without actually having to write a nested rdf:Description element. In this case, the rdf:parseType="Resource" attribute used in the exterms:weight property element indicates that a blank node is to be created as the value of the exterms:weight property, and that the enclosed elements (rdf:value and exterms:units) describe properties of that blank node. Further details on rdf:parseType="Resource" are given in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-syntax][RDF-SYNTAX[/URL]].
    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL]也显示了对[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections]Section 4.2[/URL]介绍的属性rdf:parseType的用法,在这里,rdf:parseType="Resource"用以表示节点的内容同时被解释为一个新的匿名节点,而不用写一个嵌套的rdf:Description元素。rdf:parseType="Resource" 用在属性 exterms:weight 元素节点中表示创建了一个匿名节点作为属性的值,且包含的元素 (rdf:value 和 exterms:units) 描述了这个匿名节点的属性。关于rdf:parseType="Resource"更详细的信息在[RDF-SYNTAX].

    The same approach can be used to represent quantities using any units of measure, as well as values taken from different classification schemes or rating systems, by using the rdf:value property to give the main value, and using additional properties to identify the classification scheme or other information that further describes the value.
    相同的方法也可用于表示具有任何单位的数量,用rdf:value属性表示主值,用其他的属性表示关于数量的其他信息。

    There is no need to use rdf:value for these purposes (e.g., a user-defined property name, such as exterms:amount, could have been used instead of rdf:value in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL]), and RDF does not associate any special meaning with rdf:value. rdf:value is simply provided as a convenience for use in these commonly-occurring situations.
    但没有必要用rdf:value去取代用户自定义的属性,如[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example21]Example 21[/URL]中的属性exterms:amount, 因为RDF并没有给rdf:value特殊的解释。它只是作为表示这种情形的惯例。

    However, even though much existing data in databases and on the Web (and in later Primer examples) takes the form of simple values for properties such as weights, costs, etc., the principle that such simple values are often insufficient to adequately describe these values is an important one. In a global environment such as the Web, it is generally not safe to make the assumption that anyone accessing a property value will understand the units being used (or other contextually-dependent information that may be involved). For example, a U.S. site might give a weight value in pounds, but someone accessing that data from outside the U.S. might assume that weights are given in kilograms. The correct interpretation of data in the Web environment may require that additional information (such as units information) be explicitly recorded. This can be done in many ways, such as using rdf:value, building units into property names (e.g., exterms:weightInKg), defining specialized datatypes that include units information (e.g., extypes:kilograms), or adding additional user-defined properties to specify this information (e.g., exterms:unitOfWeight), either in descriptions of individual items or products, in descriptions of sets of data (e.g., all the data in a catalog or on a site), or in schemas (see [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#rdfschema]Section 5[/URL]).


    然而,尽管大部分数据库中和Web上的数据用简单的数值作为属性(如,重量,价格等)的值,这种简单的数值往往不足够描述这些值。在像Web这样的环境,一般来说,假设其他人访问属性的值的时候能知道它的单位(或其他上下文相关的信息)是不稳妥的。例如,一个美国的网站给中重量的单位是磅,但不是美国的人访问这个数据的时候常假设单位是公斤。对Web上数据的正确解释可能需要其他的信息,如单位信息。这有很多种方法:例如,用rdf:value,把单位信息放在属性名字种,如属性exterms:weightInKg包含了数据的单位信息。或者,加上用户自定义的的信息,如exterms:unitOfWeight, 在物品或产品实例的描述中,在一个数据集的描述中,或者在Schema中(参考[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#rdfschema]Section 5[/URL])

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 0:10:00
     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客84
    发贴心情 
    【一日一段 -0718】

    4.5 XML Literals


    Sometimes the value of a property needs to be a fragment of XML, or text that might contain XML markup. For example, a publisher might maintain RDF metadata that includes the titles of books and articles. While such titles are often just simple strings of characters, this is not always the case. For instance, the titles of books on mathematics may contain mathematical formulas that could be represented using MathML [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-mathml][MATHML[/URL]]. Titles might also include markup for other reasons, such as for Ruby annotations [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-ruby][RUBY[/URL]], or for bidirectional rendering or special glyph variants (see, e.g., [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-charmod][CHARMOD[/URL]]).
    有时候,属性的值可能是一个XML的片断,或包含XML标记的文本。例如,出版社可能要维护一些RDF数据,包括书和文章的标题。当然,这些标题可能是简单的字符串,但并不总是这样。例如,数学书的标题可能包含用MathML [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-mathml][MATHML[/URL]]表示的数学公式。标题还可能因为其他原因包含标记,如 Ruby标注 [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-ruby][RUBY[/URL]], 或者双相的显示特殊的浮雕型变量。 ([URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-charmod][CHARMOD[/URL]])

    RDF/XML provides a special notation to make it easy to write literals of this kind. This is done using a third value of the rdf:parseType attribute. Giving an element the attribute rdf:parseType="Literal" indicates that the contents of the element are to be interpreted as an XML fragment. [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example22]Example 22[/URL] illustrates the use of rdf:parseType="Literal":
    RDF/XML提供了一个特殊的符号,使书写这种文字变得简单。即通过属性rdf:parseType第三个值,如果一个元素节点的有属性节点rdf:parseType="Literal",表明这个元素节点的内容应该被解释为一个XML片断。[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example22]Example 22[/URL] 演示了这种用法。

    Example 22: RDF/XML for an XML Literal


    <?xml version="1.0"?>

    <rdf:RDF xmlns:rdf="[URL=http://www.w3.org/1999/02/22-rdf-syntax-ns#]http://www.w3.org/1999/02/22-rdf-syntax-ns#[/URL]"


                xmlns:dc="[URL=http://purl.org/dc/elements/1.1/]http://purl.org/dc/elements/1.1/[/URL]"
                xml:base="[URL=http://www.example.com/books]http://www.example.com/books[/URL]">


      <rdf:Description rdf:ID="book12345">
         <dc:title rdf:parseType="Literal">
           <span xml:lang="en">
             The <em>&lt;br /&gt;</em> Element Considered Harmful.
           </span>
         </dc:title>
      </rdf:Description>

    </rdf:RDF>


    The RDF/XML in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example22]Example 22[/URL] describes a graph containing a single triple with subject ex:book12345, and predicate dc:title. The rdf:parseType="Literal" attribute in the RDF/XML indicates that all the XML within the <dc:title> element is an XML fragment that is the value of the dc:title property. In the graph, this value is a typed literal, whose datatype, rdf:XMLLiteral, is defined in [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-concepts][RDF-CONCEPTS[/URL]] specifically to represent fragments of XML (including character sequences that may or may not include XML markup). The XML fragment is canonicalized according to the XML Exclusive Canonicalization recommendation [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-xml-xc14n][XML-XC14N[/URL]]. This causes declarations of used namespaces to be added to the fragment, the uniform escaping or unescaping of characters, the expansion of empty-element tags, and other transformations. (For these reasons, and the fact that the triples notation itself requires further escaping, the actual typed literal is not shown here. RDF/XML provides the rdf:parseType="Literal" attribute so that RDF users will not have to deal directly with these transformations. Those interested in the details should consult [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-concepts][RDF-CONCEPTS[/URL]] and [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-syntax][RDF-SYNTAX[/URL]].) Contextual attributes, such as xml:lang and xml:base are not inherited from the RDF/XML document, and, if required, must, as shown in the example, be explicitly specified in the XML fragment.
    [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example22]Example 22[/URL] 中的RDF/XML 描述了一个包含了一个三元组的图,这个三元组的主体是ex:book12345, 谓词是dc:title. 属性节点 rdf:parseType="Literal" 表示元素节点 <dc:title> 下的内容是一个XML片断,即作为属性dc:title的值。在这个图中,值是类型为rdf:XMLLiteral 的类型文字。[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-concepts][RDF-CONCEPTS[/URL]] 特意定义rdf:XMLLiteral作为表示XML片断的数据类型。这些XML片断都是根据XML Exclusive Canonicalization recommendation [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-xml-xc14n][XML-XC14N[/URL]]规范化了的,这导致了一些转换,如为XML片断加上已用的名字空间声明,统一的字符转义或去转义,空元素的扩展。(因为这些原因以及三元组的标注本身需要一些转义符,这里不显示真正的类型文字。RDF/XML 提供了属性 rdf:parseType="Literal" 使RDF用户不用进行这些转换。详细信息请参考[URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-concepts][RDF-CONCEPTS[/URL]] 和 [URL=http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-rdf-syntax][RDF-SYNTAX[/URL]].) 一些上下文属性,如xml:lang 和 xml:base 并不会从RDF/XML文档中继承,如果需要的化,如上例所示,必须在XML片断中给出。

    This example illustrates that care must be taken in designing RDF data. It might appear at first glance that titles are simple strings best represented as plain literals, and only later might it be discovered that some titles contain markup. In cases where the value of a property may sometimes contain markup and sometimes not, either rdf:parseType="Literal" should be used throughout, or software must handle both plain literals and literals of type rdf:XMLLiteral as values of the property.
    这个例子表明了书写RDF数据是要谨慎。乍看,标题的值是用平凡文字表示的简单字符串,后来又发现会包含XML标记。如果一个属性的值有时包含XML标记,有时有不包含,应该都用rdf:parseType="Literal",或者软件应该能处理属性的值可能是平凡文字和rdf:XMLLiteral类型的文字的情况。

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 0:11:00
     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客85
    发贴心情 
    好了,休息三天!!
    不翻了,累死了。

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 0:13:00
     
     forwar 帅哥哟,离线,有人找我吗?水瓶座1982-1-28
      
      
      威望:4
      等级:大三暑假(TOFEL考了650分!)
      文章:171
      积分:869
      门派:XML.ORG.CN
      注册:2004/3/2

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给forwar发送一个短消息 把forwar加入好友 查看forwar的个人资料 搜索forwar在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 引用回复这个贴子 回复这个贴子 查看forwar的博客86
    发贴心情 偶也来一日一段
    2.2 The RDF Model
    Groups of statements are represented by corresponding groups of nodes and arcs.
    陈述中的组被相应的节点和弧的组所描述。
    Groups翻译为组行不行?
    -------------------------------
    So, to reflect the additional English statements
    http://www.example.org/index.html has a creation-date whose value is August 16, 1999
    http://www.example.org/index.html has a language whose value is English
    in the RDF graph, the graph shown in Figure 3 could be used (using suitable URIrefs to name the properties "creation-date" and "language"):
    所以,英文陈述其他的内容可以如图3所示的那样反映出来:

    Figure 3: Several Statements About the Same Resource
    图3:相同资源中的其他个别的陈述:


    Figure 3 illustrates that objects in RDF statements may be either URIrefs, or constant values (called literals) represented by character strings, in order to represent certain kinds of property values.

    (In the case of the predicate http://purl.org/dc/elements/1.1/language the literal is an international standard two-letter code for English.)

    Literals may not be used as subjects or predicates in RDF statements. In drawing RDF graphs, nodes that are URIrefs are shown as ellipses, while nodes that are literals are shown as boxes.

    (The simple character string literals used in these examples are called plain literals, to distinguish them from the typed literals to be introduced in Section 2.4. The various kinds of literals that can be used in RDF statements are defined in [RDF-CONCEPTS]. Both plain and typed literals can contain Unicode [UNICODE] characters, allowing information from many languages to be directly represented.)
    图3说明了RDF陈述中的客体可以是URIrefs,也可以是常量值(称作文字),即用于表示某种属性值的字符串。

    (比如在以“http://purl.org/dc/elements/1.1/language”做谓词的例子,文字(literal)就是英文的国际标准--双字母码。)
    在RDF的陈述中,文字(literal)可能不被用作主体或者谓词。在RDF图中,节点为URIrefs的都用椭圆来表示,而节点为文字(literal)的则用方框来表示(这个例子中的简单字符串文字叫做简单文字,它与将会在2.4节做介绍的类型文字(typed literals)是不同的。在[RDF-CONCEPTS]中详细说明了各种不同的可以用在RDF陈述中的文字。简单文字和类型文字都能容许采用双字节编码[UNICODE]的字符,即允许用多种语言直接描述的信息。)

    Sometimes it is not convenient to draw graphs when discussing them, so an alternative way of writing down the statements, called triples, is also used. In the triples notation, each statement in the graph is written as a simple triple of subject, predicate, and object, in that order. For example, the three statements shown in Figure 3 would be written in the triples notation as:
    有时当讨论它们的时候画图不是很方便,因此一个被称作三元组表达式(以下简称三元组)的折中记法也会被用到。在三元组表达式符号中,在图中的每个陈述都可以写成主体,谓词,客体三个为一组,并且顺序不能颠倒。如图3所表示的陈述用三元组表示法来记就是:
    <http://www.example.org/index.html>; <http://purl.org/dc/elements/1.1/creator>; <http://www.example.org/staffid/85740>; .

    <http://www.example.org/index.html>; <http://www.example.org/terms/creation-date>; "August 16, 1999" .

    <http://www.example.org/index.html>; <http://purl.org/dc/elements/1.1/language>; "en" .

    Each triple corresponds to a single arc in the graph, complete with the arc's beginning and ending nodes (the subject and object of the statement). Unlike the drawn graph (but like the original statements), the triples notation requires that a node be separately identified for each statement it appears in. So, for example, http://www.example.org/index.html appears three times (once in each triple) in the triples representation of the graph, but only once in the drawn graph. However, the triples represent exactly the same information as the drawn graph, and this is a key point: what is fundamental to RDF is the graph model of the statements. The notation used to represent or depict the graph is secondary.
    每一个三元组均对应图中相应的一条弧,以及这个弧的起始节点和终止节点(即是陈述中的主体和谓词)。三元组要求一个为在每个它出现过的陈述而分别定义的节点,就这点而言,不像图形表达法那样(倒像是原先的陈述那样)。因此,譬如, “http://www.example.org/index.html”在三元组表示法中共出现了三次(在每个三元组表达式中均出现过一次),而在图形表示法中只出现了一次。但是,三元组精确的描述了图形中所表达的信息,并且揭示了一个要点:RDF的基本原理就是陈述的模型图,而用于表达或是描述这个图形的表达方式则是次要的。
    ---------------------------------
    triples notation 翻成三元组表示法行不行?

    and this is a key point: what is fundamental to RDF is the graph model of the statements. The notation used to represent or depict the graph is secondary.
    翻成:RDF的基本原理就是陈述的模型图,而用于表达或是描述这个图形的表达方式则是次要的。行不行?

    ---------------------------------
    orangebench 猛男啊!

    ----------------------------------------------
    >>>>>>>>    ^o^   <<<<<<<<

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 0:25:00
     
     yuji1998 帅哥哟,离线,有人找我吗?魔羯座1981-12-22
      
      
      威望:5
      头衔:蓝色先锋
      等级:大二(研究C++)
      文章:212
      积分:1059
      门派:XML.ORG.CN
      注册:2004/4/10

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给yuji1998发送一个短消息 把yuji1998加入好友 查看yuji1998的个人资料 搜索yuji1998在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问yuji1998的主页 引用回复这个贴子 回复这个贴子 查看yuji1998的博客87
    发贴心情 我考,我该翻译哪一段的内容阿。
    还剩哪几段每人要阿,我无所谓的,哪里都可以

    ----------------------------------------------
    私人网站:蓝尚WEB商务平台http://www.lanshang.com     建站黄页:http://www.lanshang.com/link.asp WEB技术文库:http://www.lanshang.com/wenzhang/ 
    电子书籍: http://www.lanshang.com/ebook/  技术交流:http://www.lanshang.com/bbs/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 1:32:00
     
     forwar 帅哥哟,离线,有人找我吗?水瓶座1982-1-28
      
      
      威望:4
      等级:大三暑假(TOFEL考了650分!)
      文章:171
      积分:869
      门派:XML.ORG.CN
      注册:2004/3/2

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给forwar发送一个短消息 把forwar加入好友 查看forwar的个人资料 搜索forwar在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 引用回复这个贴子 回复这个贴子 查看forwar的博客88
    发贴心情 
    The full triples notation requires that URI references be written out completely, in angle brackets, which, as the example above illustrates, can result in very long lines on a page. For convenience, the Primer uses a shorthand way of writing triples (the same shorthand is also used in other RDF specifications).This shorthand substitutes an XML qualified name (or QName) without angle brackets as an abbreviation for a full URI reference (QNames are discussed further in Appendix B). A QName contains a prefix that has been assigned to a namespace URI, followed by a colon, and then a local name. The full URIref is formed from the QName by appending the local name to the namespace URI assigned to the prefix. So, for example, if the QName prefix foo is assigned to the namespace URI
    http://example.org/somewhere/, then the QName foo:bar is shorthand for the URIref
    http://example.org/somewhere/bar. Primer examples will also use several "well-known" QName prefixes
    (without explicitly specifying them each time), defined as follows:
    一个完整的三元组表达式要求写出全部的URI地址,正如上面例子那样,所以导致了在一页中有很多长句,方便起见,本书用一种简写法(在其他的RDF规范里用的也是这种)来记述三元组。This shorthand substitutes an XML qualified name (or QName) without angle brackets as an abbreviation for a full URI reference (QNames are discussed further in Appendix B).
    ------------------------------------
    这句话不会翻.  : ( 谁来翻一下...  

    一个QName包括一个被赋值为命名空间URI的前缀,其后是一个冒号,然后是个地址名称。完整的URIref是由QName通过将地址名称添加到已经赋值给前缀的命名空间URI的方式组成的。因此,例如,如果将命名空间URI“http://example.org/somewhere/”赋值给QName前缀foo,那么QName “foo:bar”就是URIref“http://example.org/somewhere/bar”的缩写(有个例子什么都明白了,^O^)。在本书的例子中也会用一些“公认的”QName前缀(这些前缀无需说明就可使用),定义如下:
    prefix rdf:, namespace URI: http://www.w3.org/1999/02/22-rdf-syntax-ns#
    prefix rdfs:, namespace URI: http://www.w3.org/2000/01/rdf-schema#
    prefix dc:, namespace URI: http://purl.org/dc/elements/1.1/
    prefix owl:, namespace URI: http://www.w3.org/2002/07/owl#
    prefix ex:, namespace URI: http://www.example.org/ (or http://www.example.com/)
    prefix xsd:, namespace URI: http://www.w3.org/2001/XMLSchema#

    Obvious variations on the "example" prefix ex: will also be used as needed in the examples, for instance,
    显然,“example”的前缀 “ex:”的变形在需要时也会用在示例中,譬如:

    prefix exterms:, namespace URI: http://www.example.org/terms/ (for terms used by an example

    organization),
    prefix exstaff:, namespace URI: http://www.example.org/staffid/ (for the example organization's staff

    identifiers),
    prefix ex2:, namespace URI: http://www.domain2.example.org/ (for a second example organization), and so on.

    Using this new shorthand, the previous set of triples can be written as:
    用这种简写法,先前的三元组可以写成:
    ex:index.html dc:creator exstaff:85740 .
    ex:index.html exterms:creation-date "August 16, 1999" .
    ex:index.html dc:language "en" .

    -----------------------------------
    TO:yuji1998   没关系的,你随便选一段然后在这发个帖说明一下,省的别人和你翻重了(我每天都担心这件事会发生...)就行了.
    -----------------------------------
    偶可是第88楼啊~~~爽啊~~~

    [此贴子已经被作者于2004-7-16 2:44:27编辑过]

    ----------------------------------------------
    >>>>>>>>    ^o^   <<<<<<<<

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 2:09:00
     
     orangebench 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      等级:研一(参加了一年一度的XML大会)(版主)
      文章:681
      积分:4761
      门派:W3CHINA.ORG
      注册:2004/5/28

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给orangebench发送一个短消息 把orangebench加入好友 查看orangebench的个人资料 搜索orangebench在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问orangebench的主页 引用回复这个贴子 回复这个贴子 查看orangebench的博客89
    发贴心情 
    看一下这个:http://wiki.w3china.org/wiki/index.php/RDF入门_推荐标准
    就知道哪些还没有翻译了。

    第6节还没开始,现在基本的安排是:
    第2节:forwar
    第3节:admin
    第4节:orangebench
    第5节:trevol (还有5。1和5。2。 5.3-5.5已经翻译完毕)

    你可以找第2,第3节的后面的小节 或者第6节翻译。;-)

    以下是引用yuji1998在2004-7-16 1:32:09的发言:
    还剩哪几段每人要阿,我无所谓的,哪里都可以

    ----------------------------------------------
    Semantic Web is a dream; Semantic Web technology is 
    the reality.
    Weblog: http://blog.w3china.org/~orangebench/

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 8:58:00
     
     cwzb 帅哥哟,离线,有人找我吗?双鱼座1981-3-10
      
      
      威望:4
      头衔:没有耳多
      等级:(版主)
      文章:253
      积分:1753
      门派:XML.ORG.CN
      注册:2004/1/15

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给cwzb发送一个短消息 把cwzb加入好友 查看cwzb的个人资料 搜索cwzb在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问cwzb的主页 引用回复这个贴子 回复这个贴子 查看cwzb的博客90
    发贴心情 
    可惜我E文不好

    ----------------------------------------------
    无能不多智不要紧。
    关键是肯学,感兴趣!

    送给我自己的话!

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/7/16 17:42:00
     
     GoogleAdSense双鱼座1981-3-10
      
      
      等级:大一新生
      文章:1
      积分:50
      门派:无门无派
      院校:未填写
      注册:2007-01-01
    给Google AdSense发送一个短消息 把Google AdSense加入好友 查看Google AdSense的个人资料 搜索Google AdSense在『 Semantic Web(语义Web)/描述逻辑/本体 』的所有贴子 访问Google AdSense的主页 引用回复这个贴子 回复这个贴子 查看Google AdSense的博客广告
    2024/5/21 9:37:05

    本主题贴数262,分页:[1] ... [6] [7] [8] [9] [10] [11] [12]... [27]

    管理选项修改tag | 锁定 | 解锁 | 提升 | 删除 | 移动 | 固顶 | 总固顶 | 奖励 | 惩罚 | 发布公告
    W3C Contributing Supporter! W 3 C h i n a ( since 2003 ) 旗 下 站 点
    苏ICP备05006046号《全国人大常委会关于维护互联网安全的决定》《计算机信息网络国际联网安全保护管理办法》
    156.250ms