以文本方式查看主题 - 中文XML论坛 - 专业的XML技术讨论区 (http://bbs.xml.org.cn/index.asp) -- 『 Semantic Web(语义Web)/描述逻辑/本体 』 (http://bbs.xml.org.cn/list.asp?boardid=2) ---- 关于启动翻译 W3C RDF Primer 的倡 议(完成初审,欢迎大家Review) (http://bbs.xml.org.cn/dispbbs.asp?boardid=2&rootid=&id=8689) |
-- 作者:admin -- 发布时间:7/8/2004 2:20:00 PM -- 关于启动翻译 W3C RDF Primer 的倡 议(完成初审,欢迎大家Review) 已提交给W3C, 译文链接为 http://zh.transwiki.org/cn/rdfprimer.htm[/color] W3C RDF Primer Recommendation是一个重要的RDF规范。该规范是W3C RDF系列规范中内容相对简单的一个文 档,适于RDF入门者。 鉴于目前还没有系统学习RDF的中文文档,相信这个规范的汉化,将使得更多的朋友可以深入了解RDF。 因此,翻译RDF Primer的意义非常重大,对SW技术面向非科研人员的推广等将起到积极的作用,希望更多有能力参加翻译的朋友加入我们的小组,共同完成该文档的翻译 。 本次翻译行动将采用Wiki协作的方式。 使用Wiki的好处是,对于那些很想为翻译计划贡献力量、而时间精力有限的朋友,可以量力而行,根据自己的 情况,选择翻译其中一段文字、或修改他人的翻译,而不影响整个翻译的协作过程。 本次翻译行动的Leader是:trevol (拥有翻译过程中异议的最终裁决权。比如关于同一段文字的不同译法的最 终决定。) 开始时间为7月中旬,结束时间为8月底。翻译完成后,翻译小组将召集有相关研究背景的人士进行为期15天的 Review。如果没有异议,翻译文档将被提交给W3C。 本次翻译行动在Wiki上的链接为:http://wiki.w3china.org/wiki/index.php/RDF入门%20推荐标准 翻译过程中产生的讨论,请回复本贴。 然后在回复本帖,并注明自己可以贡献的时间,以及能否翻译的部分。谢谢! RDF primer 总共有7个主要的章节 ,共139页。 目前的分配情况如下(保持更新): 6.1 都柏林核心元数据计划 5页 --(初稿:Ontoweb,初审: orangebench ) 第七章 RDF规范相关文档 - 2页 (orangebench,已完成初稿) 致谢: trevol
[此贴子已经被作者于2004-10-3 19:24:22编辑过]
|
-- 作者:forwar -- 发布时间:7/8/2004 11:54:00 PM -- "http://wiki.w3china.org"我已经访问了,并注册了用户名:forwar,现在已经基本掌握了Wiki的使用方法,我十分想加入这次W3C RDF Primer 的翻译活动,虽然我水平不高,但我时间和精力很充裕(我现在在放暑假),每天保证可以至少有2-3个小时时间可以用在翻译上;至于能翻译的部分,我感觉都差不多--因为都有难度,如果我可以参加,那我可以接受分配下来的任务。
[此贴子已经被作者于2004-7-9 0:24:32编辑过]
|
-- 作者:admin -- 发布时间:7/9/2004 1:27:00 AM -- 欢迎欢迎。。 |
-- 作者:trevol -- 发布时间:7/9/2004 8:37:00 AM -- 欢迎forwar, 留个 MAIL 或者MSN吧。。。呵呵 |
-- 作者:orangebench -- 发布时间:7/9/2004 9:06:00 AM -- 我也会参加部分翻译,时间在7月底,具体部分无所谓,请trevol分配吧。 |
-- 作者:trevol -- 发布时间:7/9/2004 10:17:00 AM -- 首先非常感谢大家热心参与。我们共同努力,争取把这件事情做好。 RDF primer 总共有7个主要的章节 ,共139页。 第一章 简介 -4页 大家注册后,就可以通过wiki开始协同翻译。只要是还没有人翻译的部分,您都可以翻译,而且翻译过程中遇到的任何问题,都可以到这里来讨论。 再次感谢大家的参与! |
-- 作者:admin -- 发布时间:7/9/2004 11:00:00 AM -- 关于翻译中遇到的相关术语,请参见 http://wiki.w3china.org/wiki/index.php/Terminology 如遇到未包含在内的术语,可以来这l讨论,或直接在 http://wiki.w3china.org/wiki/index.php/Terminology 里添加(遇到问题,再来这里讨论) |
-- 作者:forwar -- 发布时间:7/9/2004 1:38:00 PM -- 谢谢admin,trevol!我的EMAIL:forwar@w3china.org. MSN:forwarr@hotmail.com,欢迎和我联系!谢谢! |
-- 作者:forwar -- 发布时间:7/9/2004 9:17:00 PM -- 摘要里有这两句: It introduces the basic concepts of RDF and describes its XML syntax. 它介绍了RDF的基本概念并且描述了它的可扩展标记语言(eXtensible Markup Language)的语法。 句中的XML syntax译为可扩展标记语言(eXtensible Markup Language)的语法,不知行不行。 It describes how to define RDF vocabularies using the RDF Vocabulary Description Language, 它描述了该如何去定义那些使用了RDF词汇描述术语的RDF词汇, the RDF Vocabulary Description 译为RDF词汇描述术语,不知行不行,这些http://wiki.w3china.org/wiki/index.php/Terminology里没有,所以先试着翻了下,请大家看看。
|
-- 作者:orangebench -- 发布时间:7/9/2004 9:48:00 PM -- 不要完全直译,要在理解的基础上,有一定的意译。
It describes how to define RDF vocabularies using the RDF Vocabulary Description Language, 可译为:它描述了该如何用RDF词汇描述语言去定义RDF词汇集, RDF vocabularies :RDF词汇集 |
-- 作者:orangebench -- 发布时间:7/9/2004 9:51:00 PM -- 可以参考 宋老师的新书: 《语义网 简明教程》 还有 trevol的博士论文 |
-- 作者:forwar -- 发布时间:7/9/2004 10:18:00 PM -- 谢谢指点,因为我先前没有类似的经验,所以比较拘谨,不太敢用意译,怕词不达意,甚至译错了。现在好多了。谢谢指教!! |
-- 作者:forwar -- 发布时间:7/9/2004 10:22:00 PM --
偶知道,你们都是猛男...感觉好有压力... -------------------------------------------------------------------------------------- 还有: ...... 这个部分在它出版时可以描述出这份文献的地位。 Other documents may supersede this document. 其他资料可以替代这份文献。 [此贴子已经被作者于2004-7-9 23:55:06编辑过]
|
-- 作者:admin -- 发布时间:7/9/2004 11:53:00 PM -- 个人觉得如果原文没有把XML展开为Extensible Markup Language,译文中也不需要把。 |
-- 作者:forwar -- 发布时间:7/9/2004 11:57:00 PM --
那我画蛇添脚了,呵呵,见笑了...我马上就改过来。 目录都是术语,汗~~偶搞不定...偶休息下,玩会儿星际...
|
-- 作者:admin -- 发布时间:7/10/2004 1:10:00 AM --
刚才又翻译了一段。。睡觉了。。
|
-- 作者:forwar -- 发布时间:7/10/2004 1:14:00 PM -- 在2. Making Statements About Resources中有这两句话:感觉翻的不顺手,情大家修改一下: 1.Parts of this statement are emphasized to illustrate that, in order to describe the properties of something, there need to be ways to name, or identify, a number of things: 2.the thing the statement says is the value of this property (who the creator is), for the thing the statement describes 声明所描述的事物(如这个网页的作者是谁)是这事物属性的值。
|
-- 作者:orangebench -- 发布时间:7/10/2004 2:30:00 PM -- statement的标准翻译是什么? 陈述,语句,声明? 1.Parts of this statement are emphasized to illustrate that, in order to describe the properties of something, there need to be ways to name, or identify, a number of things: 这个声明的各个部分被强调了是想说明: 为了描述某些事物的特性,需要某种方法去命名或者是识别事物,使其不致于混淆。 这样行吗?没有去看上下文。
|
-- 作者:orangebench -- 发布时间:7/10/2004 2:44:00 PM -- 很感谢你的辛勤工作,我们会尽力帮助你的。 Other documents may supersede this document.
|
-- 作者:forwar -- 发布时间:7/10/2004 4:37:00 PM -- 这个声明的各个部分被强调了是想说明: 为了描述某些事物的特性,需要某种方法去命名或者是识别事物,使其不致于混淆。这样翻好多了。我马上就去改过来。谢谢鼓励!谢谢!! --------------------------------------------------------------------------------------------------------------
[此贴子已经被作者于2004-7-10 20:35:00编辑过]
|
-- 作者:yuji1998 -- 发布时间:7/10/2004 5:59:00 PM -- 我也参加,大家一起来。 |
-- 作者:hyandlsz -- 发布时间:7/10/2004 7:57:00 PM -- 好! |
-- 作者:forwar -- 发布时间:7/10/2004 9:43:00 PM -- 好的,人多力量大! ------------------------------------------------------------------------------------------------------------------ RDF is based on the idea that the things being described have properties which have values, and that resources can be described by making statements, similar to those above, that specify those properties and values. RDF uses a particular terminology for talking about the various parts of statements. 被描述的事物有很多有值的属性,而我们通过发表那些可详细说明事物具有的属性及属性的值的声明(就像上面的例子)来描述那些资源,RDF正是基于这样的思想才产生的。RDF有一套独特的术语来表达声明的各个部分。 Specifically, the part that identifies the thing the statement is about (the Web page in this example) is called the subject. The part that identifies the property or characteristic of the subject that the statement specifies (creator, creation-date, or language in these examples) is called the predicate, and the part that identifies the value of that property is called the object. 确切地说,关于事物(譬如上例中的网页)的声明中用于识别事物的那部分就叫做主语,而用于区分声明对象主语的各个不同属性(譬如:作者,创建日期,语种等等)的那部分就叫做谓语,声明中用于区分各个属性的值的那部分叫做宾语。 subject,predicate,object翻成主谓宾语行不行?
|
-- 作者:admin -- 发布时间:7/10/2004 11:46:00 PM -- -------------------------------------------------------------------------------------------------------------- ps:我在2.1 Basic Concepts里把statement全部译成声明。 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` statement也可以译为 "陈述"。 最终怎么翻译,还需在讨论讨论。。 |
-- 作者:admin -- 发布时间:7/11/2004 12:11:00 AM --
|
-- 作者:admin -- 发布时间:7/11/2004 12:24:00 AM -- 对于Class, Object, Property,以及forwar提到的subject, predict,object等 是不是可以考虑不翻? 或在所有出现的地方都用注明英文原文? 但翻译为"**化"还有一个问题,reify如何翻译呢? 和reification相同?
|
-- 作者:orangebench -- 发布时间:7/11/2004 5:31:00 AM -- 我的翻译:仅供参考 ;-) 我认为的翻译的一个原则:让别人能看懂,在直译的基础上意译。 ;-) RDF的基本思想是:被描述的事物有很多属性,且这些属性都是有值的,另外这 些事物对应的资源可以通过说明这些属性及属性的值的陈述(就像上面的例子)来描 述。RDF有一套独特的术语来表达陈述的各个部分。 Specifically, the part that identifies the thing the statement is about 确切地说,在陈述中,用于表达陈述所要描述的事物(如上例中的网页),的那部分叫做主体,用于表达陈述所要描述的主体的各个不同属性(如上例中的:作者,创建日期,语种)的那部分就叫做谓词,用于表达属性的值的那部分叫做客体。
|
-- 作者:forwar -- 发布时间:7/11/2004 6:03:00 AM -- ----------------------------------------------------------------------------------------------------------------- 个人感觉翻成主体,谓词,客体是比我原先翻成主谓宾语更恰当些。至于admin说不翻注明英文原文感觉也好,我不管了,你们看着办了~~呵呵~~ 我们翻译的进度不算慢吧? -----------------------------------------------------------------------------------------------------------------
[此贴子已经被作者于2004-7-11 6:25:18编辑过]
|
-- 作者:admin -- 发布时间:7/11/2004 10:49:00 AM --
|
-- 作者:admin -- 发布时间:7/11/2004 10:50:00 AM -- 哇~~~forwar,orangebench..你们这么晚还在拼阿~~~~
|
-- 作者:forwar -- 发布时间:7/11/2004 3:45:00 PM -- 惭愧啊...偶那时候在看电影--怪物史莱克-2,片子不错。 ------------------------------------------------------------------------------------------------------------- the Uniform Resource Locator怎么翻呢?翻成统一资源定位器?还是用英文原文。
[此贴子已经被作者于2004-7-11 16:42:48编辑过]
|
-- 作者:orangebench -- 发布时间:7/11/2004 4:59:00 PM -- 用URL即可,它应该有规范翻译
|
-- 作者:trevol -- 发布时间:7/11/2004 5:41:00 PM -- 看了 ORANGEBENCH 和FORWAR的帖子,真是感到惭愧啊。。。 我这两天跑去爬长城去了。抓紧时间努力。。。 |
-- 作者:trevol -- 发布时间:7/11/2004 6:00:00 PM -- 用URL即可,它应该有规范翻译 以下是引用forwar在2004-7-11 15:45:05的发言: the Uniform Resource Locator怎么翻呢?翻成统一资源定位器?还是用英文原文。 ------------------------------------- Uniform Resource Locator 可以译为: 统一资源定位符; URL 不用译 Uniform Resource Identifier 可以译为: 同一资源标识符 ; URI也不用译 |
-- 作者:forwar -- 发布时间:7/11/2004 6:48:00 PM --
------收到. * network-accessible things, such as an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), or a group of other resources. * things that are not network-accessible, such as human beings, corporations, and bound books in a library. * abstract concepts that do not physically exist, such as the concept of a "creator". 为了达到这个目的,Web又规定了一套更通用的标识符系统,人们称之为URI。URL是URI的一种特殊形式。全部的URI分享着那些由不同人或组织都各自能创建的资源,并且使用它们区分鉴定事物。可是,URI并不局限于只能区分有网络地址或使用其他计算机存取机构的资源。事实上,一个创建好的URI可以涉及到一份陈述中所涉及的任何资源,这些资源包括: ※ 网络可及的资源,譬如,一个电子文档,一副图片,一种服务(例如,“今天洛山矶的天气预报”),或者是一组其他的资源; ※ 网络不可及的资源,譬如,人类,企业,在图书馆装订成册的书籍; ※ 抽象概念,比如“作者”这个概念; 其中:a more general form of identifier 翻成一套更通用的标识符系统,行不行? --------------------------------------------------------------------------------------------------------------- 传说中的leader回归了...... --------------------------------------------------------------------------------------------------------------- 刚才看了前面的帖子,正式翻译到7月中旬才开始麽?
[此贴子已经被作者于2004-7-11 19:39:32编辑过]
|
-- 作者:admin -- 发布时间:7/11/2004 11:35:00 PM -- 现在应该算7月中旬了吧
|
-- 作者:admin -- 发布时间:7/11/2004 11:46:00 PM --
------收到. * network-accessible things, such as an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), or a group of other resources. * things that are not network-accessible, such as human beings, corporations, and bound books in a library. * abstract concepts that do not physically exist, such as the concept of a "creator". 为了达到这个目的,Web又规定了一套更通用的标识符系统,人们称之为URI。URL是URI的一种特殊形式。全部的URI分享着那些由不同人或组织都各自能创建的资源,并且使用它们区分鉴定事物。可是,URI并不局限于只能区分有网络地址或使用其他计算机存取机构的资源。事实上,一个创建好的URI可以涉及到一份陈述中所涉及的任何资源,这些资源包括: ※ 网络可及的资源,譬如,一个电子文档,一副图片,一种服务(例如,“今天洛山矶的天气预报”),或者是一组其他的资源; ※ 网络不可及的资源,譬如,人类,企业,在图书馆装订成册的书籍; ※ 抽象概念,比如“作者”这个概念; 其中:a more general form of identifier 翻成一套更通用的标识符系统,行不行? 那句话的意思是: 所有URI的共同特征是:不同的人或组织可以彼此独立地创建并使用URI来标识事物。 network-accessible 翻成 网络可及的 怎么样? 传说中的leader回归了...... --------------------------------------------------------------------------------------------------------------- 刚才看了前面的帖子,正式翻译到7月中旬才开始麽?
|
-- 作者:forwar -- 发布时间:7/11/2004 11:58:00 PM -- 那句话的意思是: 所有URI的共同特征是:不同的人或组织可以彼此独立地创建并使用URI来标识事物。 是比我翻的清晰多了,看来我是理解错了。 ------------------------------------------------------------------------------------------------------------------ 反正这两段话翻的时候感觉很不顺,如果是做阅读理解的话,估计要挂挂了,呵呵... 在RDF中资源一词有其特殊含义,而且这里的意思并不是资源,所以感觉还是“事物”比较好...----- 回过头再看看,确实不应该全翻成资源。 谢谢admin的斧正!
|
-- 作者:wooyi -- 发布时间:7/12/2004 10:42:00 AM -- 斑竹你好,我叫WOOYI,刚刚注册你们的论坛,我很乐意为这次翻译活动也贡献自己一点微薄的力量,只是我的空闲时间不多且不固定,我本人也是对XML一无所知,刚开始学,所以翻译中的错误难免,希望各位指正。 |
-- 作者:admin -- 发布时间:7/12/2004 11:31:00 AM -- 欢迎欢迎。。尽管在翻译RDF Primer过程中,你可能会遇到不少困难。
|
-- 作者:orangebench -- 发布时间:7/12/2004 3:38:00 PM -- 一日一段 -0712 5.3 Interpreting RDF Schema Declarations
The difference between these approaches may seem to be only syntactic, but in fact there is an important difference. In the programming language class description, the attribute author is part of the description of class Book, and applies only to instances of class Book. Another class (say, softwareModule) might also have an attribute called author, but this would be considered a different attribute. In other words, the scope of an attribute description in most programming languages is restricted to the class or type in which it is defined. In RDF, on the other hand, property descriptions are, by default, independent of class definitions, and have, by default, global scope (although they may optionally be declared to apply only to certain classes using domain specifications). As a result, an RDF schema could describe a property exterms:weight without a domain being specified. This property could then be used to describe instances of any class that might be considered to have a weight. One benefit of the RDF property-based approach is that it becomes easier to extend the use of property definitions to situations that might not have been anticipated in the original description. At the same time, this is a "benefit" which must be used with care, to insure that properties are not mis-applied in inappropriate situations. Another result of the global scope of RDF property descriptions is that it is not possible in an RDF schema to define a specific property as having locally-different ranges depending on the class of the resource it is applied to. For example, in defining the property ex:hasParent, it would be desirable to be able to say that if the property is used to describe a resource of class ex:Human, then the range of the property is also a resource of class ex:Human, while if the property is used to describe a resource of class ex:Tiger, then the range of the property is also a resource of class ex:Tiger. This kind of definition is not possible in RDF Schema. Instead, any range defined for an RDF property applies to all uses of the property, and so ranges should be defined with care. However, while such locally-different ranges cannot be defined in RDF Schema, they can be defined in some of the richer schema languages discussed in Section 5.5.
|
-- 作者:gisemo -- 发布时间:7/12/2004 3:41:00 PM -- 希望能帮上忙,暑假期间,不太忙,对 RDF有一定了解 E-mail:emo_gis@163.com |
-- 作者:admin -- 发布时间:7/12/2004 4:48:00 PM -- 欢迎欢迎。。现在就可以开始翻译了
|
-- 作者:trevol -- 发布时间:7/13/2004 8:44:00 AM -- 赞成 ORANGEBENCH: 每天少看半小时新闻,少聊 半个小时的天,每天好好翻译一段RDF Primer. 坚持一个月。 |
-- 作者:trevol -- 发布时间:7/13/2004 10:11:00 AM -- 5. Defining RDF Vocabularies: RDF Schema RDF provides a way to express simple statements about resources, using named properties and values. However, RDF user communities also need the ability to define the vocabularies (terms) they intend to use in those statements, specifically, to indicate that they are describing specific kinds or classes of resources, and will use specific properties in describing those resources. RDF使用命名特性和值来表达与资源有关的简单声明。但是,在某些情况下,用户希望能够根据需要自定义一些词汇,然后用这些词汇来描述资源。这些词汇表明用户正在描述某种资源,并且会采用某些特定的特性来描述。 For example, the company example.com from the examples in Section 3.2 would want to describe classes such as exterms:Tent, and use properties such as exterms:model, exterms:weightInKg, and exterms:packedSize to describe them (QNames with various "example" namespace prefixes are used as the names of classes and properties here as a reminder that in RDF these names are actually URI references, as discussed in Section 2.1). 例如,3.2节所举例子中,example.com 公司想要描述一个类:exterms:Tent,并且使用特性 exterms:model,exterms:weightInKg 和 exterms:packedSize来描述它们。(这些类和特性的名字之前带有各种“example”名称空间前缀,表明:在RDF中,这些名字其实都是RUI引用,2.1小节中已经讨论过这个问题)。 Similarly, people interested in describing bibliographic resources would want to describe classes such as ex2:Book or ex2:MagazineArticle, and use properties such as ex2:author, ex2:title, and ex2:subject to describe them. Other applications might need to describe classes such as ex3:Person and ex3:Company, and properties such as ex3:age, ex3:jobTitle, ex3:stockSymbol, and ex3:numberOfEmployees. 类似的情况,那些对图书资源比较感兴趣的RDF开发人员可能会描述 ex2:Book或者ex2:MagazineArtical这样的类,并使用ex2:author, ex2:title ,ex2:subject之类的特性来描述这些类。其它的一些应用可能会描述诸如ex3:Person、ex3:Company 这样的类和ex3:age 、ex3:jobTitle、ex3:stockSymbol 、ex3:numberofEmployee之类的一些特性。 RDF itself provides no means for defining such application-specific classes and properties. Instead, such classes and properties are described as an RDF vocabulary, using extensions to RDF provided by the RDF Vocabulary Description Language 1.0: RDF Schema [RDF-VOCABULARY], referred to here as RDF Schema. RDF本身并不能针对特定应用需求来定义一些类和特性。这些类和特性被称为RDF词汇,它们需要通过RDF词汇描述语言:RDF Schema(RDF的一种扩展语言) 来定义。 |
-- 作者:orangebench -- 发布时间:7/13/2004 10:25:00 AM -- 这个"intened use"怎么翻译,比较好些? 谢谢 5.4 Other Schema Information As with a number of the built-in RDF properties such as rdf:value, the uses described for these RDF Schema properties are only their intended uses. [RDF-SEMANTICS] defines no special meanings for these properties, and RDF Schema does not define any constraints based on these intended uses. For example, there is no constraint specified that the object of a rdfs:seeAlso property must provide additional information about the subject of the statement in which it appears. 对于其他内嵌的RDF属性,如rdf:value, 他们的用途就是本来用途(intended use),文档[RDF-SEMANTICS]对这些属性没有定义特定的语义,RDF Schmea也没有基于他们的本来用途定义任何的约束。例如,没有约束限制属性rdfs:seeAlso的客体必须为它所在的陈述的主体提供额外的信息。 |
-- 作者:trevol -- 发布时间:7/13/2004 11:07:00 AM -- intended uses 译成“设计用途”怎么样? 参见 :http://www.w3.org/TR/2004/REC-rdf-mt-20040210/ Since the range of possible uses for rdf:value is so wide, it is difficult to give a precise statement which covers all the intended meanings or use cases. Users are cautioned, therefore, that the meaning of rdf:value may vary from application to application. In practice, the intended meaning is often clear from the context, but may be lost when graphs are merged or when conclusions are inferred.
|
-- 作者:orangebench -- 发布时间:7/13/2004 11:27:00 AM -- 非常好,谢谢!
|
-- 作者:orangebench -- 发布时间:7/13/2004 11:33:00 AM -- 一日一段 -0713 Another important difference is that RDF Schema descriptions are not necessarily prescriptive in the way programming language type declarations typically are. For example, if a programming language declares a class Book with an author attribute having values of type Person, this is usually interpreted as a group of constraints. The language will not allow the creation of an instance of Book without an author attribute, and it will not allow an instance of Book with an author attribute that does not have a Person as its value. Moreover, if author is the only attribute defined for class Book, the language will not allow an instance of Book with some other attribute. RDF Schema, on the other hand, provides schema information as additional descriptions of resources, but does not prescribe how these descriptions should be used by an application. For example, suppose an RDF schema states that an ex:author property has an rdfs:range of class ex:Person. This is simply an RDF statement that RDF statements containing ex:author properties have instances of ex:Person as objects. This schema-supplied information might be used in different ways. One application might interpret this statement as specifying part of a template for RDF data it is creating, and use it to ensure that any ex:author property has a value of the indicated (ex:Person) class. That is, this application interprets the schema description as a constraint in the same way that a programming language might. However, another application might interpret this statement as providing additional information about data it is receiving, information which may not be provided explicitly in the original data. For example, this second application might receive some RDF data that includes an ex:author property whose value is a resource of unspecified class, and use this schema-provided statement to conclude that the resource must be an instance of class ex:Person. A third application might receive some RDF data that includes an ex:author property whose value is a resource of class ex:Corporation, and use this schema information as the basis of a warning that "there may be an inconsistency here, but on the other hand there may not be". Somewhere else there may be a declaration that resolves the apparent inconsistency (e.g., a declaration to the effect that "a Corporation is a (legal) Person"). Moreover, depending on how the application interprets the property descriptions, a description of an instance might be considered valid either without some of the schema-specified properties (e.g., there might be an instance of ex:Book without an ex:author property, even if ex:author is described as having a domain of ex:Book), or with additional properties (there might be an instance of ex:Book with an ex:technicalEditor property, even though the schema describing class ex:Book does not describe such a property). In other words, statements in an RDF schema are always descriptions. They may also be prescriptive (introduce constraints), but only if the application interpreting those statements wants to treat them that way. All RDF Schema does is provide a way of stating this additional information. Whether this information conflicts with explicitly specified instance data is up to the application to determine and act upon. |
-- 作者:orangebench -- 发布时间:7/13/2004 1:06:00 PM -- property 翻译为特性 还是 属性?请统一
|
-- 作者:admin -- 发布时间:7/13/2004 2:20:00 PM -- 感觉属性好一些。。 但是会与attribute冲突。 (1)翻译为特性以区别于attribute的属性
|
-- 作者:orangebench -- 发布时间:7/13/2004 2:35:00 PM -- 我觉得都翻译为属性,比较符合习惯。 至于和attribute的冲突,可以注明英文,或者把attribute翻译为XML属性
|
-- 作者:admin -- 发布时间:7/13/2004 3:15:00 PM -- 请大家注意使用中文的标点符号。。 |
-- 作者:trevol -- 发布时间:7/13/2004 3:38:00 PM -- 感觉Property 和 Attribute之间还是有些细微的差异: PROPERTY 可能强调一个SUBJECT和其它SUBJECT之间的区别的性质,所以感觉译为“特性”合适一些; 而ATTRIBUTE 只是强调一个SUBJECT所具备的性质,故译为“属性”。 多听听大家的意见。 |
-- 作者:orangebench -- 发布时间:7/13/2004 3:50:00 PM -- 什么地方会混淆呢? 我只发现在rdf xml syntax中,有属性节点(attribute node)。在RDF中没有attribute的概念吧? |
-- 作者:orangebench -- 发布时间:7/13/2004 3:55:00 PM -- 一日一段--0714 5.4 Other Schema Information RDF Schema provides a number of other built-in properties, which can be used to provide documentation and other information about an RDF schema or about instances. For example the rdfs:comment property can be used to provide a human-readable description of a resource. The rdfs:label property can be used to provide a more human-readable version of a resource's name. The rdfs:seeAlso property can be used to indicate a resource that might provide additional information about the subject resource. The rdfs:isDefinedBy property is a subproperty of rdfs:seeAlso, and can be used to indicate a resource that (in a sense not specified by RDF; e.g., the resource may not be an RDF schema) "defines" the subject resource. RDF Vocabulary Description Language 1.0: RDF Schema [RDF-VOCABULARY] should be consulted for further discussion of these properties. RDF Schema还提供了一些其他内嵌的属性,这些属性可以用于为RDF Schema和实例提供文档和其他信息。例如,rdfs:comment属性可用于提供关于资源的易读的描述,rdfs:label属性可用于提供关于资源的更易读的名字, rdfs:seeAlso属性可用于提示其他地方可能有关于此资源的更多的描述,rdfs:isDefinedBy是rdfs:seeAlso的子属性,可用于提示其他地方有关于此资源的定义。对这些属性更多的讨论,请参考RDF Vocabulary Description Language 1.0: RDF Schema [RDF-VOCABULARY]。 As with a number of the built-in RDF properties such as rdf:value, the uses described for these RDF Schema properties are only their intended uses. [RDF-SEMANTICS] defines no special meanings for these properties, and RDF Schema does not define any constraints based on these intended uses. For example, there is no constraint specified that the object of a rdfs:seeAlso property must provide additional information about the subject of the statement in which it appears. 对于其他内嵌的RDF属性,如rdf:value, 他们的用途就是规范中的设计用途(intended use),文档[RDF-SEMANTICS]对这些属性没有定义特定的语义,RDF Schmea也没有基于他们的设计用途定义任何的约束。例如,没有约束限制属性rdfs:seeAlso的客体必须为它所在的陈述的主体提供额外的信息。 |
-- 作者:admin -- 发布时间:7/13/2004 5:11:00 PM -- 这几个怎么翻: * RDF Schema要不要翻译 * RDF URIs : RDF的URIs还是不翻。 * Like HTML, this RDF/XML is machine processable and, using URIs, can link pieces of information across the Web. * The following documents contribute to the specification of RDF: |
-- 作者:orangebench -- 发布时间:7/13/2004 5:56:00 PM --
|
-- 作者:forwar -- 发布时间:7/13/2004 8:23:00 PM --
是在译文里面麽?是不是要和英文的符号对应起来? ------------------------------- 大家都风风火火地干起来了,真是鼓舞人心啊!! |
-- 作者:admin -- 发布时间:7/13/2004 8:29:00 PM -- 恩。。是的
|
-- 作者:forwar -- 发布时间:7/13/2004 9:19:00 PM -- TO admin:无法编辑2.2The RDF Model这一段,点[编辑]后看到的是2.1 基本概念。 |
-- 作者:admin -- 发布时间:7/13/2004 9:40:00 PM --
那就电击下一个[编辑] |
-- 作者:trevol -- 发布时间:7/13/2004 10:18:00 PM -- RDF Schema does not provide a vocabulary of application-specific classes like exterms:Tent, ex2:Book, or ex3:Person, and properties like exterms:weightInKg, ex2:author or ex3:JobTitle. Instead, it provides the facilities needed to describe such classes and properties, and to indicate which classes and properties are expected to be used together (for example, to say that the property ex3:jobTitle will be used in describing a ex3:Person). RDF Schema 并没有针对特定应用提供诸如 exterms:Tent , ex2:Book 或者 ex3:Person这样的一些类或者是诸如 exterms:weightInKg 、ex2:author 或者 ex3:JobTitle 这样的一些特性词汇。RDFS只是提供了描述一种这些类和特性的能力 (facilities),并且可以暗示某些类和特性期望合在一起使用(例如,特性 ex3:jobTitle 应该用来描述ex3:Person)。 In other words, RDF Schema provides a type system for RDF. The RDF Schema type system is similar in some respects to the type systems of object-oriented programming languages such as Java. For example, RDF Schema allows resources to be defined as 换句话说,RDF Schema为RDF提供了一个类型系统。RDF Schema 类型系统在某些方面类似于Java这样的面向对象编程语言的类型系统。例如,RDF Schema允许资源被定义为一个或者多个类的实例。另外,RDFS通常把类组织成为一种分级结构;例如,类 ex:Dog可以定义为ex:Mammal的子类,而ex:Mammal又是ex:Animal的子类。 如果某个资源是类 ex:Dog的实例,那么隐含意味着它也是ex:Animal的实例。 However, RDF classes and properties are in some respects very different from programming language types. RDF class and property descriptions do not create a straightjacket into which information must be forced, but instead provide additional 然而,RDF 类和特性在某些方面又与编程语言的类型系统有着明显的差异。RDF类和特性并没有过多束缚资源的描述方式,而是提供了一些关于RDF 资源的额外描述信息。这些添加的信息可以通过各种方式来使用,具体内容将在5.3节中介绍。 The RDF Schema facilities are themselves provided in the form of an RDF vocabulary; that is, as a specialized set of predefined RDF resources with their own special meanings. The resources in the RDF Schema vocabulary have URIrefs with the prefix http://www.w3.org/2000/01/rdf-schema# (conventionally associated with the QName prefix rdfs:). Vocabulary descriptions (schemas) written in the RDF Schema language are legal RDF graphs. RDF Schema 所具有的这些能力本身也是以 RDF词汇形式提供的。也就是说,这些RDF 词汇是一组带有特殊含义的、预定义的RDF资源。 这些资源的(RDF Schema词汇)URI带有前缀 http://www.w3.org/2000/01/rdf-schema# (QName通常采用前缀 rdfs:)。采用RDF Schema 语言所定义的词汇描述(schemas)也是合法的RDF图。 Hence, RDF software that is not written to also process the additional RDF Schema vocabulary can still interpret a schema as a legal RDF graph consisting of various resources and properties, but will not "understand" the additional built-in meanings of the RDF Schema terms. To understand these additional meanings, RDF software must be written to process an extended language that includes not only the rdf: vocabulary, but also the rdfs: vocabulary, together with their built-in meanings. This point will be illustrated in the next section. 下一小节将详细分析RDF Schema的基本资源和特性。 |
-- 作者:trevol -- 发布时间:7/13/2004 10:20:00 PM -- RDF PRIMER 这篇文章感觉写得罗罗嗦嗦。。。十分不爽。。。 |
-- 作者:orangebench -- 发布时间:7/13/2004 11:03:00 PM -- 呵呵。没办法,入门篇嘛。我开始翻译4。3 RDF Reification 了 |
-- 作者:admin -- 发布时间:7/13/2004 11:16:00 PM --
讨论讨论reification怎么翻好~~~ |
-- 作者:orangebench -- 发布时间:7/14/2004 12:15:00 AM -- 一日一段 -0715 5.5 Richer Schema Languages RDF Schema provides basic capabilities for describing RDF vocabularies, but additional capabilities are also possible, and can be useful. These capabilities may be provided through further development of RDF Schema, or in other languages based on RDF. Other richer schema capabilities that have been identified as useful (but that are not provided by RDF Schema) include: RDF Schema提供了描述RDF词汇集的基本能力,更强的表达能力是可能的,也是有用的。这些能力可能通过RDF Schema的发展提供,也可能由其他基于RDF的语言提供。其他已经被认为有用但RDF Schema没有提供的,更丰富的表达能力包括: • cardinality constraints on properties, e.g., that a Person has exactly one biological father. The additional capabilities mentioned above, in addition to others, are the targets of ontology languages such as DAML+OIL [DAML+OIL] and OWL [OWL]. Both these languages are based on RDF and RDF Schema (and both currently provide all the additional capabilities mentioned above). The intent of such languages is to provide additional machine-processable semantics for resources, that is, to make the machine representations of resources more closely resemble their intended real world counterparts. While such capabilities are not necessarily needed to build useful applications using RDF (see Section 6 for a description of a number of existing RDF applications), the development of such languages is a very active subject of work as part of the development of the Semantic Web. |
-- 作者:trevol -- 发布时间:7/14/2004 9:03:00 AM -- [quto] 以下是引用orangebench在2004-7-13 23:03:58的发言: 呵呵。没办法,入门篇嘛。我开始翻译4。3 RDF Reification 了 讨论讨论reification怎么翻好~~~ 物化,对象化,具体化~~~请补充。。 [/quto] “物化”和“对象化”通常是哲学、政治经济学对REIFICATION在具体语境下的 翻译,在这里采用这种翻译可能会让读者有点摸不着头脑。 我们不如直接采用 REIFICATION这个词的本意-“具体化”,在这种语境下应该是“声明化”,呵呵,不过好像没有人这样译。 |
-- 作者:orangebench -- 发布时间:7/14/2004 9:43:00 AM -- reification建议为"具体化" Literal 呢? 目前的翻译是“字面量”,我们在逻辑里面一般翻译为“文字”, XML Literal 呢? literal value 呢? plain literal? typed literal? |
-- 作者:trevol -- 发布时间:7/14/2004 9:58:00 AM -- Literal -建议译为“文字” plain literal -“平凡文字” 大家讨论讨论。。
|
-- 作者:zhuxuanlv -- 发布时间:7/14/2004 11:32:00 AM -- 好不错,有创意!置顶! |
-- 作者:orangebench -- 发布时间:7/14/2004 11:38:00 AM -- 请参与翻译的朋友,对自己翻译的东西,做好本地备份,以防万一。 |
-- 作者:admin -- 发布时间:7/14/2004 12:14:00 PM --
我对reification是这样理解的(不知对不对): 就是一个statement本来是对某个客观事物的描述,这个statement是主动的,主观的。 而reification指的是,把一个主动的,主观的statement看作一个客观事物(即将statement客观化,或物化),然后对他进行描述的过程。 如果可以这样理解的话,我觉得并没有看到 抽象->具体的过程呀~~~~只看到了物化(客观化)的过程。。 不知说的对不对~~~ 欢迎讨论。。。 |
-- 作者:admin -- 发布时间:7/14/2004 12:16:00 PM -- 提交之前,最好先在本地复制一份。以防止提交失败,造成内容丢失。
|
-- 作者:admin -- 发布时间:7/14/2004 2:19:00 PM --
需要把 ===2.1 Basic Concepts === <BR> 最后的<BR> 去掉。 即=== 标题 === 后不能有其他符号 |
-- 作者:cquzjh -- 发布时间:7/14/2004 5:39:00 PM -- 算我一个,愿尽绵薄之力,呵呵! |
-- 作者:forwar -- 发布时间:7/14/2004 8:40:00 PM --
哦,是这样啊,我明白了。多谢指教! |
-- 作者:orangebench -- 发布时间:7/14/2004 9:03:00 PM -- 你可以开始翻译,挑还没有翻译的,如4.1; 4.2 谢谢!
|
-- 作者:向日葵 -- 发布时间:7/15/2004 3:14:00 PM -- 我去Wiki注册了,sunflower是也 翻译计划就要开始了吧:) |
-- 作者:admin -- 发布时间:7/15/2004 3:57:00 PM -- 已经完成15%了。。欢迎加入我们~~~
|
-- 作者:orangebench -- 发布时间:7/15/2004 5:13:00 PM -- 我准备开始翻译4。1;4。2 了,大家不要和我抢 ;-) |
-- 作者:orangebench -- 发布时间:7/16/2004 12:08:00 AM -- 【一日一段- 0716】 4.2 RDF Collections 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]:
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). 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]:
Example 17: RDF/XML for a Collection of Students <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]"
</rdf:RDF>
Example 18: RDF/XML for a Collection of Students in "Longhand" <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]"> </rdf:Description> <rdf:Description rdf:nodeID="sch1"> </rdf:Description> <rdf:Description rdf:nodeID="sch2"> </rdf:Description> <rdf:Description rdf:nodeID="sch3"> </rdf:Description> </rdf:RDF>
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. |
-- 作者:orangebench -- 发布时间:7/16/2004 12:10:00 AM -- 【一日一段 -0717】 4.4 More on Structured Values: rdf:value exstaff:85740 exterms:manager exstaff:62345 .
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: address(exstaff:85740, "1501 Grant Avenue", "Bedford", "Massachusetts", "01730")
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.)
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., 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. 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: 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]:
Example 21: RDF/XML using rdf:value <!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:RDF>
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. 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. 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]). |
-- 作者:orangebench -- 发布时间:7/16/2004 12:11:00 AM -- 【一日一段 -0718】 4.5 XML Literals 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":
Example 22: RDF/XML for an XML Literal <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]"
</rdf:RDF>
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. |
-- 作者:orangebench -- 发布时间:7/16/2004 12:13:00 AM -- 好了,休息三天!! 不翻了,累死了。 |
-- 作者:forwar -- 发布时间:7/16/2004 12:25:00 AM -- 偶也来一日一段 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 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.) (比如在以“http://purl.org/dc/elements/1.1/language”做谓词的例子,文字(literal)就是英文的国际标准--双字母码。) 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: <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. 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. ---------------------------------
|
-- 作者:yuji1998 -- 发布时间:7/16/2004 1:32:00 AM -- 我考,我该翻译哪一段的内容阿。 还剩哪几段每人要阿,我无所谓的,哪里都可以 |
-- 作者:forwar -- 发布时间:7/16/2004 2:09:00 AM -- 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前缀(这些前缀无需说明就可使用),定义如下: Obvious variations on the "example" prefix ex: will also be used as needed in the examples, for instance, prefix exterms:, namespace URI: http://www.example.org/terms/ (for terms used by an example organization), identifiers), Using this new shorthand, the previous set of triples can be written as: -----------------------------------
[此贴子已经被作者于2004-7-16 2:44:27编辑过]
|
-- 作者:orangebench -- 发布时间:7/16/2004 8:58:00 AM -- 看一下这个:http://wiki.w3china.org/wiki/index.php/RDF入门_推荐标准 就知道哪些还没有翻译了。 第6节还没开始,现在基本的安排是: 你可以找第2,第3节的后面的小节 或者第6节翻译。;-)
|
-- 作者:cwzb -- 发布时间:7/16/2004 5:42:00 PM -- 可惜我E文不好 |
-- 作者:trevol -- 发布时间:7/16/2004 10:39:00 PM -- 5.1 Describing Classes- 描述类 A basic step in any kind of description process is identifying the various kinds of things to be described. RDF Schema refers to these "kinds of things" as classes. A class in RDF Schema corresponds to the generic concept of a Type or Category, somewhat like the notion of a class in object-oriented programming languages such as Java. RDF classes can be used to represent almost any category of thing, such as Web pages, people, document types, databases or abstract concepts. Classes are described using the RDF Schema resources rdfs:Class and rdfs:Resource, and the properties rdf:type and rdfs:subClassOf. 描述过程通常从划分被描述事物的种类开始。RDF Schema 把事物的种类称之为类。 RDF Schema中的类与我们通常所说的类型或者分类基本相同,在某种程度上也类似于Java这样的面向对象编程语言中的类的概念。RDF类可以用来表示事物的任何分类,例如,网页、人、文档类型、数据库或者抽象概念。类可以通过 RDF Schema中的资源:rdfs:Class 、rdfs:Resource,以及特性:rdf:type 和rdfs:subClassOf来表示。例如,假设某个组织-example.org 想要使用RDF来提供有关不同种类摩托车(Motor vehicles)的信息,它首先需要一个类来表达摩托车的分类。属于某个类的资源被称为该类的实例。在本例中,example.org被设计为这个摩托车类的实例。 在RDF Schema中,任何具有特性 rdf:type,并且该特性值是 rdfs:Class 的资源都是一个类。因此,摩托车类可以用 URI引用表示为:ex:MotorVehicle(ex: 表示URI引用-http://www.example.org/schemas/vehicles, 该前缀表明URI引用来自 example.org所创建的词汇) ,这个资源具有rdf:type 特性,该特性的值是rdfs:Class。 也就是说,example.org应该编写如下的 RDF 声明: As indicated in Section 3.2, the property rdf:type is used to indicate that a resource is an instance of a class. So, having described ex:MotorVehicle as a class, resource exthings:companyCar would be described as a motor vehicle by the RDF statement: 正如在3.2小节中所讨论的那样,特性 rdf:type用来表明该资源是某个类的实例。因此,将ex:MotorVehicle描述为类之后,资源exthing:companyCar可以用RDF声明描述为摩托车:exthings:companyCar rdf:type ex:MotorVehicle . (This statement uses a common convention that class names are written with an initial uppercase letter, while property and instance names are written with an initial lowercase letter. However, this convention is not required in RDF Schema. The statement also assumes that example.org has decided to define separate vocabularies for classes of things, and instances of things.) (在书写声明的时候,通常会遵守一些约定,例如,类名的首字母通常会用大写,特性和实例名称的首字母往往用小写。但是,RDF Schema并不强制要求这一点。 声明假定example.org 为每类事物及事物实例会定义特定的词汇(separate vocabularies)。)
The resource rdfs:Class itself has an rdf:type of rdfs:Class. A resource may be an instance of more than one class. rdfs:Class也是资源,而且它本身的rdf:type 是 rdfs:Class。 一个资源可以是多个类的实例。描述完ex:MotorVehicle之后,example.org可能需要再定义其它的类来代表各种特定种类的摩托车,例如,passenger veicles, vans, minivans,等等。这些类可以采用和类ex:MotorVehicle同样的方法来定义。首先为每个新建的类指定一个URI引用,然后编写如下的 RDF声明将这些资源定义为类,如: and so on. However, these statements by themselves only describe the individual classes. example.org may also want to indicate their special relationship to class ex:MotorVehicle, i.e., that they are specialized kinds of MotorVehicle. 上面的这些声明本身只是描述了单个的类。example.org可能还想要描述类之间的关系。例如, 类 ex:MotorVehicle是一种特殊的MotorVehicle。 这种两种类之间的特化关系可以用预定义的特性:rdfs:subClassOf来描述。 例如,可以编写代码 ex:Van rdfs:subClassOf ex:MotorVehicle 来声明:ex:Van是一种特殊的ex:MotorVehicle。 在上面的例子中,rdfs:subClassOf的含义是,任何ex:Van类的实例同时也是ex:MotroVehicle的实例。因此,如果资源exthings:companyVan是ex:Van的实例,那么,基于所声明的rdfs:subClassOf关系, RDF软件可以理解RDF Schema词汇,并推理出额外的有用信息,exthings:companyVan 也是ex:MotorVehicle的实例。 exthings:companyVan的例子说明了一点:RDF Schema可以定义一种扩展语言。但是,RDF本身并没有定义 RDF Schema中的词汇,比如 rdfs:subClassOf所具有的含义. 因此,虽然某个RDF schema定义了ex:Van和ex:MotorVehicle之间的 rdfs:subClassOf 关系,但是 RDF 软件只能认识到这个声明是一个三元组,谓词是 rdfs:subClassOf。RDF软件并不能理解rdfs:subClassOf所代表的含义,也就是说,并且不能推理出新加事实:exthing:companyVan 也是 ex:MotorVehicle的实例。造成这种现象的原因在于理解RDF的软件并不一定能够理解RDF Schema 术语 The rdfs:subClassOf property is transitive. This means, for example, that given the RDF statements: rdfs:subClassOf特性具有传递性,也就是说,如果给出一些RDF 声明: ex:Van rdfs:subClassOf ex:MotorVehicle . RDF Schema defines ex:MiniVan as also being a subclass of ex:MotorVehicle. As a result, RDF Schema defines resources that are instances of class ex:MiniVan as also being instances of class ex:MotorVehicle (as well as being instances of class ex:Van). A class may be a subclass of more than one class (for example, ex:MiniVan may be a subclass of both ex:Van and ex:PassengerVehicle). RDF Schema defines all classes as subclasses of class rdfs:Resource (since the instances belonging to all classes are resources). 这些声明可以推理出ex:MiniVan同时也是ex:MotroVehicle 的子类。相应的,如果RDF Schema定义了某个资源是ex:MiniVan的实例,那么它同时也会是ex:MotorVehicle的实例(也是类ex:Van的实例)。类可以是多个类的子类。(例如:ex:MiniVan 可能是ex:Van和ex:PassengerVehicle的子类)。RDF Schema直接定义所有的类都是rdfs:Resource的子类(因为任何类的实例也都资源)。 图18 显示了本例中所讨论的类层次图。
|
-- 作者:trevol -- 发布时间:7/16/2004 11:18:00 PM -- ORAGEBENCH 好好休息两天啊。。。不要累坏了身体。。。呵呵 |
-- 作者:forwar -- 发布时间:7/17/2004 3:32:00 AM -- 偶也来一日一段 Since RDF uses URIrefs instead of words to name things in statements, RDF refers to a set of URIrefs (particularly a set intended for a specific purpose) as a vocabulary. Often, the URIrefs in such vocabularies are organized so that they can be represented as a set of QNames using a common prefix. That is, a common namespace URIref will be chosen for all terms in a vocabulary, typically a URIref under the control of whoever is defining the vocabulary. URIrefs that are contained in the vocabulary are formed by appending individual local names to the end of the common URIref. This forms a set of URIrefs with a common prefix. For instance, as illustrated by the previous examples, an organization such as example.org might define a vocabulary consisting of URIrefs starting with theprefixhttp://www.example.org/terms/ for terms it uses in its business, such as "creation-date" or "product", and another vocabulary of URIrefs starting with http://www.example.org/staffid/ to identify its employees. RDF uses this same approach to define its own vocabulary of terms with special meanings in RDF. The URIrefs in this RDF vocabulary all begin with http://www.w3.org/1999/02/22-rdf-syntax-ns#, conventionally associated with the QName prefix rdf:. The RDF Vocabulary Description Language (described in Section 5) defines an additional set of terms having URIrefs that begin with http://www.w3.org/2000/01/rdf-schema#, conventionally associated with the QName prefix rdfs:. (Where a specific QName prefix is commonly used in connection with a given set of terms in this way, the QName prefix itself is sometimes used as the name of the vocabulary. For example, someone might refer to "the rdfs: vocabulary".) 从RDF用在陈述中用URIref替代词语来命名事物开始,RDF就通过引用词汇表来使用URIref(特别是那些适合具体的目的URIref)。通常,为了能像一套有公用前缀的QName那样被描述,能充当这种词汇表的URIref都是被组织过的。也就是说 文章里面的terms我翻成术语,不知行不行? 使用公用的URI前缀提供了一种便捷的方法来组织与一套术语集相关的URIrefs,然而,着仅仅只是一种约定。RDF模型只认可完整的URIrefs;它不会去看URIrefs的具体内容或使用任何关于它们结构的知识。特别地,RDF不会仅仅因为URIrefs有一个公用的主要前缀而认定这些URIrefs之间有联系(更深入的探讨请看附录A)。此外,RDF也不因为URErefs有不同的主要前缀而认定这些URIrefs不会出现在同一个词汇表里面。一个独特的组织,过程步骤,设备等等都可以通过任意使用其他词汇表里的URIrefs为它定义一个有意义的词汇表。 In addition, sometimes an organization will use a vocabulary's namespace URIref as the URL of a Web resource that provides further information about that vocabulary. For example, as noted earlier, the QName prefix dc: will be used in Primer examples, associated with the namespace URIref http://purl.org/dc/elements/1.1/. In fact, this refers to the Dublin Core vocabulary described in Section 6.1. Accessing this namespace URIref in a Web browser will retrieve additional information about the 另外,有时一个组织将使用词汇表的URIref命名空间用作是提供关于该词汇表的详细资料这种Web资源所在地的URL。例如:像起初很著名的QName前缀dc: 将会在入门书的例子中用到,它是和命名空间URIref http://purl.org/dc/elements/1.1/相关联的。事实上,这参考使用了在6.1节阐述的都柏林核心词汇表。通过在网页浏 In the rest of the Primer, the term vocabulary will be used when referring to a set of URIrefs defined for some specific purpose, such as the set of URIrefs defined by RDF for its own use, or the set of URIrefs defined by example.org to identify its employees. The term namespace will be used only when referring specifically to the syntactic concept of an XML namespace (or in describing the URI assigned to a prefix in a QName). 在这本入门书的其余部分里,当涉及到一些为特殊目而定义的一套URIref,比如供RDF自身的使用而定义的各种URIref ,或者是example.org定义的用来区分它雇员的一套URIref,时都将会用到术语词汇集。命名空间的术语只是当明确地涉 ----------------------------------- 翻成了:也就是说,一个公用的命名空间URIref将会被在一个词汇表里的全部条件所选择,并且受控于任何一个定义这个词汇表的人。 2.The URIrefs in this RDF vocabulary all begin with http://www.w3.org/1999/02/22-rdf-syntax-ns#, conventionally associated with the QName prefix rdf:. 翻成了:在这个RDF的词汇表中的URIrefs都是以http://www.w3.org/1999/02/22-rdf-syntax-ns#做开头的,并按照惯例把它和QName前缀rdf:关联起来。 3.there is nothing that says that URIrefs with different leading prefixes cannot be considered part of the same vocabulary. A particular organization, process, tool, etc. can define a vocabulary that is significant for it, using URIrefs from any number of other vocabularies as part of its vocabulary. 4.The term namespace will be used only when referring specifically to the syntactic concept of an XML namespace (or in describing the URI assigned to a prefix in a QName). 翻成了:命名空间的术语只是当明确地涉及到一个XML命名空间的句法概念的时候才会用的到(或者是当描述一个已被赋值到一个QName前缀的URI的时候)。 |
-- 作者:admin -- 发布时间:7/17/2004 4:01:00 PM -- 这几个如何翻译(目前的翻译在=>后) |
-- 作者:trevol -- 发布时间:7/17/2004 7:24:00 PM -- -- 作者:admin -- 发布时间:2004-7-17 16:01:15 -- |
-- 作者:orangebench -- 发布时间:7/17/2004 8:42:00 PM -- to trevol: 这样不太好吧 ;-) 不管怎样,老婆应该是第一位的! -------------------------------------------------------------------------- |
-- 作者:trevol -- 发布时间:7/17/2004 8:42:00 PM --
1.That is, a common namespace URIref will be chosen for all terms in a vocabulary, typically a URIref under the control of whoever is defining the vocabulary. 翻成了:也就是说,一个公用的命名空间URIref将会被在一个词汇表里的全部条件所选择,并且受控于任何一个定义这个词汇表的人。 2.The URIrefs in this RDF vocabulary all begin with http://www.w3.org/1999/02/22-rdf-syntax-ns#, conventionally associated with the QName prefix rdf:. 翻成了:在这个RDF的词汇表中的URIrefs都是以http://www.w3.org/1999/02/22-rdf-syntax-ns#做开头的,并按照惯例把它和QName前缀rdf:关联起来。 4.The term namespace will be used only when referring specifically to the syntactic concept of an XML namespace (or in describing the URI assigned to a prefix in a QName). 翻成了:命名空间的术语只是当明确地涉及到一个XML命名空间的句法概念的时候才会用的到(或者是当描述一个已被赋值到一个QName前缀的URI的时候)。 ----> 术语 命名空间只是在特指XML命名空间这个语法概念的时候才会使用(或者用来描述 QName中的URI前缀) |
-- 作者:trevol -- 发布时间:7/17/2004 8:47:00 PM --
欠老婆的时间,以后慢慢再补吧。。。呵呵 |
-- 作者:forwar -- 发布时间:7/17/2004 10:40:00 PM -- 这样翻确实清楚多了,多谢leader的指点!!! |
-- 作者:forwar -- 发布时间:7/17/2004 10:50:00 PM -- 翻译完成25%啦,发贴庆祝一下.... ---------------------------- 其实:我是想占这有纪念意义的第100楼,请大家原谅我的私心...哈哈哈~~~
|
-- 作者:admin -- 发布时间:7/17/2004 11:06:00 PM --
trevol的敬业精神真令人敬佩阿~~~~
|
-- 作者:mangz -- 发布时间:7/18/2004 9:50:00 PM -- admin 和trevol你们好,我在http://Wiki.w3china.org 注册好,名字是:mangz,我每天可以有3小时左右的时间,我正想做这方面的课题,做一下翻译,有助于我尽快熟悉这个领域。翻译那个部分都可以,尽管分配:zchchina@hotmail.com |
-- 作者:forwar -- 发布时间:7/18/2004 11:40:00 PM -- 欢迎mangz的加入!!!!! |
-- 作者:admin -- 发布时间:7/19/2004 12:15:00 AM -- 欢迎欢迎。。好像第六部分和附录还没人翻。。
|
-- 作者:qqqdragon -- 发布时间:7/19/2004 10:51:00 AM -- 我想加入,我的毕业设计就是这方面的内容。如果需要,请发信:qqqdragon@sohu.com. |
-- 作者:trevol -- 发布时间:7/19/2004 1:53:00 PM --
欢迎,欢迎! 第六章中可以挑选一个感兴趣的小节进行翻译! 谢谢! |
-- 作者:mangz -- 发布时间:7/19/2004 3:29:00 PM -- ok |
-- 作者:Candy -- 发布时间:7/19/2004 4:23:00 PM -- 我研二了,对XML有一定了解,正好这一个月有时间,想参加这次翻译计划。 我的MSN是:candy_yh@hotmail.com [此贴子已经被作者于2004-7-19 16:44:33编辑过]
|
-- 作者:trevol -- 发布时间:7/19/2004 5:04:00 PM --
欢迎,欢迎! 帮主正在翻译第三章-RDF的XML语法。 你可以去帮帮他。 再次感谢 Candy 美眉的热情参与! |
-- 作者:Candy -- 发布时间:7/19/2004 5:24:00 PM -- ok 那我也从第三章开始翻译吧,如何? |
-- 作者:admin -- 发布时间:7/19/2004 5:39:00 PM -- 好啊~~ 3.1我快要完成了,要不3.2就交给你了?
|
-- 作者:Candy -- 发布时间:7/19/2004 5:47:00 PM -- ok 我先翻译3.2和3.3
|
-- 作者:forwar -- 发布时间:7/20/2004 2:24:00 AM -- 终于把2.2节The RDF Model搞定了,有几个词组不知怎么翻好: 1.formal logic 翻成形式逻辑行不行? 2.RDF applications 翻成RDF应用程序行不行? 3.It will simply not associate with the triple any special meaning that the vocabulary developer might have associated with a URIref like ed:dsfbups. 这句话看不懂...凑合着翻了一下:这只不过是没把词汇表开发人员赋值给一个URIref(比如 ed:dsfbups)的任何特定含义赋值给三元组。special meaning 翻成特定含义,还是特殊含义? -------------------------------------- 心情好愉悦...爽!!! |
-- 作者:orangebench -- 发布时间:7/20/2004 9:27:00 AM -- 我的看法:
|
-- 作者:orangebench -- 发布时间:7/20/2004 7:56:00 PM -- 翻译软件翻译的?;-) 2.4 Typed Literals The last section described how to handle situations in which property values represented by plain literals had to be broken up into structured values to represent the individual parts of those literals. Using this approach, instead of, say, recording the date a Web page was created as a single exterms:creation-date property, with a single plain literal as its value, the value would be represented as a structure consisting of the month, day, and year as separate pieces of information, using separate plain literals to represent the corresponding values. However, so far, all constant values that serve as objects in RDF statements have been represented by these plain (untyped) literals, even when the intent is probably for the value of the property to be a number (e.g., the value of a year or age property) or some other kind of more specialized value.
|
-- 作者:weekend -- 发布时间:7/20/2004 8:20:00 PM -- 我也想帮忙翻译啊。 我一个星期应该可以拿出10小时吧。 你们需要帮忙吗? 我已经注册好了。用户名是 weekend |
-- 作者:orangebench -- 发布时间:7/20/2004 11:17:00 PM -- 4。3节这段感觉很难翻译,不是完全理解其中的含义,特别第2句和最后一句。请大家看看。 Note that asserting the reification is not the same as asserting the original statement, and neither implies the other. That is, when someone says that John said something about the weight of a tent, they are not making a statement about the weight of a tent themselves, they are making a statement about something John said. Conversely, when someone describes the weight of a tent, they are not also making a statement about a statement they made (since they may have no intention of talking about things called "statements").The text above deliberately referred in a number of places to "the conventional use of reification". As noted earlier, care is needed when using the RDF reification vocabulary because it is easy to imagine that the vocabulary defines some things that are not actually defined. While there are applications that successfully use reification, they do so by following some conventions, and making some assumptions, that are in addition to the actual meaning that RDF defines for the reification vocabulary, and the actual facilities that RDF provides to support it. |
-- 作者:orangebench -- 发布时间:7/20/2004 11:52:00 PM -- 这段也不太明白,特别是最后几句。 ;-( Using rdf:ID as shown in Example 20 generates the reification automatically, and provides a convenient way of indicating the URIref to be used as the subject of the statements in the reification. Moreover, it provides a partial "hook" relating the triples in the reification with the piece of RDF/XML syntax that caused them to be created, since the value triple12345 of the rdf:ID attribute is used to generate the URIref of the subject of the reification triples. However, this relationship is once again outside RDF, since there is nothing in the resulting triples that explicitly says that the original triple had the URIref exproducts:triple12345 (RDF does not assume there is any relationship between a URIref and any RDF/XML that it might have been used or abbreviated in). |
-- 作者:weekend -- 发布时间:7/21/2004 4:02:00 AM --
也就是说,当有的人说,John说了些关于帐篷重量的东西,他们并不是在陈述一个帐篷的重量,他们是在陈述John说了什么。 这样会不会好点? |
-- 作者:trevol -- 发布时间:7/21/2004 11:41:00 AM --
欢迎,欢迎。。。 您可以翻译 6。3 节 XPackage 谢谢! |
-- 作者:trevol -- 发布时间:7/21/2004 11:43:00 AM -- 5。1 和5。2 都已经翻译完了。。。现在正在校对。。 大家加油啊!
|
-- 作者:orangebench -- 发布时间:7/21/2004 12:14:00 PM -- section 4.3 ,这个"hook"怎么翻译阿? Moreover, it provides a partial "hook" relating the triples in the reification with the piece of RDF/XML syntax that caused them to be created, since the value triple12345 of the rdf:ID attribute is used to generate the URIref of the subject of the reification triples.
|
-- 作者:orangebench -- 发布时间:7/21/2004 12:18:00 PM -- 有时间的话,5.3-5.5 也看看吧,看是否和你前面的翻译有冲突。 ;-) 今天把4.3 翻译完,但有些还是拿不准,不是完全理解了4.3说的东西,这节希望
|
-- 作者:orangebench -- 发布时间:7/21/2004 12:20:00 PM -- 感觉你的翻译清晰易懂些,谢谢 ;-)
|
-- 作者:admin -- 发布时间:7/21/2004 12:27:00 PM -- 翻译为钩子 ? 这样会不会太难听了?
|
-- 作者:admin -- 发布时间:7/21/2004 12:29:00 PM -- 欢迎欢迎~~~~我们的力量越来越强了
|
-- 作者:forwar -- 发布时间:7/21/2004 1:12:00 PM --
这个不是我弄的...估计是翻译软件翻的,不通顺啊。 |
-- 作者:orangebench -- 发布时间:7/21/2004 1:31:00 PM -- //哈哈,像Leader学习 第四章已经翻译完了。。。现在正在校对。。 大家加油啊! |
-- 作者:trevol -- 发布时间:7/21/2004 2:37:00 PM --
HOOK -挂钩、钩子 ,至少和WINDOWS编程中的术语是一致的。如果感觉绕口的话,就保留原文 HOOK。 比译成- 虎克 -强 ! 呵呵 |
-- 作者:orangebench -- 发布时间:7/21/2004 2:55:00 PM -- 那partial hook呢? 半钩? 还是 离别钩? 我翻译的是“窍门”
|
-- 作者:admin -- 发布时间:7/21/2004 5:03:00 PM -- 晕阿~~~怎么还有partial hook
|
-- 作者:trevol -- 发布时间:7/21/2004 5:25:00 PM --
Partial hook------------是不是我们小时候钓鱼用的“偏勾”啊! 写这个东东的肯定是个钓鱼迷。。。 开玩笑。。 |
-- 作者:weekend -- 发布时间:7/22/2004 6:03:00 AM -- 好d。我会努力!
|
-- 作者:nybon -- 发布时间:7/22/2004 11:10:00 AM -- 我也想加入翻译,可以吗,时间不是很固定,一天一个小时差不多吧,我已经注册了在那里,用户名是nybon.我应该从哪里开始翻呢,分配一小节试试吧先^_^,太多会被吓到. 还有我建议一下那个RDF Primer的wiki页面是不是可以分一下页呢,每一章节分一下或者怎么样,感觉载入那个页面实在太费时间了,而且很长,滚动条都要拉半天才能到下面,看起来比较困难好像. |
-- 作者:orangebench -- 发布时间:7/22/2004 11:23:00 AM -- 非常欢迎。我觉得你可以在第六节,随意挑一小节翻译。 rdf primer是比较大,我也向admin提过这问题,他说分页难度太大,只好讲究了。;-)
|
-- 作者:orangebench -- 发布时间:7/22/2004 11:31:00 AM -- 目前的完成情况: 摘要(forwar;已完成初稿) 目录(admin;已完成初稿,个人感觉有些地方没翻好和协商好,需要进一步商榷) 第一章 简介 -4页 (admin,已完成初稿) 第二章 资源描述语句 -24页 (forwar,即将完成) 第三章 RDF的XML语法 -19页 (admin,正在翻译中,3.1已完成) 第四章 其它RDF能力特征 -24页(orangebench,已完成初稿) 第五章 定义RDF 词汇 RDF Schema -19页(trevol,已完成初稿) 第六章 RDF应用领域 -31页(尚缺 ) 第七章 RDF规范相关文档 - 2页 附录 11页(尚缺 )
|
-- 作者:admin -- 发布时间:7/22/2004 12:06:00 PM -- 我先报名翻译附录 :-) |
-- 作者:nybon -- 发布时间:7/22/2004 4:27:00 PM -- 上面到6.3是吗,那我就6.4吧 |
-- 作者:forwar -- 发布时间:7/22/2004 5:00:00 PM -- Blank nodes provide one way to do this. For each n-ary relationship, one of the participants is chosen as the subject of the relationship (John in this case), and a blank node is created to represent the rest of the relationship (John's address in this case). The remaining participants in the relationship (such as the city in this example) are then represented as separate properties of the new resource represented by the blank node. 翻成:空节点提供了一种完成这个任务的方法:对于每一个N元关系,选择其中的一元(participant)作为这个关系的主体(比如John),创建一个空节点来描述其余的关联关系(比如John's address),这个N元关系的其他元(比如city)则被描述成由空节点描述的新资源的各个单独的属性。 |
-- 作者:orangebench -- 发布时间:7/22/2004 5:03:00 PM -- participant 翻译的不错啊,元 挺好的 ;-) 我翻译的4。4 节也是讲n元关系的。
|
-- 作者:forwar -- 发布时间:7/22/2004 5:15:00 PM -- 回帖速度够快,汗... ----------------------------- 好的,那我以后就照这翻了. |
-- 作者:nybon -- 发布时间:7/22/2004 7:13:00 PM -- 那个wiki页面的有的章节的"编辑"的链接似乎有点问题,像6.5 CIM/XML我点编辑的话链接到的是6.2 PRISM的编辑,而点6.7 section(不是标题的那个)的编辑才会链接到6.5的编辑,is there any problem or I made some mistake?? |
-- 作者:orangebench -- 发布时间:7/22/2004 7:23:00 PM -- 一直有这问题,也没有得到解决 ;-) 就只好后移两位,就是正确的链接了,将就一下了。
|
-- 作者:trevol -- 发布时间:7/22/2004 9:46:00 PM -- 欢迎 nybon 加入,目前第六章分配情况如下: 6. RDF 应用领域 6.3 XPackage 4页 (已经分配给 weekend) 6.5 CIM/XML 4页 (已分配给 nybon) [此贴子已经被orangebench于2004-7-23 2:34:25编辑过]
|
-- 作者:nybon -- 发布时间:7/23/2004 12:52:00 AM -- 哦,这样的呀,那就6.5^_^ |
-- 作者:nybon -- 发布时间:7/23/2004 12:58:00 AM --
呃,也算解决了那
|
-- 作者:Candy -- 发布时间:7/23/2004 11:05:00 AM -- 第三章中的“RDF URIrefs”该怎么翻译啊? URIrefs需要翻译出来嘛? |
-- 作者:nybon -- 发布时间:7/23/2004 12:17:00 PM -- 嗯,张维明有出一本书叫《语义信息模型及应用》,里面很多内容都是翻译RDF Model and Syntax Specification的,不知道有没有翻到这个URIref,书现在不在我手头,应该别人也有的吧,看看就知道了. |
-- 作者:trevol -- 发布时间:7/23/2004 1:07:00 PM --
URIref 暂时先不翻译了,最后统稿的时候,在同一一下。。。 |
-- 作者:Ontoweb -- 发布时间:7/23/2004 4:21:00 PM -- 还有吗?我注册的是storm,看大家都那么辛苦,真想分担些,虽然时间紧。 |
-- 作者:trevol -- 发布时间:7/23/2004 5:03:00 PM --
好呀,非常欢迎! 6。1 节 有关 dublin Core 应用的那块内容 您翻译一下,可以吗? 谢谢 |
-- 作者:admin -- 发布时间:7/23/2004 5:18:00 PM -- 那是因为在某个标题(即== heading ==)后出现了多余字符 (== heading == 后面不应出现字符,必须另起一行) 遇到这种情况,需要点击下一个[编辑],再不行,就再下一个。
|
-- 作者:Ontoweb -- 发布时间:7/23/2004 5:25:00 PM -- 好的, |
-- 作者:Ontoweb -- 发布时间:7/23/2004 6:54:00 PM -- 6.1 Dublin Core Metadata Initiative 都柏林核心元数据倡议
都柏林核心元素已广泛地用于文件因特网资源(都柏林核心创造者元素早期的例子)。 都柏林核心当前的元素在都柏林核心元数据元素集中给出了定义,版本1.1: 参考描述[ DC ]。且包含下列的属性的定义: |
-- 作者:forwar -- 发布时间:7/23/2004 9:25:00 PM -- 2.3,2.5节已经翻译完了,因为这两天房东家的交换机坏了,暂时无法传上来,过两天修好了就行了。第二章还差2.4节初稿就全部完工了,正在翻译中...... ---------------------------------------------------------------------------------------- 还有,orangebench,我这两天上不了网,每天睡的都很早...呵呵~~ |
-- 作者:orangebench -- 发布时间:7/23/2004 9:49:00 PM -- 呵呵,令人振奋!月底基本可以出初稿了! 最新动态: 摘要(forwar;已完成初稿) 6.1 都柏林核心元数据计划 5页 --Ontoweb
第七章 RDF规范相关文档 - 2页 |
-- 作者:Ontoweb -- 发布时间:7/24/2004 10:04:00 AM -- Initiative 译成什么好呢? 倡议 ? 计划? 翻译中感觉还有些词汇需要统一起来,这恐怕要劳驾Admin,trevol,orangebench....几位了, 6.1节初稿已经提交,请校对!! |
-- 作者:orangebench -- 发布时间:7/24/2004 10:40:00 AM -- 呵呵,这么快! 我觉得 Initiative 翻译为倡议 挺好的.
|
-- 作者:forwar -- 发布时间:7/24/2004 7:25:00 PM --
现在初稿完成的有没有60%了?胜利就在眼前!!! |
-- 作者:admin -- 发布时间:7/24/2004 8:08:00 PM -- 同意斑竹的看法
|
-- 作者:admin -- 发布时间:7/26/2004 3:37:00 PM -- 这几个单词如何翻译 3.3 RDF/XML Summary The examples above have illustrated some of the basic ideas behind the RDF/XML syntax. These examples provide enough information to begin writing useful RDF/XML. A more thorough discussion of the principles behind the modeling of RDF statements in XML (known as striping), together with a presentation of the other RDF/XML abbreviations available, and other details and examples about writing RDF in XML, is given in the (normative) RDF/XML Syntax Specification [RDF-SYNTAX].
|
-- 作者:orangebench -- 发布时间:7/26/2004 4:06:00 PM -- Consider a graph of nodes, each with a type (ie. category or 'class'), and each having a bunch of named properties (relationships) connecting it to other nodes, which might be simply string-y values, or further nodes that are themselves at the sharp and/or blunt ends of various other edges in the graph. We need to create XML elements (possibly with associated attributes) that stand for these nodes and arcs. RDF's convention for doing this is called striped because, as you look at the XML element nesting structure, elements alternately represent nodes and edges. This is RDF striping. Understanding this basic representational convention is all you need to understand most RDF/XML examples you'll encounter. Understanding the Striped RDF/XML Syntax 根据上面的解释,striping 也许可以翻译为 “斑纹”语法 ? 有没有更好的翻译?
|
-- 作者:forwar -- 发布时间:7/27/2004 12:14:00 AM -- 二等兵forwar报告:第二章的全部内容已经翻译完毕,请检阅。 ------------------------------------ 还有一些问题如下: 1.validity 翻成合法性?合乎规则性?有效性? 2.lexical space 翻成词汇空间?词汇域?value space 值域?,我翻成了值域,行不行? 3.A lexical-to-value mapping from the lexical space to the value space. 4.the built-in XML Schema datatypes 翻成“XML模型内建数据类型”行不行?
|
-- 作者:orangebench -- 发布时间:7/27/2004 12:22:00 AM -- 呵呵,不是二等兵,应该是 敢死队 ;-)
|
-- 作者:forwar -- 发布时间:7/27/2004 12:29:00 AM -- 多谢orangebench的指点!现在正在对译文进行修改。 |
-- 作者:trevol -- 发布时间:7/27/2004 9:58:00 AM --
|
-- 作者:trevol -- 发布时间:7/27/2004 10:11:00 AM --
|
-- 作者:nybon -- 发布时间:7/27/2004 4:20:00 PM -- An excellent discussion of CIM/XML can be found in [http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#ref-devos [DWZ01]]. [NB: This power industry CIM should not be confused with the CIM developed by the [http://www.dmtf.org/ Distributed Management Task Force] for representing management information for distributed software, network, and enterprise environments. The DMTF CIM also has an XML representation, but does not currently use RDF, although independent research is underway in that direction.] power system These extensions support the description of inverse roles and multiplicity (cardinality) constraints describing how many instances of a given property are allowed for a given resource (allowable values for a multiplicity declaration are zero-or-one, exactly-one, zero-or-more, one-or-more). 红色的地方怎么译呀都? NB是什么意思? power system是翻成电力系统还是能源系统?感觉字面来看是能源,不过那边讲的似乎都是电力有关的。 inverse role是什么意思? |
-- 作者:nybon -- 发布时间:7/27/2004 4:28:00 PM -- Finally, CIM/XML also illustrates an important fact for those looking for additional examples of "RDF in the Field": sometimes languages are described as "XML" languages, or systems are described as using "XML", and the "XML" they are actually using is RDF/XML, i.e., they are RDF applications. RDF in the field怎么翻又?? |
-- 作者:trevol -- 发布时间:7/27/2004 5:17:00 PM --
NB [I]N.B. n : a Latin phrase (or its abbreviation) used to indicate that special attention should be paid to something; "the margins of his book were generously supplied with pencilled NBs" [syn: nota bene, NB, N.B.] 译成:“注:”就可以了。 POWER SYSTEM: 建议 译为-电力系统; INVERSE ROLE: 建议暂时译为: 反向角色; CARDINALITY:建议译为:基数;[/I] |
-- 作者:trevol -- 发布时间:7/27/2004 5:21:00 PM --
RDF in the field 可以翻译为 RDF在领域中的应用 |
-- 作者:猫小 -- 发布时间:7/27/2004 6:03:00 PM -- 感觉这里气氛很好,并且很感谢该站的资源 希望W3C在中国的发展能从这里走向未来 |
-- 作者:nybon -- 发布时间:7/28/2004 8:34:00 AM -- ok,知道了 |
-- 作者:orangebench -- 发布时间:7/28/2004 9:46:00 PM -- 进度报告: 已初步校对第1节和2.1节,其中2.1节中的关于URI,URIref的部分,请admin校对。 |
-- 作者:admin -- 发布时间:7/28/2004 10:25:00 PM -- 好的~~ |
-- 作者:nybon -- 发布时间:7/29/2004 10:50:00 AM -- 6.5 基本完成,已经提交上去了,也请admin校对帮助修改一下^_^,辛苦了
|
-- 作者:admin -- 发布时间:7/29/2004 11:47:00 AM -- 好的 |
-- 作者:orangebench -- 发布时间:7/29/2004 9:20:00 PM -- 2。2正在校对中,由于比较长,需要好几天,我会在校对完后再更新wiki. |
-- 作者:orangebench -- 发布时间:7/29/2004 9:26:00 PM -- To Ontoweb, nybon: 如果有时间的话,你们还可以继续翻译第6节的其他部分哦。 ;-) |
-- 作者:Ontoweb -- 发布时间:7/29/2004 10:24:00 PM -- 如果有空一定会的,但这几天正在苦闷的忙着 |
-- 作者:forwar -- 发布时间:7/30/2004 12:57:00 AM -- 我看第六节的6.2 PRISM部分没分配,那我来翻译一下吧。 -------------------------------------------------------------------------------------------- 发表一个陈述先:PRISM我不懂...呵呵,翻这段要不要有深入的理论基础,如果要的话,恐怕我翻不来,那我先试试吧。房东家的交换机出问题了,所以最近可能不能频繁的上网,和大家交流起来恐怕会有些不方便,不过我会定时来这里看看的,了解一下最新的动态(admin,不会收我门票吧?哈哈~)。 |
-- 作者:orangebench -- 发布时间:7/30/2004 10:26:00 AM -- 昨晚加班,2.2节已经校对完了。本来以为要好几天,但发现你翻译的很好,就迅速解决了 ;-) 那6.2就交给你了 ;-)
|
-- 作者:forwar -- 发布时间:7/30/2004 4:38:00 PM --
保证按时完成任务!
|
-- 作者:forwar -- 发布时间:7/30/2004 11:43:00 PM -- 任务已经完成了,由于家里机器不能上网,现在不能更新6.2节,想明天就能上网了。到时候回传上去,另外,必然的,还有一些问题要和大家讨论。问题比较多,请各位做好心理准备,哈哈哈~~~ |
-- 作者:forwar -- 发布时间:7/31/2004 11:44:00 AM -- 又是一个阳光明媚的清晨...好像已经快12点了... ------------------------------------ 翻译6.2节的过程中,遇到的问题如下: 1.Publishing Requirements for Industry Standard Metadata [PRISM]出版业必需的行业元数据标准? 2.end-to-end metadata 怎么翻? 3.Rights Tracking 翻成 权限追踪 行不行? 4.PRISM Controlled Vocabulary(pcv) 翻成 PRISM限制性词汇集 行不行? 5.Digital Rights Management 翻成 数字权限管理 行不行? 6.Example 36 says that the photographer for the Corfu image was employee 3845, better known as John Peterson. It also says that the geographic coverage of the photo is Greece. It does so by providing, not just a code from a controlled vocabulary, but a cached version of the information for that term in the vocabulary. 这段话我是这样翻的: 例36说明了图片“Corfu”的摄影师员工号是“3845”(employee 3845),就是人们熟知的John Peterson(better known as John Peterson)。它还说明了图片的出处在地理学上是希腊。它能做到这些,不仅仅是因为提供了一个取自限制性词汇集的代码,还提供了关于词汇集中术语信息的一个隐藏的解释。 行不行? ------------------------------------
|
-- 作者:admin -- 发布时间:7/31/2004 6:12:00 PM -- 关于若干需要统一的地方(下面是我正在使用的方案,欢迎提出不同意见,并确定最终方案): Section 2 -> 第2节
[此贴子已经被作者于2004-8-9 12:19:42编辑过]
|
-- 作者:admin -- 发布时间:7/31/2004 6:35:00 PM -- 不了解上下文,仅供参考 :-)
|
-- 作者:forwar -- 发布时间:8/1/2004 -- employee 3845,员工 3845,我猜是这个意思,于是就这样写了;图片上的画面所在地理位置为希腊,这一句我翻错了,这句没理解好。现在看看“还说明了图片的地理出处在地理学上是希腊”翻的真搞笑~~哈哈哈~~ |
-- 作者:trevol -- 发布时间:8/1/2004 10:47:00 AM --
|
-- 作者:admin -- 发布时间:8/1/2004 11:05:00 AM -- 什么叫 end-to-end metadata ? 从一个应用系统到另一个应用系统的元数据? |
-- 作者:trevol -- 发布时间:8/1/2004 12:16:00 PM --
End-to-end metadata: Most published content already has metadata created for it. Unfortunately, when content moves between systems, the metadata is frequently discarded, only to be re-created later in the production process at considerable expense. PRISM aims to reduce this problem by providing a specification that can be used in multiple stages in the content production pipeline. An important feature of the PRISM specification is its use of other existing specifications. Rather than create an entirely new thing, the group decided to use existing specifications as much as possible, and only define new things where needed. For this reason, the PRISM specification uses XML, RDF, Dublin Core, and well as various ISO formats and vocabularies. END TO END metadata 可能是可以被多个应用(END)所共用和重用的元数据吧。。。 |
-- 作者:forwar -- 发布时间:8/1/2004 5:15:00 PM -- 我已经参照回帖将原文有出入的地方改过来了。又长了不少的见识...^_^ |
-- 作者:trevol -- 发布时间:8/1/2004 7:06:00 PM -- WIKI怎么那么慢啊? 5.1 和 5。2 都校完了。。。明天贴上去。 第六章还有哪些小节没有人翻呀? 同志们加把劲,奥运会前一定要把初稿搞定啊!!! |
-- 作者:forwar -- 发布时间:8/1/2004 7:28:00 PM -- 呵呵,向雅典奥运会献礼? |
-- 作者:npubird -- 发布时间:8/1/2004 8:32:00 PM -- 第4章我校对完。请大家检查。 |
-- 作者:orangebench -- 发布时间:8/1/2004 8:46:00 PM -- 谢谢npubird的辛苦劳动!
|
-- 作者:weekend -- 发布时间:8/1/2004 10:24:00 PM -- 各位,6.3 翻译了.亲大家去帮忙修改一下. 因为是第一次翻译所有很多都不懂. 本来可以更好的,但是我有毕业设计在身, 翻得不是很好.见谅. |
-- 作者:nybon -- 发布时间:8/2/2004 10:39:00 AM -- 嗯,出去了两天才回来.现在还算满空的,主要时间是看书,要是还需要人手的话我可以继续的,就是不知道我翻的质量怎么样呢,哪里不好的话我再翻的话也可以注意一下.章节的话就6.6吧^_^,找个少点的 |
-- 作者:orangebench -- 发布时间:8/2/2004 10:53:00 AM -- 我大概看了一下你翻译的6.5, 感觉翻译的很好,可以继续哦。
|
-- 作者:nybon -- 发布时间:8/2/2004 12:00:00 PM -- ok,那我继续6.6吧就 |
-- 作者:orangebench -- 发布时间:8/2/2004 12:10:00 PM -- Ok! 2.3, 2.4 校对完毕, forwar的翻译很不错, 非常感谢! 吃饭去了..... |
-- 作者:nybon -- 发布时间:8/2/2004 12:31:00 PM -- 为什么那个翻译的网页打不开呢,显示出来一串乱码 "鏁版嵁搴撴寚浠よ娉曢敊璇? 杩欏彲鑳芥槸鐢变簬闈炴硶鎼滅储鎸囦护鎵寮曡捣鐨?瑙?$5), 涔熷彲鑳芥槸鐢变簬杞欢鑷韩鐨勯敊璇墍寮曡捣銆? 鏈鍚庝竴娆℃暟鎹簱鎸囦护鏄細 SELECT user_name,user_password,user_newpassword,user_email,user_options,user_rights,user_touched FROM user WHERE user_id=67 鏉ヨ嚜浜庡嚱鏁?"User::loadFromDatabase"銆? MySQL杩斿洖閿欒 "1016: Can't open file: 'user.MYD'. (errno: 145)"銆?" ??
|
-- 作者:orangebench -- 发布时间:8/2/2004 12:43:00 PM -- 空间不够了,admin正在申请更多空间....
|
-- 作者:forwar -- 发布时间:8/2/2004 1:29:00 PM --
还谢个啥,真是太客气了,呵呵。。。 |
-- 作者:anonymous -- 发布时间:8/3/2004 3:04:00 PM -- 呵呵,我来晚了? |
-- 作者:Kevin-20040804 -- 发布时间:8/4/2004 3:32:00 PM -- 真的很羡慕为这里做出贡献的兄弟姐妹们,很感谢你们,虽然我没有权力和资格代表其它人,但这份感谢是我对议员的一种尊重的言语表达。 |
-- 作者:orangebench -- 发布时间:8/4/2004 3:46:00 PM -- 谢谢! 我们后面还会继续组织翻译RDF,OWL的其他规范, 欢迎参与!
|
-- 作者:trevol -- 发布时间:8/6/2004 10:12:00 AM -- 新版WIKI修好了。。。大家继续努力呀! 奥运前搞定,算是献礼。。。更重要的是我们可以专心看奥运了。。。 |
-- 作者:trevol -- 发布时间:8/6/2004 11:06:00 AM --
nybon,6。6 翻译得怎么样了。。。呵呵。。。好几天没有见你了哦。。。 |
-- 作者:forwar -- 发布时间:8/6/2004 12:23:00 PM -- 新的WIKI好清爽~~~忍不住想多看两眼~~~ |
-- 作者:orangebench -- 发布时间:8/6/2004 4:35:00 PM -- 我来翻译第7章,很少,才2页多。 |
-- 作者:trevol -- 发布时间:8/6/2004 4:38:00 PM --
强!榜样!
|
-- 作者:orangebench -- 发布时间:8/6/2004 5:45:00 PM -- 最后一句: 不知道如何翻译好。 ===7.2 Test Cases=== The test cases are not a complete specification of RDF, and are not intended to take precedence over the other specification documents. However, they are intended to illustrate the intent of the RDF Core Working Group with respect to the design of RDF, and developers may find these test cases helpful should the wording of the specifications be unclear on any point of detail.<BR> 这些测试用例并不是一个RDF的完全规范, 以不优先于其他规范文档. 然而, 他们是用以说明RDF核心工作组对RDF的设计用途, 发现这些测试用例有用的开发人员应该注意到这个(测试用例)规范从任何详细程度上来说都是不够清晰的. |
-- 作者:admin -- 发布时间:8/6/2004 6:39:00 PM -- 最后一句感觉需要改动了一下 :-)
|
-- 作者:orangebench -- 发布时间:8/6/2004 6:41:00 PM -- 你这样一说,意思就清楚了. 我马上改过来! //admire
|
-- 作者:admin -- 发布时间:8/6/2004 8:00:00 PM -- 可以等到下次更新时一起更新 怪我把主题做得太长了,现在的RDF Primer已经有500K了,每更新一次,数据库就增大500K,不仅费空间,而且打开速度也很慢,, 今后的翻译会考虑每个主题的长度不超过50K。
|
-- 作者:xujcan -- 发布时间:8/7/2004 3:01:00 PM -- 现在申请加入这个计划还完吗?我可以付出的时间是从现在到8月底! |
-- 作者:admin -- 发布时间:8/7/2004 6:43:00 PM -- 6.7还没人翻,你可以先翻译这一章。 如果有时间可以REVIEW别人的部分。
|
-- 作者:orangebench -- 发布时间:8/7/2004 7:02:00 PM -- 非常欢迎! 除了可以翻译6.7 和review 其他人翻译的外, Wiki上还有相关的规范,如RDF concept and abstract syntax, owl overview都可以翻译.
|
-- 作者:Spark -- 发布时间:8/7/2004 11:25:00 PM -- 3. -》权限跟踪 注:版权是copyright,是right的子集 :) 5. -》数字权限管理 理由同上。 相信我,这个说法是通用的。
|
-- 作者:nybon -- 发布时间:8/8/2004 12:20:00 AM --
^_^,去同学那里玩了两天才回来.翻的差不多了,不过有写地方不会翻, question list: The objective of the Gene Ontology (GO) Consortium [GO] is to provide controlled vocabularies to describe specific aspects of gene products. controlled要怎么翻?受控制的词汇表吗?我不大清楚这里是什么意思 The three organizing principles of the GO are molecular function, biological process, and cellular component.
|
-- 作者:nybon -- 发布时间:8/8/2004 12:47:00 AM -- This tag represents the relationship "GO:0016209 isa GO:0003674", or, in English, "Antioxidant is a molecular function." 纯粹的一个翻译问题,它这里说"in English",我后面应该翻还是不翻呢? 译文1: 该标记表示了"GO:0016209 isa GO:0003674"这一关系,或者用英语来说,表示了"抗氧化剂是一个分子功能" 译文2: 该标记表示了"GO:0016209 isa GO:0003674"这一关系,或者用英语来说,表示了"Antioxidant is a molecular function" |
-- 作者:admin -- 发布时间:8/8/2004 12:54:00 AM -- 请qinpu进来看一下
|
-- 作者:nybon -- 发布时间:8/8/2004 1:07:00 AM -- go:association can have both go:evidence, which holds a go:dbxref to the evidence supporting the association, and a go:gene_product, which contains the gene symbol and go:dbxref. 这种简单的词我都翻不来,应该翻成什么比较妥当呢? ISS means "inferred from sequence similarity [with <database:sequence_id>]" 上面这些词术语又是什么呢? since the nesting of other elements within these elements does not conform to the alternate node/predicate arc "stripes" described in Sections 2.1 and 2.2 of [RDF-SYNTAX]. 这个前面是怎么译的来着?呀,好多不懂
[此贴子已经被作者于2004-8-8 10:57:54编辑过]
|
-- 作者:xujcan -- 发布时间:8/8/2004 8:58:00 PM -- 好的,我一定尽快完成。^_^ |
-- 作者:trevol -- 发布时间:8/9/2004 8:39:00 AM --
controlled vocabulary ->可译成 “受控词表” ,言下之意就是词表是某个权威组织开发和维护的。 那三个专业词汇 MOLECULAR FUNCTION、BIOLOGICAL PROCESS, CELLULAR COMPONENT 翻译得应该不错。具体可以参考:http://www.bioclub.org/modules/xoopsfaq/index.php?cat_id=2 |
-- 作者:trevol -- 发布时间:8/9/2004 8:41:00 AM --
类似这样的情况,可以在英文句子的后面加上括号,标以中文翻译。 |
-- 作者:admin -- 发布时间:8/9/2004 3:12:00 PM -- [B] 是不是可以考虑翻译的 术语 和 格式 统一 了?[/B] 建议在Wiki中进行讨论~~~ 关于术语清访问(如有一个术语多个候选翻译,则使用第一个) 有把握的可以直接Wiki上修改(点击顶部的edit); |
-- 作者:trevol -- 发布时间:8/9/2004 3:20:00 PM --
在REVIEW第三章的时候,发现文中多次同时出现 ATTRIBUTE 和 PROPERTY两个词。如果两个词都翻译为属性的话,可能会丢失一些信息。 ATTRIBUTE 确实是在从XML语法层面上谈问题;而RDF/S中,每当从RDF数据模型层面上讨论问题的时候,都采用用PROPERTY一词。因此,笼统地将两个词都译为“属性”并不合适。毕竟这两个词在RDF PRIMER中都出现,而且第三章尤其频繁。 建议在翻译中区分这两个词,ATTRIBUTE 翻译为-“属性”;PROPERTY 翻译为“特性”。 请大家继续发表意见。。。谢谢! |
-- 作者:admin -- 发布时间:8/9/2004 4:29:00 PM -- 这的确是老外给咱们出的一个难题~~~~~ trevol大哥说的是的确存在的问题。 但是总觉得特性,有点怪怪的感觉,毕竟我们从OO,UML都习惯了说,为一个类声明/设置/添加一个属性;一个Person的实例/个体具有属性Weight等等。要改口的确有些困难 :-)
|
-- 作者:orangebench -- 发布时间:8/9/2004 4:46:00 PM -- 准确地说,attribute在第3节中是指XML的属性(attribute node)节点,而 property是RDF的属性(谓词)。 特性 我也觉得有点难以接受, 总觉得怪怪的。 所以,我的建议是:如果通过上下文不会混淆,都翻译为属性,可能混淆的话,attribute 翻译为XML属性(节点),property翻译为RDF属性 此外,在attribute第一次出现的时候, 注明一下它的意思:即XML属性节点。
|
-- 作者:trevol -- 发布时间:8/9/2004 8:56:00 PM -- RDF PRIMER 到目前为止只剩下了6.4、6.6 、6。7三个小节,尚未完成。同志们加把劲!争取明天集中精力把这三个小节结束,具体任务分配: 6.4-----TREVOL 翻译完成后,全面初审,我们争取在13号前发布意见征求版!
|
-- 作者:orangebench -- 发布时间:8/9/2004 11:06:00 PM -- 谁用过CC/PP吗?这段话怎么理解? A CC/PP ''vocabulary'' defines specific components and their attributes. CC/PP however, does not define such vocabularies. Instead, vocabularies are defined by other organizations or applications (as described below). |
-- 作者:orangebench -- 发布时间:8/9/2004 11:57:00 PM -- 这个profile怎么翻译? An instance of a CC/PP vocabulary is called a ''profile''. 我翻译的是:特征文件。 有没有更好的? 谢谢! |
-- 作者:orangebench -- 发布时间:8/10/2004 12:41:00 AM -- 翻译完6.7,越发觉得RDF是个好东西! Yeah! 6。7已提交,请reviewer做些修改。 |
-- 作者:trevol -- 发布时间:8/10/2004 11:53:00 AM -- RDF PRIMER 初稿已经翻译完毕!感谢一起奋战了将近一个月的兄弟姐妹们,大家辛苦了!庆祝一下。。。。。 呵呵,抓紧时间完成第一遍REVIEW.....,力争13号提出增求意见稿. --------------------------------------------------------------------------------- |
-- 作者:orangebench -- 发布时间:8/10/2004 12:12:00 PM -- Cheers!
|
-- 作者:nybon -- 发布时间:8/10/2004 12:21:00 PM -- 6.6节已经提交,不过满多东西不会翻的,someone helps me to do a review and modification. |
-- 作者:forwar -- 发布时间:8/10/2004 11:03:00 PM -- 终于都搞定了,可喜可贺呀! 什么时候REVIEW结束呢? 这个入门书要以什么样的形式流传呢?电子书么? |
-- 作者:orangebench -- 发布时间:8/11/2004 12:10:00 AM -- 6.2 "hits the stands" 怎么翻译? typically they all go live at the time the magazine hits the stands. |
-- 作者:trevol -- 发布时间:8/11/2004 9:13:00 AM --
hit the stands ----------翻译为“杂志发行”应该是正确的。可以用magazine hits the stands 到GOOGLE上搜索一下。 |
-- 作者:trevol -- 发布时间:8/11/2004 10:24:00 AM -- 第三章也已经完成了初步的REVIEW..... |
-- 作者:trevol -- 发布时间:8/11/2004 10:48:00 AM --
当杂志发行时,其内容也就开始上线了。 |
-- 作者:orangebench -- 发布时间:8/11/2004 11:22:00 PM -- 6.3 weekend 的翻译非常好,我几乎没做改动。谢谢! |
-- 作者:orangebench -- 发布时间:8/12/2004 12:47:00 AM -- 刚看了6.5的翻译,由于牵涉到电力系统,难度比较大,但还是翻译的很好,我也几乎没做改动。谢谢nybon! |
-- 作者:nybon -- 发布时间:8/12/2004 8:35:00 AM -- ^_^,6.6我就翻不来了,像金山快译干的一样,赶快谁改一下吧 |
-- 作者:forwar -- 发布时间:8/12/2004 10:28:00 AM --
这是我翻的,当时翻的不恰当,如果这样:当杂志发行时,其内容也跟着公诸于世了。行不行??
|
-- 作者:forwar -- 发布时间:8/12/2004 10:34:00 AM -- 刚才又看了一遍6.2PRISM。“而把它许可给一个叫LexisNexis (http://www.lexisnexis.com/) 的聚集软件则是另外一个例子。”这句话中的“聚集软件”对么?
|
-- 作者:orangebench -- 发布时间:8/12/2004 11:06:00 AM -- 英文是 aggregator, RSS中常有RSS Aggregator, 就是RSS 聚集软件的意思。也学翻译 为“聚合器”更好些。
|
-- 作者:orangebench -- 发布时间:8/12/2004 2:53:00 PM -- 6.6 刚看了一遍,感觉也翻译的很好,很通顺。 感觉nybon同学的文笔很不错,强烈要求nybon在有时间的前提下review其他的章节。 ;-) 从6。5 到6。6 到其他章节,原来我的贪心 ;-)
|
-- 作者:Ontoweb -- 发布时间:8/12/2004 9:40:00 PM -- 可喜可贺,期待着看到大家辛勤劳动后的收获 |
-- 作者:trevol -- 发布时间:8/13/2004 8:48:00 AM -- the RSS 1.0 author can provide large amounts of metadata and handling instructions to the recipient of the file. 不是很了解RSS1.0, 这话怎么译啊 ? |
-- 作者:forwar -- 发布时间:8/16/2004 1:50:00 AM -- 现在天天没事做,真想念前几个星期日夜加班加点翻译的充实啊! |
-- 作者:qinpu -- 发布时间:8/21/2004 6:16:00 AM -- 我也觉得这样比较好,要么宁愿不译或者加上注释,要不然“特性”会让很多在搞SW的研究者更混淆。
|
-- 作者:qinpu -- 发布时间:8/21/2004 6:31:00 AM --
这样可以吗? |
-- 作者:qinpu -- 发布时间:8/21/2004 6:34:00 AM -- 唉,给版主添乱了,惭愧惭愧 :( 刚才没留意应该集中回复到这一贴,另开了一个集中回复帖子了 http://bbs.w3china.org/dispbbs.asp?boardid=2&id=9488&star=1#9488 再有时间就去wiki直接看看了,等忙完这几天。 |
-- 作者:trevol -- 发布时间:8/21/2004 7:01:00 PM --
对 "handling instructions to the recipient of the file" 的含义还是不理解。。 |
-- 作者:qinpu -- 发布时间:8/21/2004 9:59:00 PM --
是我翻译的不太准,recipient 和handling好像翻错了,这样看看行不行(意译):
|
-- 作者:hjx_221 -- 发布时间:8/30/2004 9:07:00 PM -- 学习之中…… |
-- 作者:txx5890 -- 发布时间:8/30/2004 10:53:00 PM -- 我愿意加入翻译的行列 |
-- 作者:shenmingfei2004 -- 发布时间:9/9/2004 1:35:00 AM -- 不错 |
-- 作者:weekend -- 发布时间:9/16/2004 6:06:00 PM --
谢谢.这是第一次参加翻译.还真想看看我那些地方被改了,然后就知道自己哪里不足了.如果再有那样的机会,我想我也会参加的. |
W 3 C h i n a ( since 2003 ) 旗 下 站 点 苏ICP备05006046号《全国人大常委会关于维护互联网安全的决定》《计算机信息网络国际联网安全保护管理办法》 |
1,312.500ms |