原站英文机器转录 + 本地中文机器初译(未完成逐句听审) 原作者及许可见 attribution.txt;中文由九天新增,不代表原作者认可。 00:00:10.610 EN: Welcome to the Knowledge Engineering and Semantic Web Lecture. So last week, we started talking about OWL. And today, we want to continue some remaining bits and pieces about the web ontology language. 中文初译: 欢迎来到知识工程和语义网络讲座。 上周,我们开始讨论“ OWL ” 。 而今天,我们要继续一些关于网络文学语言的剩余部分。 00:00:26.490 EN: Let's maybe briefly go through what we discussed last week. So OWL builds on top of RDF schema and on RDF. So all OWL ontologies are also RDF files or can be represented in RDF. 中文初译: 我们或许可以简短地回顾一下我们上周讨论过的事情。所以“OWL”建在了“RDF”的模型和“RDF”之上。所以所有的“OWL”内涵也是“RDF”的文件,或者可以在“RDF”中代表。 00:00:45.170 EN: Ontologies is a term which already originated from philosophy. So it's well-known for many decades. Actually, one of the first ontology projects I did, I did with the Protestant Church. 中文初译: 原教旨学是一个已经源于哲学的术语。因此,它数十年来都是众所周知的。实际上,我首先做的最初一项原教旨学项目之一,就是与新教教会合作。 00:00:59.450 EN: And they were very excited about using ontologies. And then it became quite popular in computer science. Increasingly, it started with a definition by Tom Cooper in 1993. 中文初译: 他们对于使用本体论非常兴奋。然后计算机科学中它变得相当流行。越来越多的人开始于1993年汤姆·库珀的定义。 00:01:15.790 EN: But since then, it's increasingly gained more popularity for representing knowledge. So it's a standard by W3C, which we discussed. 中文初译: 但从那以后,它越来越受人欢迎 来代表知识。所以这是W3C的标准,我们讨论过。 00:01:29.310 EN: There are some shortcomings of RDF and RDF schema, which OWL addresses, especially when you want to represent more complex knowledge. 中文初译: “RDF”和“RDF”的模型有一些缺点,“OWL”处理这些缺点,特别是当你想代表更复杂的知识时。 00:01:39.030 EN: And OWL also builds on description logics. And there is also this Manchester syntax, which you should maybe be able to read a bit. 中文初译: “OWL”还建立在描述逻辑上。还有曼彻斯特语法, 你可以读一点。 00:01:50.630 EN: But this is just another syntax. And everything can be also represented in RDF, in Turtle, for example, or other RDF serializations. 中文初译: 但这只是另一种语法。所有的东西都可以在“RDF ” ( RDF)中,比如“Turtle ” ( Turtle ) 或其他“RDF ” ( RDF ) 序列中出现。 00:02:01.250 EN: And OWL documents usually have a header with some prefix declarations. You can add some meta information about the ontology, for example, like comments, versioning, imports. 中文初译: “OWL”文档通常有一个带有某些前缀声明的页眉。 您可以添加一些关于本体论的元信息, 比如评论、 版本、 导入等 。 00:02:14.870 EN: There are a number of properties which are added in the OWL standard for versioning, like versioning info, prior version, backward compatibility, incompatibility, deprecated class, deprecated property, because of course ontologies are evolving. 中文初译: 在“OWL” 版本标准中添加了一些属性,例如版本信息、先前版本、后向兼容性、不兼容性、折旧等级、折旧属性等,因为本体论当然在演变。 00:02:33.030 EN: They are not fixed, but they should evolve because the domains, of course, also change. The conceptualization should be refined. 中文初译: 它们不是固定的,但是它们应该演变,因为领域当然也会改变。 概念化应当加以完善。 00:02:42.510 EN: But on the other hand, since it's a shared conceptualization, you should not or try not to break the conceptualization. 中文初译: 但另一方面,由于这是共同的概念化, 你不应该或者尽量不打破概念化。 00:02:51.210 EN: That's why it's a good practice to try to be backward compatible. So don't redefine classes differently in later versions, but introduce maybe a new class and then mark the old one as deprecated class, for example. That helps to keep things compatible. 中文初译: 这就是为什么尝试后向兼容是一个好的做法。 所以不要在以后的版本中以不同的方式重新定义班级, 而是引入一个新的班级, 然后将旧班标为折旧类, 比如说。 这有助于保持事物的兼容性。 00:03:14.750 EN: So OWL documents are sets of axioms, and different syntaxes exist there as well. But as I said, the RDF syntaxes can be used for all OWL documents, like turtle, for example. 中文初译: 所以“ OWL” 文档是一套轴法, 那里也有不同的语法。 但是正如我所说, “ RDF” 语法可以用于所有“ OWL” 文件, 比如像龟一样。 00:03:35.710 EN: And the Manchester syntax is one which is a bit more concise and easier to read and write and a bit more closer to maybe the logic viewpoint. 中文初译: 曼彻斯特语法更简洁,更便于阅读和写作, 更接近逻辑观点。 00:03:46.590 EN: So then we talked about classes, roles, and individuals. So the terminology maybe is sometimes a bit different. 中文初译: 然后我们谈论了班级、角色和个人。所以术语有时可能有点不同。 00:03:53.510 EN: Don't be confused about that. Individuals you can also call instances. Roles are also called properties. And they are defined classes and roles in the same way as we have seen that already in RDF schema. 中文初译: 不要混淆这一点。 个人也可以称之为实例。 角色也被称为属性。 它们被定义的类别和角色与我们已经在“ RDF” 模式中看到的相同。 00:04:09.610 EN: We can define domain and ranges. One new addition in OWL is that we distinguish two types of properties, object properties and data type properties. 中文初译: 我们可以定义域和范围。在“ OWL” 中新增一个新内容,就是我们区分两类属性:物体属性和数据类型属性。 00:04:21.690 EN: So object properties are used to establish links and relationships between objects, between individuals or also classes, between resources, basically, while data type properties attach data values or describe an individual with data values. 中文初译: 因此,物体属性用于在对象之间、个人之间或分类之间、资源之间、基本上在资源之间建立联系和关系,而数据类型属性则附加数据值或用数据值描述个人。 00:04:45.950 EN: And of course, domain and range can be used there as well. So the data type properties, they are called in the logic terminology concrete roles. 中文初译: 当然,域和范围也可以在那里使用。因此数据类型属性在逻辑术语中被称作具体作用。 00:04:58.590 EN: Data type property, for example, here, first name is a data type property. The domain is a person, but the range is then a data type. 中文初译: 数据类型属性,例如,这里,第一个名称是数据类型属性。域是一个人,但区域则是一个数据类型。 00:05:07.130 EN: Here in that case, a string. And then we can, of course, use these properties or roles to describe instances or individuals, like here in that example, Albert Einstein with his first name. 中文初译: 在这样的情况下,一个字符串。然后,当然,我们可以使用这些属性或角色 来描述一些事件或个人, 比如在那个例子中,艾伯特·爱因斯坦的名。 00:05:23.390 EN: Then there are different types of relationships between classes, which are here given as an overview. So we can construct new classes out of existing classes. 中文初译: 然后,各班之间有不同类型的关系,在这里作为概述。所以我们可以在现有班级中建造新的班级。 00:05:35.410 EN: That's something which we could not really do in RDF schema. So here we can define in OWL then the equivalence of classes, the disjointness of classes, the union of classes. 中文初译: 这是在“RDF”模式中我们无法真正做到的。所以在这里我们可以在“OWL”中定义班级的等同性, 班级的脱节,班级的结合。 00:05:49.410 EN: And these are class expressions which are possible in OWL. So equivalent class basically means that two classes are subclasses of each other, mutually in both directions. 中文初译: 这些是“OWL”中可能的分类表达式。所以等同的等级基本上意味着两个类别是彼此的子类, 相互向上。 00:06:03.470 EN: So here we had this example of publication and publications, which are both, which are equivalent. And that's why publications is a subclass of publication and publication is a subclass of publications. 中文初译: 因此,我们这里有出版和出版物的例子, 两者都是一样的。这就是为什么出版是出版物的一个子类,出版则是出版物的一个子类。 00:06:19.970 EN: That's basically the meaning of equivalent class. It's basically a shortcut for defining two classes as being mutual subclasses of each other. 中文初译: 这基本上就是等同阶级的含义。它基本上是一个捷径, 用来将两个等级定义为相互的子类。 00:06:31.730 EN: So subclass of we can use then disjoint with. So this is quite important because by default, individuals can belong to different, to several classes at the same time. 中文初译: 所以子类可以使用,然后与它脱钩。所以这很重要, 因为默认情况下, 个人可以同时属于不同的, 几个类。 00:06:45.170 EN: It's maybe some of you know this from object oriented programming. There is this concept of multiple inheritance that you inherit from several classes and the same is possible in OWL. 中文初译: 也许你们中有些人从目标导向的编程中知道这一点。 有很多继承的概念, 您可以从几个班级继承, 在“ OWL ” 中也可以这样。 00:06:59.590 EN: So instances individuals can belong to several classes and sometimes even implicitly. So you don't have explicitly defined a class to be or an instance, an individual to be an instance of a class, but by reasoning, by inference, applying inference rules, it becomes apparent that the only interpretation of your model, of your ontology is that an individual must belong also to a different class. 中文初译: 所以,个人可以属于几个类别,有时甚至是隐含的。所以你没有明确地定义一个类是或一个实例,一个人就是某个类的例子,但是通过推理,通过推断,运用推论规则, 很明显地,对于你的模型,对你的本体论的唯一解释是,一个人必须也属于另一个类别。 00:07:28.650 EN: And that's why it's also good practice to define classes which must be disjoint as disjoint. And that's what you see here. 中文初译: 这就是为什么也很好的做法 定义那些必须分解的类别。这就是你在这里看到的。 00:07:38.330 EN: The class faculty staff is defined to be disjoint with application. Sounds pretty clear for us, but for a reasoner, if it's not explicitly stated, it could be that there are instances which belong to faculty staff and to publication. 中文初译: 班级教职员被定义为与应用程序脱节。 对于我们来说,这听起来相当清楚,但对于一个理性者来说,如果没有明确的表述,那可能就是存在属于教职员和出版的案例。 00:07:59.990 EN: And that's why adding such axioms is a good practice. And then a reasoner can maybe determine some inconsistencies if there is no possibility that an individual can belong to these disjoint classes. 中文初译: 这就是为什么添加这样的轴心是一个好的做法。然后一个理智者也许可以确定一些不一致之处, 如果一个人不可能属于这些脱节的类别的话。 00:08:21.800 EN: Then there's this subclass reasoning. So if you have a book, for example, as a subclass of publication. So yeah, basically you can imagine classes as sets of instances of individuals, right? 中文初译: 然后是这个子类推理。所以如果你有一本书,比如说,作为出版物的子类。所以是的,基本上你可以想象 个人的一系列案例,对吧? 00:08:36.300 EN: So if you have a class person, then you have the set of people which belong to the person class. And similarly, you have a class publication and then you have, for example, books and papers which belong to the publication class. 中文初译: 所以,如果你有一个班级的人, 那么你有一组属于人类的人。同样,你有一个班级的出版, 然后,比如说,你的书和论文 属于出版班。 00:08:52.260 EN: And if they are not defined to be disjoint, it could be that a person also becomes a publication for some reason. 中文初译: 如果它们没有被界定为脱节,那么可能是由于某种原因某人也成为了出版物。 00:09:02.180 EN: For example, if you later add more axioms to your ontology, for example, this all value or some values from public restrictions, which we discussed later or last week already, then a reasoner might infer new knowledge and he might infer that some author also is a publication because you maybe made some mistake in the representation, right? 中文初译: 例如,如果你后来在你的本体论上增加更多的轴心,例如,这些来自公共限制的所有价值或某些价值,我们已在晚些时候或上周讨论过,那么一个理智者可能会推断出新的知识,而且他可能推论一些作者也是一份出版物,因为你也许在表述中犯了错误,对吧? 00:09:32.820 EN: So this implicit information has the result that you might make some mistake. For example, I can give you an example. 中文初译: 因此,这个隐含信息的结果是 你可能会犯一些错误。例如,我可以举一个例子给你。 00:09:42.600 EN: There is the schema.org vocabulary, which I've shown you. And there is, for example, the class point of interest. 中文初译: 我给你们看过Schema.org的词汇表。例如,阶级利益。 00:09:51.380 EN: And the class point of interest has a phone number attached. And then there are subclasses of point of interest. 中文初译: 阶级利益点附有一个电话号码。然后有次类利益点。 00:09:58.620 EN: And so the domain of has phone number is a point of interest. And then there are some subclasses defined and there is some subclass, for example, mountain, which is one specific type of point of interest. 中文初译: 因此,拥有电话号码的域是一个感兴趣的点。 然后有一些子类被定义了, 还有一些子类,例如山, 这是一种特定的感兴趣点类型。 00:10:19.840 EN: And then since the domain of has phone number is a point of interest, it also includes a mountain. So that in the end means a mountain has a phone number, right? 中文初译: 然后,既然电话号码的域是一个感兴趣的点, 它也包括一座山。所以最后意味着山有电话号码,对吗? 00:10:32.700 EN: So this is, for example, something where you, which leads a bit to some inconsistency later on, where you figure out, it looks on a superficially, your knowledge representation looks fine. 中文初译: 举例来说,这就是一些你, 导致一些前后不一致的地方, 当你发现它表面上看的时候, 你的知识代表看起来很好。 00:10:47.100 EN: You have the class point of interest, you have the class mountain, you defined a phone number for point of interest. 中文初译: 你有阶级利益,有阶级山, 你定义了一个电话号码来表示兴趣。 00:10:54.300 EN: But since then mountain is a subclass and then have a mountain having a phone number doesn't really make sense. 中文初译: 但从那以后 山就成了一个小阶级 然后山里就有了一个电话号码 这完全说不通 00:11:01.360 EN: And this is what I mean by that this implicit information can result in some unintended consequences. And one unintended consequence can also be that an individual belongs to two classes, which should not belong. 中文初译: 这就是我的意思,这种隐含的信息可能导致一些意想不到的后果。而一个意外后果也可能是个人属于两个类别,不应该属于这两个类别。 00:11:17.640 EN: And that's in order to avoid that, you can define the classes to be disjoint. Still a reasoner will say that this individual should also be, should not only be a faculty member, but it should also be a publication, but it cannot because it's defined as disjoint. 中文初译: 为了避免这种情况,你可以定义分解的类别。仍然有一位理性者会说这个个体也应该是,不仅应该是一个教职员工,而且还应该是一个出版物,但它不能因为它被定义为分解。 00:11:37.440 EN: So a reasoner will discover an inconsistency and that helps you to fix your ontology. So that's a bit the idea of defining classes to be disjoint. 中文初译: 所以一个理性者会发现不一致之处, 有助于你修复你的本体论。所以这有点像定义各班分解的概念。 00:11:50.600 EN: So, and then we had also role properties for properties, basically properties of properties. So domain and range, we had an RDF and RDF schema already, but then also transitivity, symmetry, functionality, inverse functionality and these can be expressed also in OWL. 中文初译: 因此,我们也有属性的作用属性, 基本上是属性的属性。 所以域和范围, 我们已经有一个“RDF”和“RDF”的模型, 但是还有中转性、 对称性、功能、反函数, 这些也可以用“ OWL” 表达。 00:12:17.800 EN: Also same as, you can define the two instances, two individuals are the same. And that's what you use this term OWL same as for. 中文初译: 同样,你可以定义这两个例子, 两个人是相同的。 这就是你使用的“OWL”这个词和用词一样。 00:12:29.340 EN: And similarly can also define the two individuals are different than you use OWL different from. So that's a bit the same as, yeah, disjoint, but disjoint applies to classes, to sets, while same as and different from applies to individuals, to instances. 中文初译: 同样也可以定义这两个人 与使用“ OWL” 不同。 因此,这与使用“ OWL” 不同, 有点相同, 与使用“ OWL ” 不同。 这与使用“ OWL ” 不同, 与使用“ OWL ” ( OWL ) 不同, 与使用“ OWL ” ( OWL ) 不同, 类似, 脱联, 但脱联适用于班级, 组装, 与使用个人, 实例同样, 也不同。 00:12:50.540 EN: And here we had this example where there was a contradiction, right? So the contradiction here was we defined the domain of latitude and longitude to be spatial thing. 中文初译: 我们这里有了一个矛盾的例子,对吗?所以这里的矛盾就是我们把纬度和经度 定义为空间。 00:13:08.300 EN: And then we have defined our latitude and longitude, applied that to a company, company XY, yeah. And that for example would result that company actually becomes a spatial thing. 中文初译: 然后我们定义了我们的纬度和经度, 应用到XY公司,是的。比如说,这将导致公司 成为空间的东西。 00:13:24.540 EN: So here you have an example where you use the properties, latitude and longitude for company. And since you have previously defined latitude and longitude to have the domain spatial thing, company becomes a spatial thing, yeah. 中文初译: 因此,这里有一个例子,您使用公司的属性, 纬度和经度。既然你以前定义了纬度和经度 来拥有域空间的东西, 公司就变成了空间的事情,是的。 00:13:44.480 EN: So company is defined to be an organization, but implicitly since you use the properties, latitude and longitude, a reason I would infer are since latitude and longitude have to domain spatial thing company XY also must be a spatial thing. 中文初译: 所以公司被定义为一个组织, 但暗含地说,因为你使用 属性,纬度和经度, 我想推论的理由是, 纬度和经度必须 域空间物体,XY公司 也必须是空间物体。 00:14:00.540 EN: And that's actually an unintended consequence. So a company should not be a spatial thing. A reason I would infer it's a spatial thing, there would be no problem as long as you don't have defined company and office to be disjoint classes, yeah. 中文初译: 这其实是一个意外的后果。所以公司不应该是空间的。我推断这是空间的, 只要你没有把公司和办公室定义为脱节类, 就不会有什么问题, 是的。 00:14:22.980 EN: So you actually should define company and office to be disjoint because of course a company is something different than the office of a company. 中文初译: 所以,你实际上应该定义公司和办公室是脱节的 因为当然一个公司 不同于一个公司的办公室。 00:14:34.820 EN: And then here in that example, you would really find an inconsistency in your ontology. You would find that there's company XY, which is a company, which is an organization. 中文初译: 然后在这个例子中,你会发现你的本体论有不一致之处。 你会发现XY公司, 是一个组织,一个组织。 00:14:47.900 EN: And then by inference, it also is a spatial thing. And since you defined in your ontology both as being disjoint, this would lead to an inconsistency, yeah. And these inconsistencies, then you can investigate what's the reason for this inconsistency. 中文初译: 然后通过推论,它也是一个空间的东西。既然你对本体论的定义 两者都是脱节的, 这会导致不一致,是的。这些不一致, 然后你就可以去调查这种不一致的原因是什么。 00:15:06.340 EN: Here the reason is that you attach the latitude and the longitude directly to company XY. You actually should attach that to office and not to a company. 中文初译: 这里的原因是,您直接将纬度和经度与 XY 公司挂钩。 您实际上应该把纬度和经度与办公室而不是公司挂钩。 00:15:18.200 EN: So it should be attached to office XY, yeah. So you should create another individual office XY and then attach latitude and longitude to office XY and then everything is fine. 中文初译: 所以它应该附属于 XY 办公室,是的。所以你应该另建一个单独的办公室 XY, 然后把纬度和经度加到 XY 办公室,然后一切都很好。 00:15:32.480 EN: So then there is a possibility to define classes as enumerations. This is also called nominals, basically that you list all the members of the class, all the instances, the individuals which belong to the class. 中文初译: 因此可以将分类定义为计数。这也称为名义数字, 基本上您列出该类的所有成员, 所有的例子, 属于该类的个人。 00:15:47.800 EN: So here in that case, we define the class moon of Mars and we say there are two instances there, Phobos and Deimos. 中文初译: 因此,在这种情况下,我们定义了火星的月亮等级, 并且说这里有两个例子,Phobos和Deimos。 00:15:58.280 EN: And this is in turtle syntax. It looks a bit more, yeah, a bit more complex. You define moon of Mars, then has an equivalent class. 中文初译: 这是在海龟语法中。 它看起来更复杂一些, 是的, 更复杂一点。 你定义火星的月亮, 然后有一个等同的类。 00:16:09.140 EN: The equivalent class is an anonymous class, a blank node, which then uses this one off property to define and the list of two things that those two things belong or basically create this anonymous class. 中文初译: 等同的类是匿名类, 一个空白节点, 然后用这个空节点 来定义和列出两样东西 这两样东西都属于它们 或者基本上创造出这个匿名类。 00:16:29.520 EN: And then since they are equivalent, that means that moons of Mars are exactly those two individuals. So, and then there are these logical class constructors, intersection of, union of, complement of. 中文初译: 火星的月亮就是这两个人。然后是逻辑级构造器, 交汇,结合,组合,补充。 00:16:45.960 EN: They are used to construct complex classes from simpler classes. And we can see, look again at some examples. For example, we define the equivalence of the moon of Mars is equivalent to the moons and objects near Mars. So this is an intersection, yes? 中文初译: 它们用来从更简单的类中构建复杂的类。我们可以看到,再看看一些例子。例如,我们定义火星月亮的等同性相当于火星附近的月亮和物体。所以这是一个交叉点,是么? 00:17:11.300 EN: Since we have defined classes or you can imagine classes as being sets, you can build intersection of sets. And if you build the intersection of all moons in the, for example, solar system, there are a lot of moons for different planets. 中文初译: 既然我们已经定义了班级,或者你可以想象类组是成型的, 你可以建立交集。如果你在太阳系中 建造了所有月球的交汇点, 比如说太阳系, 不同行星都有许多月亮。 00:17:28.340 EN: And then the ones, the objects which are near Mars, there might be also other objects near Mars, not only moons, maybe there are some asteroids also, but those which are moons and which are near Mars, these are the moons of Mars. 中文初译: 然后这些物体,火星附近的物体, 火星附近的其他物体, 不仅有月亮,也许还有小行星, 还有卫星, 和接近火星的卫星, 这些是火星的月亮。 00:17:44.460 EN: So we can build new classes from existing classes. Here in that case, the existing classes are the classes of moons and the objects near Mars. 中文初译: 因此我们可以从现有等级中建立新的等级。在这种情况下,现有的等级是卫星和火星附近物体的类别。 00:17:54.260 EN: Similarly, we can build the union, for example, to define boat as a union of sailboat and motorboat. Maybe I translate, so this turtle syntax here, let's maybe translate that as a small exercise to triples. 中文初译: 类似地,我们可以建立工会,比如说,把船定义为帆船和机动艇的联盟。也许我翻译,所以这里的海龟语法,让我们把它变成一个小练习,三倍。 00:18:15.600 EN: So I hope you see my screen here. I can make it a bit larger, yeah? So this uses, of course, some syntactic sugar. So we say boat subclass of, and then we have here actually this square brackets indicate a blank node. 中文初译: 所以,我希望你看到我的屏幕在这里。我可以把它放大一点,是吗?所以这当然可以使用一些合成糖。所以我们说船的子类,然后我们这里有这个方括号 表示一个空白节点。 00:18:34.700 EN: So we can indicate a blank node, one, two, three, for example, let's translate that into n triples. So then we have underscore one, two, three, type our class. 中文初译: 所以我们可以指出一个空白的节点,一、二、三, 比如说,让我们把它转换成 n 三倍。然后我们强调一、二、三, 我们的班级类型。 00:18:50.960 EN: So now we have represented that. And then we have underscore one, two, three, our union of, and then this in round brackets, that's a list. 中文初译: 现在我们代表了这一点。然后我们强调一、二、三, 我们的结合,然后放在圆括号中, 是一个列表。 00:19:04.540 EN: Now we have to, I think we missed this part in RDF about lists. So we can look this up in the RDF document, in the standard. 中文初译: 现在我们必须,我想我们错过了“RDF”关于清单的这部分。所以我们可以在“RDF”的文件里,在标准中查一查。 00:19:17.100 EN: So this list basically uses this first. So now we have a union of, and then we have to again create an identifier for our list. 中文初译: 所以这个清单基本上首先使用这个。现在我们有一个联盟, 然后我们必须再次为我们的清单建立一个识别符。 00:19:27.460 EN: So six, seven, eight, then underscore six, seven, eight, type RDF lists. Actually here we have to do full stops always in the end of the triples. 中文初译: 6,7,8,然后强调6,7,8,“RDF”类清单。实际上,我们必须在三重组合的末尾 一直做全停。 00:19:44.660 EN: So, and then a list has a first element. So that's written here, like the first element, RDF first. So in the first element is our sailboat, full stop. 中文初译: 所以,然后列表有一个第一个元素。所以这是在这里写成的, 就像第一个元素,“RDF”首先。在第一个元素是我们的帆船,完全停靠。 00:19:57.740 EN: And then we have rest. The list has also a rest, the remaining basically, list. Now we have to introduce another blank note, underscore three, four, five, for example. 中文初译: 然后我们休息。这个列表还有其他的, 其余的基本上是, 列表。现在我们必须再加一个空白纸条, 比如强调三、四、五。 00:20:18.220 EN: And then underscore three, four, five, RDF has again first, and that's now our motorboat, and that is RDF nil. So the empty, an empty list. 中文初译: 然后强调三、四、五, “RDF”又是第一位, 现在这是我们的摩托艇, 也就是“RDF”零号。空的,空的列表。 00:20:37.310 EN: I think that should be also somewhere here in the standard, yeah, RDF nil. Nil stands for an empty list. The resource RDF nil is an instance of RDF list that can be used to represent an empty list or a list-like structure, yeah. 中文初译: 我认为这也应该在标准中,是的,“RDF”零。Nil代表空列表。资源“RDF”零是一个“RDF”列表的例子,可以用来代表空列表或类似列表的结构,是的。 00:20:55.810 EN: So this is basically the example from this example here, this turtle example written down in triples. So in full triples, yeah. 中文初译: 这基本上是这个例子的例子, 这个海龟的例子 以三重写下来。完全的三重,是的。 00:21:11.230 EN: And that's basically, here we have some blank notes that is square brackets and the round brackets indicate blank note identifiers. 中文初译: 基本上,这里我们有一些空白的笔记 是方括号,圆括号是空白的笔记识别符号。 00:21:22.090 EN: I have question. Sure. Can you go to the symbol code, what you showed us for now? This one, yeah. Yeah, you created blank note for the rest, okay. 中文初译: 我有一个问题,当然。你能去读一下符号代码吗? 00:21:34.090 EN: But for the first, we didn't need to create also another blank note? No, yeah, the first then indeed is the resource. 中文初译: 但是对于第一个,我们不需要再创建一个空白的音符吗?不,是的,第一个就是资源。 00:21:45.890 EN: Why should we create another blank note there? We actually want to list in the list the sailboats and the motorboats, yeah. 中文初译: 我们为什么要再做一个空白的字条? 00:21:53.510 EN: That's why the first is always referring to a concrete resource or individual instance, yeah, the rest. So basically what we do here, the problem is a bit in RDF, we have only triples. 中文初译: 这就是为什么第一种总是指具体的资源 或个别的例子,是的,其他的。所以基本上我们在这里做什么, 问题就在“RDF”里, 我们只有三倍。 00:22:06.550 EN: We have only subject predicate object, right? A list usually has more as two or more elements, right? And this is not easily possible in RDF to represent members. 中文初译: 清单通常有两个或两个以上元素,对吗?在“RDF”中代表成员并不容易。 00:22:21.530 EN: And that's why these lists are constructed by, yeah, first defining a list and then giving the first element of the list and then the rest of the list. 中文初译: 这就是为什么这些清单是由,是的,首先确定一个清单, 然后给出清单的第一个要素,然后列出其余的部分。 00:22:33.690 EN: And the rest is again, actually here, we could again define that underscore three, four, five, RDF type, RDF list. Yeah, so a list is constructed incrementally by always defining the first element of the list and then the rest of the list, which is again a list. 中文初译: 其余的是,实际上在这里, 我们可以再次定义它强调三、 四、 五, “RDF” 类型, “RDF” 列表。 是的, 所以一个列表是渐进的, 总是通过定义列表的第一个元素, 然后是列表的其余部分, 也就是列表 。 00:23:01.520 EN: And this way you can create arbitrary long lists. There is actually also another possibility to do this with these underscore properties. 中文初译: 这样您就可以创建任意的长列表 。 实际上还有另一种可能使用这些突出显示属性来做到这一点 。 00:23:15.460 EN: So this is an ordered list here. And the advantage is here, you really have them ordered. Yeah, you have always the first and the rest and that's why you have an order in the list, yeah? 中文初译: 所以,这是这里的订单清单。优势就在这里,你真的有他们订单。是的,你总是有第一个和其余的, 这就是为什么你在列表中有一个订单的原因,是吗? 00:23:26.240 EN: First, second, third, and so on. And also the list is in a way closed because in the end we have these rests RDF nil. 中文初译: 首先,第二,第三,等等。同样,清单也以某种方式被关闭了, 因为最后我们把这些“RDF”的零。 00:23:36.560 EN: So that means the list ends there, yeah? And there's also this other possibility of defining lists using underscore one, two, three as properties. 中文初译: 这意味着列表就到此结束,是的。还有另一种可能性 定义列表时用强调一、二、三作为属性。 00:23:52.540 EN: So three, we actually don't need here in our case. So we could also define this in a way, and that's maybe a bit simpler way to do it. 中文初译: 所以,第三,我们实际上不需要在这里处理我们的情况。所以我们也可以用某种方式来定义这一点, 这样做也许比较简单一些。 00:24:02.680 EN: One, sailboat and two, motor boat, yeah? Underscore, six, seven, eight. This is also possible to do it that way, to basically list the members using these underscore properties in RDF. 中文初译: 一艘帆船和两艘机动船,是么? 00:24:22.720 EN: Okay, but this is just to show you basically how to translate the syntactic sugar from these examples in the end into RDF triples. 中文初译: 好吧,但这只是要向你们展示 如何将这些例子中的同义糖 翻译为“RDF”三倍。 00:24:34.060 EN: In the end, it's always only subject predicate object triples, yeah? That's important. Everything you see here can be translated in subject predicate object triples. 中文初译: 归根结底,它总是只有实验对象的上游物体三倍,是么?这很重要。你在这里看到的一切都可以被翻译为 实验对象的上游物体三倍。 00:24:43.860 EN: And that's also very important because we have those triple stores. We will also learn in two weeks how we can query them using the Sparkle query language. 中文初译: 这也很重要,因为我们有三家商店。我们两周后还会学习如何使用Sparkle查询语言询问它们。 00:24:55.020 EN: And if there would be a different, if it would be not only triples, it would be very complicated to actually run queries on top of RDF knowledge bases. 中文初译: 如果有不同的情况,如果不只是三倍, 以“RDF”知识库为顶端进行查询将会非常复杂。 00:25:07.740 EN: That's why everything in RDF and RDF schema and OWL can be represented in simple subject predicate object statements. 中文初译: 这就是为什么“RDF”和“RDF”的图案和“OWL”中的每件东西都可以在简单的标的上游物体说明中进行表达。 00:25:15.640 EN: Here's also an example of a disjoint union. For example, professor is a subclass of an anonymous class in that case, and this anonymous class is a disjoint union of active and retired professors. 中文初译: 这也是一个脱离联系的例子。例如,教授是匿名阶级的子类, 这个匿名阶级是由活跃的和退休的教授组成的脱节联盟。 00:25:33.520 EN: That was disjoint union, and then the complement. So here faculty staff is defined as a subclass of the complement of publications. 中文初译: 这就是脱节,然后是补充。 因此这里的教职员工被定义为出版物补充的子类。 00:25:45.440 EN: So the complement of publication is basically everything, all instances, all individuals, which are not publications. 中文初译: 因此,出版物的补充基本上就是一切,所有事例,所有个人,不是出版物。 00:25:53.220 EN: And then you define faculty staff as a subclass of that. So this is basically also the same as disjoint that faculty staff is disjoint with publication. And we have these role limitations. 中文初译: 然后你将教职员定义为其中的一个子类。所以这基本上也和 教职员与出版脱节一样。我们也有这些角色限制。 00:26:09.340 EN: Like we can define complex classes using constraints on the roles, on the properties. And the first one is all values from. 中文初译: 就像我们可以使用对角色和属性的限制来定义复杂的类别一样。第一种是所有数值的。 00:26:20.960 EN: So here we have one, let's maybe also translate that. This turtle into n triples. So let me add this here. We have exam is a subclass of, and we have a blank node, underscore one, two, three. 中文初译: 因此,这里我们有一个, 让我们也许也把它翻译出来。 这只乌龟变成 n 三倍。 所以让我在此添加一下。 我们的考试是一个子类, 我们有一个空白的节点, 强调一、二、三。 00:26:37.320 EN: So the, and this underscore one, two, three is of RDF type, our restriction. So then we have underscore one, two, three is a restriction on the property examiner, full stop. 中文初译: 因此,这强调了1,2,3是“RDF”类型,我们的限制。所以我们强调1,2,3是对财产检查员的限制,完全停止。 00:26:55.280 EN: And since we have a semicolon, basically it's the next triple again starts with one, two, three, all values from must be from professor. 中文初译: 既然我们有一个分号, 基本上这是下一个三重号 从一、二、三开始, 所有价值都必须来自教授。 00:27:05.880 EN: And so that's how it would look really in triples. So this all values from restriction here in turtle syntax. And you see there is one square bracket and this one square bracket indicates a blank node and this blank node, we can also write out or create a new blank node and then write it out. 中文初译: 因此,它会以三倍的方式看。 所以从这里的海龟语法中, 所有的数值都来自限制值。 你看有一个方括号, 这个方括号表示一个空白节点和这个空白节点, 我们也可以写出来或者创建一个新的空白节点, 然后把它写出来。 00:27:28.300 EN: So we define exam being a subclass of an anonymous class here. So anonymous class because it doesn't have a name really. 中文初译: 所以我们把考试定义为一个匿名班级的子类。所以匿名班,因为它没有名字。 00:27:39.040 EN: This anonymous class is a class which is a restriction and it's a restriction on the property examiner and all values of this property must be professors. 中文初译: 这种匿名阶级是一种限制 也是对物业审查者的限制 财产的所有价值都必须是教授 00:27:51.500 EN: So what does it mean? So this basically selects all individuals which have the property examiner and where all values of this examiner property are professors. 中文初译: 这意味着什么?这基本上选择了所有拥有财产检验员的个人, 以及这些财产的所有价值都是教授。 00:28:06.240 EN: And all these instances which will fill this restriction belong to our anonymous class. And when you define exam to be a subclass of it, that means basically that for exam always, here's actually a typo, values from, that basically means that for the exams, the same restriction holds since it's a subclass 中文初译: 而所有这些将补充这个限制的事例 都属于我们匿名班。当你把考试定义为它的一个子类时, 这基本上意味着对于考试来说, 实际上总是有一个打字机的值, 这基本意味着对于考试来说, 同样的限制是相同的,因为它是一个子类 00:28:38.980 EN: that means for all properties which are applied for exams, the value of the examiner property must be professors. 中文初译: 这意味着对于申请考试的所有财产,考官财产的价值必须是教授。 00:28:48.700 EN: So shall we maybe introduce this with an example? We can say KASW exam for our lecture and then we have a property examiner and then we have maybe another property for an RDF type professor. 中文初译: 所以,我们可以举个例子来介绍这个吗?我们可以说KASW的讲座考试 然后我们有一个财产检验员 然后我们也许还有另一个财产 给“RDF”类教授 00:29:12.600 EN: So if we have such a KASW, yeah, if we have such an individual defined, it has a property examiner and the value of examiner is certain hour. 中文初译: 所以,如果我们有这样一个KASW,是的, 如果我们有这样的一个人的定义, 它有一个财产检验员, 检查员的价值是一定的时间。 00:29:32.690 EN: And since certain hour is a professor, it fulfills, this individual here fulfills this restriction. So this would be implicitly then become an exam or actually here in that case, it's yeah, could become an, or let's maybe do it differently. 中文初译: 既然教授有一定的时间,这就能满足这个限制。 也就是说,这将是隐含的考试,或者实际上,在那种情况下,是的,可以变成一个, 或者让我们做不同的事情。 00:29:57.770 EN: We say, PAESV exam RDF type exam. So what would we, we could conclude that certain hour must be a professor in that case. 中文初译: 我们说,PAESV考试“RDF”类型考试。那么,我们可以得出这样的结论:在这种情况下,一定有时间是教授。 00:30:21.850 EN: So the conclusion would be certain hour RDF type professor because otherwise this could not be true. Only if certain hour is a professor, then actually this restriction would be fulfilled. 中文初译: 因此,结论将是一定的时钟“RDF”型教授,因为否则这不可能是真的。 只有当某个时段是教授的时候,这个限制才会真正实现。 00:30:43.400 EN: And since exam is a subclass of this restriction, the restriction must also hold for all instances of exam including then certain hour. 中文初译: 由于考试是这一限制的一个子类,因此所有考试,包括时数在内,都必须有这种限制。 00:30:55.300 EN: And that means he must be a professor, yeah. So that's what reasoners do, this kind of inferencing then. So we can, there is not only all values from, but also the cardinalities. 中文初译: 这意味着他必须是教授,是的。所以理性者就是这么做的, 这样推论。所以我们可以,我们不仅有所有价值观, 而且还有基本价值观。 00:31:10.340 EN: So we, for example, can define here in that case, exam to be, is a subclass of an anonymous class and this anonymous class is a restriction also on the property examiner and the max cardinality is two in that case for the property examiner. 中文初译: 因此,举例来说,我们可以在此定义, 考试是匿名阶级的子类, 这种匿名阶级也是对财产审查者的限制, 而在这种情况下,对于财产审查者来说,最高为两个。 00:31:30.900 EN: That means an exam can have maximum two examiners. What would happen if you have three examiners? So let's say we have here, Marcus Stocker, Maria Vidal, for example. 中文初译: 这意味着考试最多可以有两个考官。如果你有三个考官,会怎么样?比如说我们这里有马库斯·斯托克、玛丽亚·维达尔。 00:31:48.260 EN: What do you think in that case? Would there be a problem? Can we actually? We need to increase the maximum cardinality to three. 中文初译: 你觉得这样会有什么问题吗?我们真的可以吗?我们需要把 最基本程度提高到3级。 00:31:57.360 EN: Yeah, that would be one possibility, but let me, let me maybe, oh, I can do a small questionnaire here for you. 中文初译: 是的,这是一种可能性,但让我, 让我,也许,哦,我可以做一个小 问卷在这里为你在这里。 00:32:12.970 EN: Unsistent. The question is, is it inconsistent? Okay, let's try if that works. So now you can basically vote. You should be able to vote. Is this inconsistent or is it consistent? 中文初译: 模糊。 问题是, 它前后不一吗? 好吧, 让我们试一下它是否有效。 所以现在你可以基本上投票了。 你应该可以投票。 这是不一致的还是一致的? 00:32:29.190 EN: The question is, is there a model in the real world where this here is basically true given the cardinality restriction? 中文初译: 问题是,在现实世界中有没有一种模式? 鉴于对基本限制的限制,这基本上是真实的。 00:32:40.270 EN: So you should be able to vote now. So far only two people voted or three. Do you see the questionnaire? Yes, we saw it. Yeah, we can, we have it. But most didn't get the answer. 中文初译: 所以,你现在应该可以投票了。 目前只有两个人或三个人投了票。 你看到问卷了吗? 是的,我们看到了。是的,我们可以,但是大多数人没有得到答案。 00:33:00.330 EN: Okay, most of you say it's inconsistent. And this is unfortunately wrong because it can be. The question is, is there a model in the real world which makes it consistent? 中文初译: 好吧,你们大多数人都说这是不一致的。不幸的是,这是错误的,因为它可能是错的。问题是,在现实世界中是否有一个模式来使其一致? 00:33:16.430 EN: And it depends a bit how you define the people, Zurin Awa, Markus Stroker, and Maria Vidal, yeah? The question is, how are they defined? But for example, one model could be that Zurin Awa and Markus Stroker actually are the same. 中文初译: 这取决于你如何定义人民,Zurin Awa、Markus Stroker和Maria Vidal。问题是,他们是如何定义的?但是举例来说,一个模型可能是Zurin Awa和Markus Stroker其实是相同的。 00:33:32.570 EN: Yeah, so if they are not defined to be different people, they could be the same. And in that case, a reason I would think, ah, two of those three must be the same. 中文初译: 是的,所以如果他们不是被定义为不同的人, 他们可能是一样的。在这种情况下,我想这三者中有两个一定是相同的。 00:33:44.290 EN: Yeah, so it would not be by default inconsistent. It becomes inconsistent if we define the individuals to be different, right? So we can say Zurin Awa, Awa, different from Markus Stroker. So we would have to add Maria Vidal. 中文初译: 是的,因此这并非默认的不一致。如果我们把个人定义为不同的人,那就变得不一致了。我们可以说Zurin Awa, Awa, Awa, 不同于Markus Stroker。所以我们必须加上Maria Vidal。 00:34:16.150 EN: And then a third one. Maria and Markus. Yeah, now they are all defined, we are all defined to be different. And then it would become inconsistent, yeah? 中文初译: 然后是第三个,玛利亚和马库斯。是啊,现在它们都被定义了, 我们都被定义为不同。然后它就会变得不一致,是吗? 00:34:30.430 EN: Because then two of those examiners could not be the same anymore. That's why this knowledge engineering and semantic web exam would have three examiners. 中文初译: 因为当时有两位考官已经不一样了。这就是为什么这次知识工程和语义网络考试会有三个考官的原因。 00:34:43.910 EN: Then it would not fulfill this cardinality restriction anymore. But since it's a subclass exam, we have a problem, right? 中文初译: 那么它就不再满足这个基本限制了。但是,既然这是一个子类的考试,我们有一个问题,对不对? 00:34:54.130 EN: But only in that case, there is a problem. So what you can see from this example is that in all reason, always tries to find a model of the world which fulfills the ontology, yeah? 中文初译: 但只有在这样的情况下,才会有问题。从这个例子中你可以看到的是, 在各种原因下, 总是试图找到一个能满足本体论的世界的模型,是么? 00:35:08.330 EN: So, and there are different things. There is this open world assumption and the unique names assumption. So the open world assumption says, what is not stated explicitly, we don't know, can be true, can be false. So if it's not stated, that Zurin Awa, Markus Stroker, Maria Vidal are different from each other, maybe some of them are actually the same, yeah? 中文初译: 所以,有不同的东西。有这样的开放世界假设和独特的名称假设。所以开放世界假设说,没有明确说明的是什么,我们不知道,什么是真实的,也可能是虚假的。如果没有说明的话,那么Zurin Awa、Markus Stroker、Maria Vidal彼此不同,也许其中一些其实是一样的,是吗? 00:35:31.570 EN: So that's the open world assumption. And also the unique names assumption here, just that we have different identifiers for things, it doesn't mean that they are different in reality, yeah? 中文初译: 这就是开放世界的假设。这里还有独特的名称假设, 只是我们的东西有不同的识别特征, 并不意味着它们实际上不同,是么? 00:35:43.930 EN: We discussed that when we talked about RDF and identifiers, there are actually always several identifiers for the same person. 中文初译: 我们讨论过,当我们谈论“RDF”和识别资料时, 同一人实际上总是有几个识别资料。 00:35:52.530 EN: For example, you can use your text ID, you can use your email address, your passport number. Some people even have several passports, right? 中文初译: 例如,您可以使用您的文本 ID, 您也可以使用您的电子邮件地址, 您的护照号码。 有些人甚至有几本护照, 对吧? 00:36:02.870 EN: If you have several passports and you use the passport number as an identifier, unique identifier, then you have several identifiers for the same person. 中文初译: 如果您有几本护照,并使用护照号码作为身份识别特征和独特身份识别特征,那么您就会为同一个人提供若干身份识别特征。 00:36:10.990 EN: That's why just that we have different identifiers, we cannot really be sure that these are also really different individuals. 中文初译: 这就是为什么我们有不同的识别特征, 我们无法真正确定这些也是 真正的不同的个人。 00:36:18.910 EN: And that's a very important thing to keep in mind with RDF and OWL and ontologies and reasoning, that a reasoner tries to find a model which you have your ontology, you have your data, your instances, your individuals, and then a reasoner will try to find an interpretation of this model or one model of it, which can make sense. And sometimes this can mean 中文初译: 这是一件非常重要的事情 需要记住 "RDF"和"OWL" 以及理论学和推理学, 一个理智者试图找到一个模型, 你拥有你的本体论, 你有你的数据, 你的例子, 你的个人, 然后一个理性者会尝试找到一种解释 这个模型或其中的一种模型, 这可以说得通。有时这可以意味着 00:36:47.310 EN: that some individuals are the same as long as it's not explicitly stated. And that's quite important to keep in mind that reasoners, inference engines, that they come to conclusions which might be unintended for you, but then you have to investigate what's the problem and then you can figure out what the problem is. 中文初译: 有些个人是相同的,只要没有明确指出。这一点很重要, 需要记住理性者,推论引擎, 他们得出的结论对你来说可能是意外的, 但是随后你必须调查什么是问题, 然后你就可以找出问题是什么。 00:37:13.350 EN: Good, we had this cardinality restrictions, then we have also has value, has value restrictions. So that means not all values of the property have to belong or one property has a certain value. 中文初译: 好,我们有这种基本限制,那么我们也有价值,有价值限制。这意味着不是所有财产的价值都属于它,也不是一个财产有一定的价值。 00:37:31.490 EN: So let's maybe look at this example here. Let's say exam hour, equivalent class. So we translate that and let's use some one, two, three, some new blank node identifier, underscore one, two, three, RDF type, OWL restriction, underscore one, two, three on property examiner. 中文初译: 让我们来看看这个例子。让我们来看一下这个例子。 比如考试时间, 等效的等级。 所以我们翻译一下这个, 然后我们使用一些一、二、三, 一些新的空白节点识别符, 突出一点,二、三, “RDF”类型,“OWL”限制, 突出一点, 二, 三关于财产检验员。 00:38:02.550 EN: Then we have one, two, three, has value. Okay, now you use our, yeah, yeah. That would be the translation into a triples. 中文初译: 那么我们有一个,二,三,有价值。 00:38:15.270 EN: We resolve basically the blank node here from this square bracket. And we define a new class exam hour or our exam, maybe should be this way. 中文初译: 我们基本上解决了这个方括号中的空白节点。我们定义了一个新的考试时间或者我们的考试,也许应该这样。 00:38:33.110 EN: Of course, it doesn't really matter how you name your classes. And then it's equivalent to a new anonymous class. 中文初译: 当然,你如何命名班级并不重要。然后它相当于一个新的匿名班。 00:38:44.290 EN: And this anonymous class is of type OWL restriction. It's a restriction on the property examiner and it should has a value hour. 中文初译: 这种匿名的分类是“OWL”类型的限制。这是对财产检验员的限制,应该有价值小时。 00:38:56.690 EN: So here, this is now other than all values from, all values from referring to a class. All values from this property must belong to a certain class. 中文初译: 因此,这里现在除了所有数值之外, 所有的值都来自某个类别。 从这个属性的所有值必须属于某个类别 。 00:39:07.290 EN: Here, it just says it has to have at least one value of this property should point to our. And then question is, would this instance here belong to this class? 中文初译: 这里,它只是说它必须至少有一个价值 来指向我们的这些财产。然后的问题是,这个例子是否属于这一类? 00:39:20.310 EN: Yes, it would because it has KASW exam as one property, which points to, okay, here at second hour, we would have to change that. 中文初译: 是的,这是因为它有KASW考试 作为一种财产, 这表示,好吧,在这里,在第二个小时, 我们必须改变这一点。 00:39:34.470 EN: Of course, they have to really match, yeah, like that. So in that case, this individual which we defined here would belong to this class. 中文初译: 当然,他们必须真正匹配,是的,就像那样。所以在这种情况下,我们在这里定义的这个人 就属于这一类人。 00:39:48.470 EN: And since it's equivalent class, so now we didn't use subclass, but we use equivalent class. That means it really also belongs to our exam. 中文初译: 因为它是等同的等级,所以现在我们没有使用子类, 但我们使用等同的等级。 这意味着它真的也属于我们的考试。 00:40:00.070 EN: So then actually it can be inferred that, so I don't know, I indicated maybe in that way that KASW exam is of type our exam. 中文初译: 所以实际上可以推断, 所以我不知道, 我用这种方式表示, KASW 考试是给我们的考试打字。 00:40:10.830 EN: Using such restriction, we can infer also, it's basically you can understand this a bit or interpret this a bit like a query. 中文初译: 使用这种限制,我们也可以推断, 它基本上你可以理解这一点一点点 或者把这个解释得有点像查询。 00:40:22.730 EN: You run a query on your knowledge base, you look for all instances which have the property examiner and which have the value, at least one value for this property must be, should be zero an hour. 中文初译: 您在您的知识库中运行查询, 查找所有有财产检验员且具有价值、 至少此属性必须有一个值的示例, 时间应该是零 小时 。 00:40:37.250 EN: And then these instances which you find in your knowledge base, you add to the class our exam. And that's a bit how you can picture this type or the restrictions yourself. 中文初译: 然后,在你的知识库中发现的这些例子, 你添加到我们的考试课上。 这就是你如何想象这种类型 或你自己的限制。 00:40:47.910 EN: They are like queries on your knowledge base and then the results which fit to this restriction, they are added to the class if it's equivalent class. 中文初译: 他们就像询问你的知识库 然后得出符合这个限制的结果, 如果属于等同的类, 就会被添加到班级中。 00:40:58.630 EN: Of course, if you have here instead of equivalent class, if you have subclass, then it would not work. Then still those instances would be added to our anonymous class. 中文初译: 当然,如果你是在这里而不是同等的阶级, 如果你有子阶级,那它就不会起作用。那么那些例子仍然会加入到我们的匿名阶级中去。 00:41:12.290 EN: But since an instance of a superclass doesn't have to be the instance of a subclass, we cannot be really sure that it also belongs to our exam. 中文初译: 但是,因为超级阶级的例子 不必是子阶级的例子, 我们不能真正确定 它是否也属于我们的考试。 00:41:24.070 EN: So in that case, if you have your subclass off, we could not make this inference, right? So this triple KASW exam RDF type, our exam could not be made in that case when there are subclass off, only when we have here equivalent class. 中文初译: 因此,在这种情况下,如果你的子类关闭了,我们无法做出这样的推论,对吗?因此,KASW的三重考试“RDF”类型,当有子类关闭时,我们就不能进行我们的考试,只有当我们这里有等同的班级的时候。 00:41:41.410 EN: Because then the instances of our anonymous class must be also instances of the defined class our exam. So domain and range, I think is clear. 中文初译: 因为我们匿名班级的事例 必须是我们考试中定义的班级的例子。因此,域和范围,我想是清楚的。 00:41:54.200 EN: We don't have to talk about that again. Yeah, and there was this, we can model the domain D of a property without using domain that can be also done with the restriction. 中文初译: 我们不必再讨论这个问题了。是的,有这样的, 我们可以模拟一个财产的D域, 而不用使用这个域, 也可以用这个限制来做。 00:42:10.100 EN: Okay, then we had negative facts in our tool. It becomes possible to assert negative property assertions, yeah? 中文初译: 好吧,那么我们的工具中就有了负面的事实。 有可能提出消极的财产主张,是吗? 00:42:20.960 EN: So here this looks, is again a bit complicated in RDF. We have to say the source individual is Bill. The assertion property is has wife and the target individual is Mary. 中文初译: 所以这里的外观在“RDF”中又有点复杂。我们必须说源头个人是Bill。声称的财产是妻子,目标个人是Mary。 00:42:35.580 EN: And that basically means that Bill has wife, Mary is not true, yeah? So that this statement, Bill has wife, Mary, is not a part of the knowledge base. 中文初译: 这基本上意味着比尔有妻子,玛丽不是真的。所以这个声明,比尔有妻子,玛丽, 并不是知识库的一部分。 00:42:48.920 EN: So that becomes possible in our two negative facts. So there are male and female persons and people have names. 中文初译: 因此,在我们的两个负面事实中,这就成为可能。因此,有男有女的人和人都有名字。 00:42:58.520 EN: So we define here male person as subclass of person, female person as a subclass of person, has name is a data type property, yeah? 中文初译: 因此,我们在这里将男性定义为个人分类的子类, 女性作为个人分类的子类, 名字是数据类型财产,是吗? 00:43:11.100 EN: Because the name is usually a string. The domain is person and the range is string, yeah? So that makes sense. And then of course, since the domain is applied to person, it can also be used or applied to the subclasses of person which are male person and female person, yeah? Since all instances of male person and instances of female person are also instances of person, of course, this domain definition then also applies to the subclasses. 中文初译: 因为名称通常是一个字符串。 域名是人, 范围是字符串, 是么? 所以这很有意义。 当然, 由于域名适用于人, 它也可以用于或应用于男女的子类人员, 是的? 由于所有男性和女性案例都是人的例子, 当然, 这个域名定义也同样适用于子类人员。 00:43:43.840 EN: So and then we have here some individuals, John and Jill, and we defined John with his name as a male person and Jill with her name as a female person. 中文初译: 然后我们在这里有一些人,约翰和吉尔, 我们定义约翰的名字是男性,吉尔的名字是女性。 00:43:59.300 EN: We didn't need also to add this joint between male person and female person? Yes, that would be better, exactly, yeah. 中文初译: 我们不需要在男女之间加上这种结合吗? 00:44:10.020 EN: Yeah, so in reality, of course, you would have to add a lot of this joint and like it's not always done actually in ontologies. 中文初译: 是啊,所以在现实中,当然了,你必须加上很多这个关节 并且就像它不是总在内科学上做的一样 00:44:23.220 EN: Yeah, so you just often ontologies are maybe also not used so much for reasoning. They are just used for describing data. And if you don't do reasoning, yeah, and you can of course use ontologies in two different ways. 中文初译: 是的,所以你只是经常说 肿瘤学可能也没有被太多用于推理。它们只是用来描述数据。如果你不做推理,是的, 当然你可以用两种不同的方式来使用肿瘤学。 00:44:40.940 EN: You can use them a bit like a database schema and that's what often actually happens in reality. Ontologies are more used like database schemas, yeah? 中文初译: 你可以像数据库一样使用它们,这就是现实中经常发生的事情。本体论更像是数据库的模型,是么? 00:44:51.300 EN: Classes are a bit similar to tables and like a database tables and properties or roles are similar to columns in the tables. 中文初译: 类与表格略相类似,就像数据库表格一样,属性或作用与表格中的列相似。 00:45:01.160 EN: So that's why often ontologies are more used from this kind of database perspective and then they don't contain all these logical axioms. 中文初译: 这就是为什么经常从这种数据库的角度 更多地使用本体论, 然后它们不包含所有这些逻辑的轴。 00:45:11.180 EN: And if as long as you don't use reasoning and your ontologies are not super complex, then maybe there is not such a big problem. 中文初译: 如果你不使用推理 你的本体论不是超复杂的 那么也许就没有什么大问题了 00:45:21.360 EN: But once the ontologies become more complex and then you also want to apply reasoners, then of course it's important to add these logical axioms because otherwise you would come to inconsistencies. 中文初译: 但一旦本体论变得更加复杂,你也要应用理性者, 那么当然有必要添加这些逻辑的共性, 因为否则你会出现不一致。 00:45:36.180 EN: If you use ontologies more as a data schema, data representation schema, then it's basically your task as ontology or knowledge engineer to take care of inconsistencies, to make sure that there are no inconsistencies. 中文初译: 如果你更多地使用本体论作为数据模型, 数据代表模型, 那么基本上你的任务就是作为本体论或知识工程师 处理不一致的问题, 确保没有不一致。 00:45:56.640 EN: Once you add more logical axioms and you use reasoners, then the reasoners can support you in identifying inconsistencies. 中文初译: 一旦您添加了更多的逻辑轴,然后使用理性,那么理智者就可以支持您识别不一致之处。 00:46:04.900 EN: But that's a bit depending on how you use ontologies. And I would say in most of the cases, ontologies are more used as a data description, data schema, yeah? 中文初译: 但是这取决于你如何使用本体论。我想说,在多数情况下,本体论更多地被用作数据描述, 数据模型,是吗? 00:46:17.300 EN: And then often these, also this our axioms, which I've shown you like these restrictions, they are rarely used in normal ontologies. 中文初译: 通常,这些也是我们的法理, 我向你们展示了这些限制, 它们很少用于正常的本体论。 00:46:33.740 EN: In some they are used, but these are, for example, biomedical or in specific domains. I would say maybe 70, 80% of the ontologies are rather shallow descriptions of data descriptions, data schemas, and then there are few in the life sciences, which also are at a lot of these logical axioms and are more complex. 中文初译: 在有些领域,它们被使用过,但是它们是生物医学或特定领域的生物医学。 我想说也许70 % , 80%的本体论只是对数据描述、数据模型的浅薄描述,然后生命科学中也很少,而生命科学也有许多符合逻辑的共性,而且更加复杂。 00:46:58.480 EN: So then we have this different versions of OWL. There was OWL1 and then OWL2 in 2009. And in OWL2, it adds these profiles and some new expressivity. 中文初译: 因此,我们有了不同的版本“OWL”。在2009年有“OWL1”和“OWL2”。在“OWL2”中,它增加了这些简介和一些新的表达性。 00:47:16.080 EN: OWL2-Fool, and why are these profile be used? Because reasoning can be very expensive in terms of resource intensive. 中文初译: "OWL2" -Foool,为什么使用这些剖面图?因为从资源密集的角度来看,推理成本很高。 00:47:28.580 EN: So what I showed you, this RDFS rules that's relatively simple to process RDF schema rules. We had this RDF schema rules, and they can be just implemented as inferencing. 中文初译: 所以,我给你们看的是,这个“RDFS”规则,它比较简单,可以处理“RDF”计划规则。我们有这样的“RDF”计划规则,它们可以作为推论执行。 00:47:43.580 EN: That simple in OWL, it gets much more complicated and reasoners need a lot of memory and a lot of computing power to actually do this reasoning on top of OWL ontologies. 中文初译: 在“OWL”中, 简单得多的“OWL”,它变得复杂得多,理性者需要大量的记忆和大量计算能力才能在“OWL”的内涵上做这个推理。 00:48:01.800 EN: And that's why there are these different flavors introduced in OWL-Fool. You can do everything, but then the reasoning will be very slow, especially when you have large, very large ontologies. 中文初译: 这就是为什么在“OWL”-Foool中引入了这些不同的口味。你可以做所有的事情, 但推理会非常缓慢, 特别是当你有大、非常大的本体论时。 00:48:14.260 EN: As long as your ontology is small, if you only have 100 classes or 200, 500, it's not a problem, but there are some knowledge bases which have thousands or even millions of individuals. 中文初译: 只要你的本体论小, 如果你只有100个班级或200,500个, 这不是什么问题, 但有一些知识基础 拥有成千上万甚至数百万个人。 00:48:27.820 EN: And then this reasoning can be really complicated and resource intensive. And that's why in OWL2, there are different profiles added. 中文初译: 然后这个推理会变得非常复杂, 资源也非常密集。这就是为什么在“OWL2”中增加了不同的描述。 00:48:39.260 EN: So in addition to OWL-Fool, there are three of these profiles, OWL-QL, OWL-EL, and OWL-RL. And the design principle for the profiles is that all two sub-languages are identified that are still implementable in polynomial time, where you can do the reasoning in polynomial time. 中文初译: 因此除了“ OWL”- Foool 外,还有三种剖面图, “OWL”-QL, “OWL”-EL, 和“OWL”-RL。 剖面图的设计原则是,所有两种子语言都被识别出来, 在多元时间仍然可以执行, 您可以在多元时间进行推理 。 00:49:05.580 EN: Polynomial time, it doesn't grow exponentially with the number of instances or class definitions. And that's why this polynomial time is something which is computationally still tractable. 中文初译: 多式时间,它不会随着实例或类定义的数量而成倍增长。 这就是为什么这个多式时间在计算上仍然是可以移动的。 00:49:22.220 EN: And that's why these subsets or sub-languages of OWL are introduced. In general, they disallow negation and disjunction because that complicates reasoning and is rarely needed. 中文初译: 这就是为什么这些“OWL”子集或亚语言被引入。一般而言,它们不允许否定和脱节,因为这会使推理复杂化,而且很少需要。 00:49:37.420 EN: Negation and disjunction creates problems. And this is disallowed in these sub-languages of OWL2. So OWL-QL stands for query language. 中文初译: 脱节和脱节会产生问题。 在“ OWL2 ” 的子语言中不允许使用这种语言。 所以“ OWL” QL 代表查询语言 。 00:49:50.320 EN: It's based on the ELITE family of description logics. There's a whole also research area, it's called description logics, which are the logical foundation for OWL and for ontologies. 中文初译: 它基于ELITE的描述逻辑。还有整个研究领域,叫做描述逻辑, 这是“OWL”和本体论的逻辑基础。 00:50:05.720 EN: And this QL is designed for query answering using SQL reviting on top of relational databases. So if you have a relational database, you can translate or map the schema of your relational database to an ontology. 中文初译: 此 QL 设计用于使用“ SQL” 在关系数据库的顶端进行查询回答。 所以, 如果您有关联数据库, 您可以将您关系数据库的图案翻译或映射为肿瘤学 。 00:50:21.720 EN: And then when you have some queries on the ontology, you can translate them into SQL queries of the underlying relational database. 中文初译: 当你对本体论有某些查询时, 你可以将其转换成“ SQL” 查询。 00:50:32.440 EN: And that's possible with the OWL-QL sub-language. So subclasses can only be class names or existentials with unrestricted fillers. 中文初译: 使用“ OWL” QL 子语言是可能的。 所以子类只能是类名或存在状态, 有不受限制的填充者。 00:50:45.780 EN: So it basically means it cannot be class names, means it cannot be these kind of restrictions, yeah? These restrictions are usually anonymous classes, unnamed classes, they are defined by as a restriction. 中文初译: 所以这基本上意味着它不能是类名, 也意味着它不能是这种限制。这些限制通常是匿名的, 无名称的,它们被定义为一种限制。 00:50:59.480 EN: So that's then here disallowed for OWL-QL. Superclasses can be class names, existentials or conjunctions with superclass fillers. 中文初译: 所以这里不允许“OWL”-QL。 超级类可以是类名、存在或与超级类填充者连在一起。 00:51:11.820 EN: Or negations with superclass filler. So that's what is possible in OWL-QL. And here are some examples. So fish is a subclass of animal. 中文初译: 或与超级填充器的否定。 所以在“ OWL”- QL 中, 这是可能的。 这里有一些例子。 所以鱼是动物的子类 。 00:51:25.180 EN: Here you see this description logic syntax. So that means subclass, fish, subclass of animal is allowed. Or also this existential quantification. 中文初译: 这里您可以看到这个描述逻辑语法。 这意味着允许亚类, 鱼类, 动物的子类。 或者还有这个存在性量化。 00:51:38.280 EN: So this has value restriction here. That's a description logic syntax for has value restriction. The has value restriction on the property has house. 中文初译: 因此这里有价值限制。 这是描述逻辑语法有价值限制。 财产的价值限制是有房子的。 00:51:51.260 EN: And this T here is the top level concept. So we basically select the instances, the individuals which have the property has house. 中文初译: 这个T是顶级的概念。所以我们基本上选择了例子, 拥有财产的个人有房子。 00:52:02.760 EN: And it has some value or it has a value something. And that is a subclass of landlord. So this is also allowed. 中文初译: 它有一定的价值,或者它有某种价值。那是地主的子类。所以这也是允许的。 00:52:12.820 EN: Let's maybe translate that into, as a small exercise here, into RDF. So we have house, a landlord. So let's do that here, has house. 中文初译: 让我们把它变成一个小练习, 变成“RDF”。所以我们有房子,房东。让我们在这里做,有房子。 00:52:29.540 EN: So we have to define a restriction. So we do this one, two, three, RDF type. OWL, restriction, restriction, yeah. 中文初译: 所以我们必须定义一个限制。所以我们做这个一,二,三,“RDF”类型。“OWL”,限制,限制,是的。 00:52:48.440 EN: Underscore one, two, three, OWL on property, has house, then underscore one, two, three, has value, OWL thing. And then we had, is a subclass of landlord. 中文初译: 一,二,三,财产上的"OWL" 有房子,然后强调一,二,三,有价值, "OWL"的东西。然后我们,是地主的子阶级。 00:53:06.850 EN: So underscore, or we can do it here. Underscore one, two, three, subclass of landlord. Yeah, so this is basically allowed, which is a has value restriction with an unrestricted filler. 中文初译: 因此强调,或者我们在这里可以做到这一点。强调1,2,3, 地主的亚类。是的,所以这基本上是允许的, 这是一个有价值限制的无限制填充者。 00:53:29.590 EN: That's why OWL thing here. That was, I think the term which we, super subclasses can be class names or existentials with unrestricted filler. 中文初译: 这就是为什么"OWL"这个词在这里。我想我们,超级子类的术语 可以是类名或者有无限制填充物的存在。 00:53:44.030 EN: And that's exactly what we have here. Existential is a has value restriction. So it must exist, it should exist. 中文初译: 这正是我们在这里拥有的东西。存在是有价值限制的。所以它必须存在,它应该存在。 00:53:55.010 EN: And an unrestricted filler means we cannot restrict it to something, yeah. It can be anything. That's why OWL thing here, yeah. 中文初译: 一个不受限制的填充器意味着我们不能把它限制在某事上,是的。它可以是任何东西。这就是为什么这里有"OWL"这个东西,是的。 00:54:06.840 EN: So this is basically an OWLQL allowed. And then we see here what is forbidden. So here, these two things, a bit more complex ones are forbidden. 中文初译: 因此,这基本上是允许的OWLQL。然后我们在这里看到什么是被禁止的。所以这里,这两件事情, 更复杂的两件是被禁止的。 00:54:18.160 EN: I haven't introduced this description logic syntax to you. So maybe, yeah, we skipped that for today. Maybe we come back to that later on. 中文初译: 所以,也许,是的,我们跳过了今天。也许我们稍后再谈这个问题。 00:54:30.830 EN: So also forbidden is equality. This junction is forbidden, yeah, where you have basically disjoint union. For example, this here would be a disjoint union of ebook and printed book. 中文初译: 平等也是被禁止的。 这个连接点是被禁止的, 是的, 你基本上已经断绝了结合。 比如说, 这里将是一个电子书和印刷书的断绝联合。 00:54:44.640 EN: It's also forbidden in OWLQL. Universals, this is this all values from restriction here. So all values from killed. 中文初译: 在OWLQL 宇宙中也禁止它, 这就是这里所有限制的价值观。 所以所有被杀死的价值观都在这里。 00:54:57.350 EN: Human, that would be a murder, yeah. So this is also not allowed. Self is not allowed. Somebody who loves himself is a narcissistic person. 中文初译: 人类,那将是谋杀,是的。所以这也不允许。自我是不允许的。爱自己的人是一个自恋的人。 00:55:13.190 EN: It's just an example, but everything which uses this self, and then also cardinalities are not allowed in OWLQL. 中文初译: 这只是一个例子, 但所有使用这种自我的东西, 以及最主要的东西 都不允许在OWLQL。 00:55:22.530 EN: And also keys and property chains and transitive properties. So a lot of things which are then possible in OWL2 are here not allowed in OWLQL. 中文初译: 以及钥匙和财产链和中转属性。所以许多在“OwL2”中可以做到的事情在这里都不允许在 OWLQL中出现。 00:55:34.230 EN: Also nominals, also basically defining classes as a set of individuals. So here, for example, the class birthday. 中文初译: 同样的名义,也基本上把班级定义为一组个人。比如说,班的生日。 00:55:46.670 EN: My birthday guess is defined as Bill, John, and Mary as a set of these three individuals. So this is also not allowed in OWLQL. 中文初译: 我的生日猜想被定义为比尔,约翰和玛丽 是这三个人的一组。所以在OWLQL中也不允许这样。 00:55:59.130 EN: And functional properties, so properties which only have one value, for example, has husband, also not allowed in OWLQL. 中文初译: 功能性财产,所以只有一种价值的财产,例如,丈夫有,在OWLQL中也不允许。 00:56:09.570 EN: So that's a very simple subset sub-language of OWL. And then there is OWL-EL, which stands for... So this focuses on terminological expressivity used for lightweight ontologies, allows existential but not universal quantification. 中文初译: 这是“OWL”的非常简单的子子语言。 然后是“OWL”-EL,它代表... 00:56:33.570 EN: No inverse symmetric properties, no disjunctions or negations are allowed there. So, and here are also some examples. What is allowed? 中文初译: 这里不允许反对称属性、脱节或否定。这里也有一些例子。什么是允许的? 00:56:43.690 EN: So we can use this existential. This is this has value. Restriction in conjunction with the subclass and another has value. 中文初译: 这样我们就可以利用这个存在。 这是有价值的。 限制与子类和另一个有价值。 00:56:53.650 EN: Yeah, here's also has value. Similarly here. Yeah, and this is a property chain down here. We haven't talked about that. Basically, a combination of has parent and has parent is a sub-property of has grandparent. 中文初译: 是的,这里也有价值。与此相似。是的,这是个财产链。我们还没有讨论过这个问题。基本上,有父母和有父母的组合是祖父母的子财产。 00:57:10.210 EN: Yeah, if you have a chain of two properties has parent, that's a property chain. And then you can define it as a sub-property of has grandparent. 中文初译: 是的,如果你有两层财产的链条 母有父有母,那就是财产链。然后你可以把它定义为祖父母的子财产。 00:57:20.490 EN: So things like that can be expressed in OWL-EL. And then there is OWL-RL rule language, which allows subclass axioms as rule-like implications with head and body. 中文初译: 类似的东西可以用“OWL”-EL来表达。然后有“OWL”-RL 规则语言, 它允许子类轴轴作为对头部和身体的类似规则的影响。 00:57:33.710 EN: So that's the last sub-language. But maybe let's not go so much into detail here. I wanted to show you some example tool, how we can create ontologies. 中文初译: 所以这是最后的子语言。 但也许我们在这里不要太详细。 我想给你们展示一些例子工具, 如何创造本体论。 00:57:47.050 EN: And there is the Protege Ontology Editor. So that's a software which you can download and install. It's implemented in Java. 中文初译: 还有一个蛋白质学编辑。所以这是一个可以下载和安装的软件。它在爪哇实施。 00:57:55.390 EN: Here you see a screenshot and you can basically create ontologies there. So you don't have to write the source code, the RDF, all source code yourself, but you basically have a nice user interface for that. 中文初译: 您可以在这里看到一个截图, 并且基本上可以创建目录。 所以您不必写源代码, “ RDF ” , 所有源代码都是你自己的, 但是您基本上有一个很好的用户界面 。 00:58:08.550 EN: It's developed by Stanford University and here's the URL where you can download it. And I want to show you actually yeah, some Web Protege Editor, how that works. 中文初译: 这是斯坦福大学开发的,这里是您可以下载的 URL。我想向您展示一下,是的,一些网络Protege编辑,如何运作。 00:58:25.770 EN: So you can use Web Protege and that's what I want to show you now. You can go to webprotege.stanford.edu and then you can also create a sign up for an account. 中文初译: 所以您可以使用 Web Protege, 这就是我现在要展示的。 你可以去 Web protege.stanford.edu, 然后您也可以创建一个账户签名 。 00:58:42.170 EN: I created one already. So once you log in, you have different projects which you create basically different ontologies. 中文初译: 我已经创造了一个。所以一旦你登录了, 你就会有不同的项目, 基本上可以创造出不同的本体论。 00:58:51.730 EN: Let's maybe select the first one which I created here, pizza ontology. And then you have it in the web browser, basically the possibility to create your ontology. 中文初译: 让我们选择我在这里创造的第一个, 披萨本体论。然后你在网络浏览器里找到它, 基本上可以创建你的本体论。 00:59:05.230 EN: So here in that case, you see you have different tabs. You have a classes tab, a properties tab, individuals tab, comments, changes, history. 中文初译: 在此情况下, 您可以看到您有不同的标签。 您有一个分类标签、 属性标签、 个人标签、 注释、 更改和历史 。 00:59:15.870 EN: And let's maybe first look at the classes tab. So we have here on the left, the class hierarchy and we see there is our thing. 中文初译: 让我们先看一下班级的标签。所以我们在左边, 班级等级,我们发现有我们的东西。 00:59:22.830 EN: That's the super class of everything. And then we have two subclasses defined pizza and zutard and then we can expand pizza. 中文初译: 这是所有事情的超级类。然后我们有两个亚类 确定比萨和冻土,然后我们可以扩大比萨饼。 00:59:33.670 EN: And then we see here Italian pizza and bicep pizza. So maybe I changed that once I click on that, I actually see here on the right hand side, the form and I can fill that out. 中文初译: 然后我们在这里看到意大利的比萨饼和比萨饼。所以也许我改变了这一点, 当我点击它的时候, 我实际上看到右手边, 表格和我可以填上这个表。 00:59:47.350 EN: So let's change it to Italian pizza and you see it changes right away. And this one to white pizza. Let's translate it to English. 中文初译: 所以让我们把它换成意大利披萨,你可以看到它马上会改变。这个变成白色披萨。让我们把它翻译成英语。 00:59:56.850 EN: So we have these two subclasses here. And we have two tarts, this we can also change. And we have different types of ingredients like meat, vegetables, and of course, cheese. 中文初译: 因此,我们在这里有这两个小类。我们有两个小类, 我们也可以改变它。我们有不同种类的成分,比如肉类、蔬菜, 当然还有奶酪。 01:00:14.120 EN: So, and that's a nice user interface where you can see basically the class hierarchy. So, and then when you edit a class, a protege generates an IRI for you. 中文初译: 所以,这是一个很好的用户界面, 你可以从中看到类的等级。 因此,当你编辑一个类时, 蛋白会产生一个“IRI”给你。 01:00:25.120 EN: You see, it generates really an identifier with some arbitrary alphanumeric code here, yeah? That's why it's very important to add these labels. 中文初译: 你看,它产生了一个识别码 带有一些任意的字母数字代码。这就是为什么添加这些标签非常重要的原因。 01:00:37.420 EN: And these are then used to basically show you, yeah, on the user interface, the class names and the instances. Then you can add also other properties here, annotations. 中文初译: 然后用这些来显示,是的, 在用户界面上, 类别名称和实例。 然后你也可以在这里添加其它属性, 注释 。 01:00:50.100 EN: You see, it suggests, there's some auto-suggestion here. For example, there is Skos. This is another vocabulary ontology which defines also a lot of properties which can be used. 中文初译: 它暗示,这里有一些自动建议。 比如说, 有 Skos 。 这是另一个词汇本体论, 也定义了许多可以使用的属性 。 01:01:10.520 EN: So for example, Skos comment, cheese is the most important in pizza. And then you can also add here the language tag, EN. 中文初译: 比如说,Skos评论,奶酪是比萨饼中最重要的。 然后你也可以在这里添加语言标签, EN。 01:01:27.120 EN: So it has always this nice auto-suggestion. And of course, you should also use EN, yeah? Then you have parents. 中文初译: 当然,你也应该使用EN,对吗? 01:01:36.720 EN: I don't know why it now on the left-hand side didn't update here, cheese. And I switched to the E. It shows me cheese because I guess somewhere I configured to show German labels. 中文初译: 我不知道为什么现在左手边没有更新,奶酪。我换了E。它让我看起司,因为我想我设置的地方 显示德国的标签。 01:01:49.360 EN: I don't know. And then with parents, you see here that it's, these are basically the super classes, yeah? And you see that here it's ingredient, but I can also attach it to some other class. 中文初译: 我不知道。关于父母,你在这里看到, 这些基本上就是超级类,是么?你看,这是成分, 但我也可以把它附加到其他类。 01:02:01.320 EN: So once I start typing, it suggests me the classes which I have already. So I can, of course, could also add it to pizza. 中文初译: 因此,一旦我开始打字,它就意味着我已经拥有的班级。所以,当然,我可以把它添加到比萨饼上。 01:02:09.320 EN: And that's exactly what I meant. You can attach one individual to two classes and you see then our class hierarchy updated and now cheese is part, is a subclass of pizza and of ingredient. 中文初译: 这正是我的意思。你可以把一个人绑在两个班级上, 你看到我们班级的等级结构更新了, 现在奶酪是一部分, 是披萨和配料的子类。 01:02:22.480 EN: Of course, that doesn't make sense. So we delete this one here. And then there are also relationships. So you can define also our properties for the class. 中文初译: 当然,这说不通。所以我们在这里删除了这个。然后还有关系。你也可以定义我们对于该类的属性。 01:02:36.090 EN: I don't know what we could add here. Yeah, doesn't matter for now. So let's maybe look at the properties. So we can go to the properties tab and here we have object properties, data type properties and annotation properties. 中文初译: 我不知道我们可以在这里添加什么。 是的, 现在并不重要。 所以让我们来看看这些属性。 所以我们可以去到属性标签上, 在这里我们有对象属性、 数据类型属性和注释属性 。 01:02:51.710 EN: And we have a top object property that's always there on top. And then we have a property has two tarts and we can change that to has ingredient. 中文初译: 我们有一个顶尖的物体属性,它总是在上面。然后我们有一个财产有两个果冻 我们可以改变成成分。 01:03:04.890 EN: Did I type that right? Ingredient like this. And then you see here domain, it can be applied to pizza and range ingredient. 中文初译: 我打的对吗? 象这样的成份。 然后你可以看到这里的域, 它可以应用到比萨和靶场成分上。 01:03:16.210 EN: So this is, once you type here, it basically suggests the classes and you can add and describe your properties. 中文初译: 这就是,一旦您输入这里的键, 它基本上就代表了班级, 您可以添加和描述您的属性 。 01:03:29.230 EN: That's a data type property. We have had bucked sides as baking time and we define this property to be functional. 中文初译: 那是数据类型财产。我们曾经在烘烤时间 遇到过侧面, 我们定义了这种财产是功能性的。 01:03:37.510 EN: So it can be only used once and a range we define, we apply it to pizza. And as a range, we have an integer value. 中文初译: 所以它只能使用一次 并且我们定义一个范围, 我们把它应用到比萨饼上。作为一个范围,我们有一个整数值。 01:03:49.350 EN: And then we can also go to the individuals tab and here you see on the left hand, some individuals. So we can go to pizza margarita. And then on the right hand, we see that margarita here it actually draws us a nice diagram that it has two ingredients, tomato sauce and pizza key cheese, which are both ingredients. 中文初译: 然后我们也可以到个人标签上,这里你可以看到左手的一些人。 所以我们可以去吃玛格丽塔披萨。然后在右手,我们看到这个玛格丽塔 给我们画了一个漂亮的图表, 它有两种成分, 番茄酱和芝士芝士, 两者都是原料。 01:04:11.870 EN: And it's an Italian pizza and a subclass of pizza. We can also look at the changes here. Who did what? And we can also look at the form. Like if we go to this details, we can then look at a regular form and we see here labels in different languages. 中文初译: 这是一个意大利比萨饼和一个小类比萨饼。 我们也可以在这里查看这些变化。 谁做了什么? 我们还可以查看表格。 比如,如果我们去研究这个细节, 我们可以看看一个普通的表格, 然后我们用不同的语言看标签 。 01:04:32.390 EN: So we have it in German and in Russian and we have relationships and we have here has baking time, five. You see that it updated when I changed the property it also updated immediately here to has baking time. 中文初译: 因此,我们用德语和俄语做了它,我们有关系,我们在这里有烘烤时间,5个。你看,当我改变它的财产时,它更新了它,这里也立即更新了它,以便有烘烤时间。 01:04:49.350 EN: So that's also very convenient that properties are when you rename it at some place, they are renamed everywhere. 中文初译: 所以,也非常方便 当你在某个地方重新命名时 地产就变得很简便了, 它们到处都被重新命名。 01:04:58.690 EN: Or renaming we actually just changed the label because the original label is actually this alphanumeric or the identifiers this alphanumeric value. 中文初译: 或者重新命名,我们实际上刚刚更改了标签, 因为原标签实际上是这个字母数字或者识别符号, 这个字母数字值。 01:05:10.130 EN: And then we have ingredients here, pizza queso and tomato sauce. So these are the, and you could add more as another ingredient. 中文初译: 然后我们在这里有原料, 披萨面盘和番茄酱。所以这些是, 你可以添加更多作为另一种成分。 01:05:21.090 EN: And you could also directly create salami we actually have already but you could also directly create a new individual there. 中文初译: 你也可以直接创造我们实际上已经拥有的腊肠, 但你也可以直接在那里创造一个新的个体。 01:05:33.810 EN: For example, we could create great named individual named Rucola. So we have edited here and then we see here it is. 中文初译: 例如,我们可以创造出一个叫Rucola的伟大名人。所以我们在这里编辑了一下,然后我们看到它就在这里。 01:05:44.610 EN: And now we have to attach a type of course, Rucola is also an ingredient. So we add it to the ingredient class. 中文初译: 现在我们必须附加一种类型的课程, Rucola也是一个成分。所以我们把它添加到成分类中。 01:05:54.070 EN: So that makes it very easy to create these kinds of knowledge basis ontologies. Right, and now you see it also here in the list of individuals Rucola. 中文初译: 这样就很容易创造出这些知识基础。对,现在你也可以在鲁科拉的个人名单中看到它。 01:06:07.930 EN: You can also define same as, yeah. So link it to another individual. Let's so you can create a new individual and then it's automatically updated. 中文初译: 您也可以定义相同的定义, 是的。 所以将其连接到另一个人身上 。 这样您就可以创建一个新的个人, 然后自动更新它 。 01:06:24.840 EN: You can also switch here to the hierarchy to select only pizzas. And then we have only margarita or the ingredients. 中文初译: 您也可以在此切换到等级, 选择只吃披萨。 然后我们只有玛格丽塔或配料。 01:06:32.460 EN: We have these four ingredients and there are different also tabs where you can see comments. You can also discuss actually you can also different people can collaborate here. 中文初译: 我们拥有这四个元素, 并且有不同的标签, 您可以在这里看到评论。 您也可以讨论一下, 实际上您也可以在这里与不同的人合作。 01:06:44.620 EN: So this is a collaborative web application. You can also see the changes by entities. So for example, you can select pizza and you see who changed when, what, what has happened there. 中文初译: 这是一个合作的网络应用程序。您也可以看到实体的变化。例如,你可以选择披萨,然后看看谁改变了那里发生的事情。 01:06:58.040 EN: So the label was changed from vice pizza to white pizza that was done by me. And you can exactly see who changed what. 中文初译: 所以标签就从副披萨 变成了白披萨 我做的。你可以看到谁改变了什么。 01:07:08.260 EN: And here also in the history, we have to complete a history of all changes especially when you collaborate with different people, work together. 中文初译: 在历史上,我们也必须完成一个所有变化的历史, 特别是当你与不同的人合作, 一起工作的时候。 01:07:17.480 EN: That's quite convenient. When there's here this button share. So link sharing is enabled. So anyone with the link can edit. 中文初译: 这样很方便。 当这里有这个按钮共享时, 链接共享被启用。 因此连接共享会被启用。 任何有链接的人都可以编辑 。 01:07:28.680 EN: So when you have the link here then everybody can basically work on this pizza ontology or you can also add specific users who can comment, edit or manage the ontology. Good, so that's basically WebProtege. 中文初译: 所以当你在这里有链接的时候, 每个人基本上都可以在这个匹萨肿瘤学上工作, 或者也可以加入特定的用户来评论、编辑或管理本体论。很好,所以这基本上是WebProtege。 01:07:48.000 EN: Protege itself is which you install on your own computer is a bit more complex and allows also to create these class restrictions that's here in WebProtege not so easily possible. 中文初译: 蛋白质本身是您在自己的电脑上安装的, 比较复杂一些, 并且还允许设置这些等级限制。 这些限制存在于WebProtege里, 并不容易做到。 01:08:04.080 EN: But what's also very nice is basically that it creates, for example, then these visual graphs which shows you basically visually how the relationship between instances, classes is there. 中文初译: 但是,同样也非常好的是, 基本上它创造出,例如, 比如这些直观的图表, 这些直观的图形显示你基本地直观地展示了 实例和类之间的关系。 01:08:28.850 EN: Good, so that's what I wanted to show you for today. 中文初译: 很好,所以这就是今天我想给你们看的