原站英文机器转录 + 本地中文机器初译(未完成逐句听审) 原作者及许可见 attribution.txt;中文由九天新增,不代表原作者认可。 00:00:10.930 EN: After last week's lecture on RDF, we start today with RDF serialization. So as you know, for each data representation, there's usually a data model. 中文初译: 上星期关于“RDF”的讲座之后,我们今天以“RDF”序列开始。所以你知道,对于每个数据表示方式来说,通常有一个数据模型。 00:00:25.990 EN: And then there are ways how to represent data according to this data model in different file formats. So maybe you're aware of how that works with XML. 中文初译: 然后有一些方法可以按照这个数据模型 以不同的文件格式来表达数据。 所以也许你了解XML是如何使用的。 00:00:42.370 EN: There is a XML data model, which is called the document object model. And then there is, of course, the XML standard, which is a file serialization in XML. 中文初译: 有一个“XML”数据模型,叫做文档对象模型。当然还有“XML”标准,即“XML”中的文件序列。 00:00:54.970 EN: Also with databases, we have a data model based on entities and relationships. And then there are different serializations on how to store and export and transfer data in SQL. 中文初译: 此外,在数据库中,我们有一个基于实体和关系的数据模型。然后,在如何储存、输出和传输“SQL”中的数据方面有不同的序列。 00:01:12.640 EN: And the same applies for RDF. So we have learned last week how RDF can be organized in triples, subject predicate object triples. 中文初译: 这同样适用于“RDF ” ( RDF) 。 所以我们上周学到了如何将“RDF ” 组织成三重, 主题的上游物体是三重。 00:01:26.100 EN: And now we will talk about how this can be represented in different syntaxes. So there are different syntaxes for RDF. 中文初译: 现在,我们将讨论如何在不同的语法中体现这一点。因此“RDF”有不同的语法。 00:01:40.380 EN: One important aspect of RDF are the URIs. So we have the possibility to use URIs, these identifiers. And they usually become relatively long. 中文初译: “RDF”的一个重要方面是“URIs ” 。 所以我们可以使用“URIs ” , 这些识别资料。 它们通常会变得相对较长 。 00:01:53.740 EN: And they can be shortened, abbreviated. And then there are different serialization formats. The one which is standardized, which you can also see here in the stack, in the RDF stack, is XML. 中文初译: 它们可以被缩短,缩略。然后有不同的序列格式。一个标准化的格式, 也可以在堆叠中看到, 在“RDF”堆叠中, “XML”是“XML”。 00:02:06.920 EN: That was the first standardized serialization of RDF in XML, which is a bit cumbersome. But there are also other ones, like N3, notation 3, which is a simple text-based format. 中文初译: 这是“XML”中“RDF”首次标准化序列化,这有点繁琐。 但也有其他的,如N3,注3,这是一个简单的文本格式。 00:02:24.500 EN: There is JSON-LD, JSON Linked Data. Many of you probably know JSON, the JavaScript Object Notation. And there is an extension of that, defining how JSON files can be represented in RDF. 中文初译: 有“JSON-LD”, JSON链接数据。 你们中许多人可能知道 JSON, JavaScript 对象符号。 并有此的延伸, 定义 JSON 文件如何在“ RDF” 中被代表 。 00:02:42.840 EN: There's all the RDFa, which can be embedded in HTML, which is important for web pages. And then turtle and triples, which you have seen already, I guess, in the last lecture, since I've used that as a default. 中文初译: 所有的“RDFa”都可以嵌入 HTML, 这对网页很重要。然后是海龟和三重, 我猜你已经在上次演讲中见过了, 因为我用它作为默认值。 00:03:03.720 EN: So prefixes for shortening namespaces, they resolve to default prefixes. And there is a service called prefixcc, which you can see here. 中文初译: 所以缩短命名空间的前缀, 他们决定使用默认的前缀。 并且有一个名为前缀的服务, 您可以在这里看到 。 00:03:15.760 EN: Let me maybe open this quickly. So this is a namespace lookup service. And you can enter a namespace and look it up. 中文初译: 让我快速打开它。 因此这是一个命名空间搜索服务。 您可以输入一个命名空间, 并查找它 。 00:03:24.640 EN: And then you see what is commonly used, this namespace, what URIs are commonly used for that. But of course, this is not hammered in stone, but something which you can define for each serialization differently. 中文初译: 然后你可以看到什么是常用的,这个命名空间,什么是“URIs ” 。但是当然,这不是石头钉的, 而是每个序列化的不同定义。 00:03:42.360 EN: But of course, it's good practice to use standard namespace prefixes. So use the top-ranked one from prefixcc, usually. 中文初译: 当然,使用标准命名空间前缀是良好做法。通常使用前置字节最上面的缩略语。 00:03:54.600 EN: So what are URIs? URIs stands for Uniform Resource Identifier. And they are used for worldwide unique identification of resources. 中文初译: “URIs”是“URIs”代表统一资源标识符。它们用于全世界独特的资源识别。 00:04:05.220 EN: Every object may be a resource as long as it has a unique identity. And you can imagine books, places, people, relationships between those things, also abstract concepts like ideas can get such URIs. 中文初译: 每个对象都可能是一个资源, 只要它具有独特的特性。 你可以想象书籍、 地方、人, 以及这些事物之间的关系, 还有抽象的概念, 比如概念可以得到这样的“URIs ” 。 00:04:27.740 EN: So everything should receive a URI which has such an identity. And unique identifiers are already used for a long time in also specific domains. 中文初译: 所以每件事都应该得到一个“ URI ” , 它具有这样的特性。 而独有的识别符号也已经在特定领域长期使用过。 00:04:40.400 EN: I guess most of you know ISBNs, which are used for books or text identification numbers for people. Or in the US, for example, social security numbers are used as identifier for people. 中文初译: 我想你们大部分人都认识ISBNs,这些书本或文字识别码用于人们的书籍或文本识别码。 或者在美国,社会保障号码被用作人们的身份识别码。 00:04:58.360 EN: Email addresses in a way also identify people. So there are various also other identifier schemes. And the URIs are basically an extension of the URL concept. 中文初译: 电子邮件地址也以某种方式识别人。 因此还有其他各种身份识别系统。 而“ URIs” 基本上是 URL 概念的延伸。 00:05:13.160 EN: URLs are Uniform Resource Locators. So the L stands for locating something. And these are basically the addresses of web pages which you have in your address bar of your browser, like up there, for example. 中文初译: URL 是统一资源定位器。 所以 L 表示查找某物。 这些基本上是您在浏览器地址栏中的网页的地址, 比如上面的网址 。 00:05:29.800 EN: And URIs basically have the same structure. But URIs don't have to have a web page. But often, so basically, you can see URLs as URIs for web pages. 中文初译: “URIs”基本上有相同的结构。但“URIs”并不一定要有一个网页。但是,通常,基本上,你可以把网址看成是网页的“URIs”。 00:05:48.040 EN: And it's also good practice basically to make URIs resolvable on the web so that you can actually retrieve information about the URI using the HTTP web protocol. 中文初译: 也是一种好的做法, 基本上可以让“URI”在网上解决, 这样您就可以使用 HTTP 网络协议 来实际检索到有关“URI”的信息。 00:06:04.750 EN: What is the syntax of URIs? That was a request for comments by Tim Berners-Lee, submitted in 1994. And these request for comments are internet standards by the Internet Engineering Task Force, IETF. 中文初译: “URIs”的语法是什么?这是Tim Berners-Lee于1994年提出的征求意见的要求,而这些征询意见的要求是互联网工程工作队(INETF)的互联网标准。 00:06:30.100 EN: And here you have the link basically to the standard. The current version was updated in 2009. It starts with a URI schema and protocol. 中文初译: 这里您有与标准的基本链接。 目前的版本在2009年更新了, 它以“ URI” 模式和协议开始 。 00:06:48.200 EN: So the protocol is usually HTTP or HTTPS. But also, FTP or mail, too, can be other protocols. And they are separated by a colon. 中文初译: 所以协议通常是 HTTP 或 HTPS。 但是, FTP 或邮件也可以是其它协议。 它们被结肠分隔开来 。 00:07:03.920 EN: And then you can, in the end, also append query parameters with the question mark or fragment identifiers after a hashtag. 中文初译: 最终,您也可以在标签后以问号或碎片识别符附加查询参数。 00:07:16.060 EN: So here you see the syntax also how this looks like. So first, the protocol, then the colon, then the hierarchy. 中文初译: 所以这里您可以看到语法也这样。首先,协议,然后结肠,然后是等级。 00:07:25.080 EN: So this includes a domain name, a server name, and a domain name, and then also a location on the server. And after that, and this is optional, there can be a query. 中文初译: 包括域名、 服务器名称和域名, 然后在服务器上还有一个位置。 在此之后, 这是可选的, 可以有一个查询 。 00:07:40.180 EN: And in the end, a fragment identifier, also optional. And you see here on the button an example of a URI from Wikipedia. 中文初译: 最后,一个碎片识别符,也是可选的。你可以看到在按钮上的一个插图 维基百科的“URI”的例子。 00:07:50.480 EN: So you have the protocol in the beginning. Then you have a path on the server. In that case, your w slash index dot php. 中文初译: 因此,您在初始就有协议。 然后您可以在服务器上找到一个路径。 这样的话, 您的 w 斜线指数点 php 。 00:08:01.120 EN: And then you have a query with the question mark and the combination of key value pairs. So here, a search string RDF, and then a hash, which is not shown here, the hash in the end. 中文初译: 然后,您可以查询问号, 以及键值对的组合。 所以这里有一个搜索字符串“ RDF ” , 然后是大麻, 这里没有显示, 最后是大麻 。 00:08:20.600 EN: And then, for example, examples. These are actually two examples, one with the query and the second one with fragment identifier. 中文初译: 然后举例说,这些实际上是两个例子, 一个是查询的例子, 第二个是碎片识别符的例子。 00:08:32.890 EN: So the URI concept is very well-suited for RDF and for knowledge bases, because everyone can define his own URIs. 中文初译: 所以“URI”的概念非常适合“RDF”和知识基础, 因为每个人都可以定义自己的“URIs”。 00:08:42.910 EN: So you don't need a central authority. You don't need to ask someone, like in ISBNs, for example. Or when you have text identifiers, you need to ask the text authorities to assign you an identifier. 中文初译: 因此您不需要中央当局。 您不需要询问某人, 比如在 ISBNs 中。 或者当您有文本标识符时, 您需要请文本当局指定身份识别符 。 00:08:57.390 EN: Or when you publish a book, you need a publisher who assigns you an ISBN. This is not required for URIs. And how can we still ensure that two people are not creating the same URIs? 中文初译: 或者当你出版一本书时, 你需要一个发行商给你指派了 ISBN。 这对“ URIs” 来说不是必需的。 我们怎么能确保两个人不创造同一个“ URIs ” ? 00:09:12.470 EN: The strategy to avoid overlapping URIs is to use the namespace of your own web space. So everybody can have a web space. 中文初译: 避免“URI”重叠的战略是使用您自己的网络空间的命名空间。 这样每个人都可以拥有一个网络空间。 00:09:23.430 EN: Every company, you can register a domain name. You don't even need a domain name. If you have a web space somewhere, can be in the university or somewhere else, you can use the names or the address of your web space as a prefix and then coin URIs by appending something to the space URI. 中文初译: 每个公司都可以注册一个域名。 您甚至不需要域名。 如果您在某个地方有网络空间, 可以在大学或其它地方使用, 您可以使用网络空间的名称或地址作为前缀, 然后通过在“ URI” 空间上附加一些东西来创建“ URI ” 。 00:09:48.040 EN: And you can also then publish documentation of the URI at this place. So here's an example. A colleague of us, Jens Lehmann, has a domain name, jenslehmann.org, and he can publish on his web space then, for example, a FOV document. 中文初译: 你也可以在这里发表“URI”的文件。这里举个例子。我们的同事Jens Lehmann有一个域名,jenslehmann.org,他可以在自己的网页空间上公布一个FOV文件。 00:10:06.820 EN: FOV stands for friend of a friend. It's a vocabulary where you can define your friends and the relationship social network. 中文初译: FOV代表朋友的朋友。它是一个词汇,你可以用来定义你的朋友 和关系社会网络。 00:10:14.440 EN: And then you can append a hash and can say that I identifies you as a person. So also by appending a hash. So you don't even need a namespace. 中文初译: 然后你可以附加一个散列, 并且可以说我认出你是一个人。同样也可以通过附着散列。 所以你甚至不需要一个命名空间。 00:10:25.880 EN: You just need to be able to create a document on the web. And then by appending fragment identifiers to this document, you can create an arbitrary number of additional URIs. 中文初译: 您只需要在网络上创建文档即可。 然后通过将碎片识别符附加到此文档中, 您可以任意创建更多“ URI ” 。 00:10:42.940 EN: So this identifies the person and not the document. If you would remove this hash I, it would identify just the document, the first part here, till RDF. 中文初译: 所以它识别了个人,而不是文件。如果你删除了这个散列I, 它只识别了文件, 第一部分在这里,直到“RDF”。 00:10:56.080 EN: That identifies the document. That's the URL. And after appending this hashtag I, it becomes a different identifier and then can identify a different entity, in that case, a person. 中文初译: 这是文件的标识。这就是 URL。在附加了这个标签I之后, 它变成了不同的识别符号, 然后可以识别另一个实体, 如果是这样的话, 一个个人。 00:11:09.820 EN: And that's very important to distinguish document identifiers from resource identifiers because the documents describe sometimes people, locations, organizations. 中文初译: 这对于区分文件识别特征和资源识别特征非常重要, 因为这些文件有时描述人、地点、组织。 00:11:21.980 EN: And that's why it's very important to distinguish these two types of identifiers from each other. So URIs were also extended into internationalized resource identifiers. 中文初译: 这就是为什么必须区分这两种类型的识别特征。所以“URIS”也扩展为国际化的资源识别特征。 00:11:39.500 EN: And that allows to contain Unicode characters. So here you see an example where we have a German umlaut in the hierarchy, in the path on the server. 中文初译: 允许包含 Unicode 字符。 所以这里您可以看到一个例子, 在服务器的路径中, 我们有一个在等级体系中的德文 umlaut 。 00:11:55.020 EN: Like in that case here, Wüste, the German word for desert. This becomes possible with the IRIs, the internationalized resource identifier. 中文初译: 就像这里的例子,Wüste,德国的沙漠词。有了“IRIs”这个国际化的资源标识符,这就成为可能。 00:12:04.160 EN: So every URI is also an IRI. But IRIs are more. You can use these Unicode characters. But not everywhere, only in certain places. 中文初译: 所以每个“URI”也是“IRI”。但是“IRI”更多。你可以使用这些 Unicode 字符,但不能在任何地方,仅在某些地方使用。 00:12:16.180 EN: So you are only allowed to use these Unicode characters after the server name, basically. And this is actually a bit complicated. 中文初译: 所以您只能使用服务器名称之后的这些 Unicode 字符。 这实际上有点复杂。 00:12:27.860 EN: Also, Unicode characters can appear in the domain name. But there it's more defined. It's a bit different set of Unicode characters. 中文初译: 此外, Unicode 字符也可以出现在域名中。 但有更定义的字符。 这是一个有点不同的 Unicode 字符组 。 00:12:41.280 EN: And you have to be very careful what special characters can be used where. That's why it's actually good practice trying to resort to URIs and not use these Unicode characters too much, because that can become a bit cumbersome. 中文初译: 而且你必须非常小心 哪些特殊人物可以被使用到哪里。这就是为什么它实际上是好的做法 试图使用“URI”而不是过多地使用这些 Unicode 字符, 因为这样会变得有点麻烦。 00:12:59.040 EN: Also sometimes tools get confused. There are also security issues. There is this possibility to use similar looking Unicode characters. 中文初译: 有时工具也会被混淆。 还有安全问题。 使用相似的看似Unicode字符的可能性。 00:13:15.340 EN: And then also you can confuse others, because there are sometimes Unicode characters which look very similar but are actually different. 中文初译: 然后你也可以混淆其他人, 因为有时有 Unicode 字符看起来非常相似, 但实际上却不同。 00:13:27.100 EN: There are also URNs, uniform resource names. So you should not confuse them. They look a bit differently. So they have URN in the beginning, and then a colon, and then also a different scheme. 中文初译: 还有URN, 统一的资源名称。 所以您不应该混淆它们。 它们看起来有点不同。 因此它们开头有URN, 然后是结肠, 然后是一个不同的方案 。 00:13:43.900 EN: Here ISSN, so they are intended for also unique and persisted identification. There are ISBNs, which I mentioned already. 中文初译: 在这里, ISSN, 所以它们也是用来进行独特和持续的识别。 有些是ISBN, 我已经提到过。 00:13:55.680 EN: So these are usually numbers with a number of digits and dashes between them. There are ISSN for journals where you have serials, where you have different issues. Usually with ISBNs, they are for books. 中文初译: 这些通常是数字, 中间有数位数字和破折号。 在期刊上, 有 ISSN 的序列, 问题不同。 通常与 ISBN 的, 书类。 00:14:12.740 EN: There is just one issue of a book with ISSNs. You have regular, for example, monthly or quarterly new editions of a journal. 中文初译: 只有一本书与ISSNs发行。例如,你定期出版月刊或季刊。 00:14:25.200 EN: And that's why there is a different identifier scheme, ISSNs. And there are also DOIs, digital object identifiers for documents. 中文初译: 这就是为什么有一个不同的识别系统, ISSNs。 还有DOI,文件的数字对象识别系统。 00:14:35.440 EN: And they look like that here, also like numbers with dots, and then slash, and then another number in the end. So these are DOIs, document object identifiers. 中文初译: 它们看起来像这里一样, 也像点数, 然后斜线,然后另一个数字在结尾处。 所以这些是DOI, 文档对象标识符。 00:14:47.660 EN: But all these other identifier schemes require some authority to control basically the namespace. So DOIs, you cannot issue yourself. 中文初译: 但所有这些其他的识别系统 都需要某种权力来控制命名空间。因此,DOI不能自问问题。 00:14:57.840 EN: You need to basically have some registrar who issues you a DOI. So what about the RDF, different RDF formats? So there is like a set of serializations in RDF. 中文初译: 基本上,你需要一些注册员 来给你发DOI。那么“RDF”和不同的“RDF”格式呢?所以在“RDF”里有一套序列。 00:15:19.780 EN: And this Venn diagram here illustrates how these are related to each other. So the simplest serialization is N-triples, which you see here in the middle of the Venn diagram. 中文初译: 这里的文恩图说明了它们是如何相互联系的。所以最简单的序列化是N三极, 你可以看到在文恩图中间。 00:15:33.980 EN: And then a bit more expressive serialization format is turtle around N-triples. And then we have SPARQL where clauses, which again add some additional expressivity. And then we have N3, which has the largest expressivity where you can also express rules. 中文初译: 然后一个更清晰的序列化格式是环绕N三峰的海龟。然后我们有“SPARQL” 条款,它又增加了一些额外的表达性。然后我们有了N3, 它具有最大的表达性, 你可以在这里表达规则。 00:16:01.050 EN: And we will see this in the lecture in more detail. And then there is also RDF XML, which can do basically what turtle can do, a bit of what also is expressible in N3 and SPARQL where clauses, but a bit separate. 中文初译: 我们会在演讲中更详细地看到这一点。然后还有“RDF”“XML”, 基本上可以做乌龟能做的事, 在N3和“SPARQL”中也有部分内容也可以表达, 其中的条款是“SPARQL”, 但有些不同。 00:16:21.020 EN: So these serializations, they sometimes add additional, sometimes syntactic sugar to make the formats easier readable, sometimes also really additional expressivity. 中文初译: 所以这些序列,它们有时会添加额外的, 有时合成糖 使格式更容易读懂, 有时还真的增加 表达性。 00:16:35.830 EN: So the most popular formats, I mentioned them already in the beginning, are N-triples. So that's the simplest format, which can be very parsed very easily. 中文初译: 所以最受欢迎的格式,我在一开始就已经提到过,是N三。这就是最简单的格式, 很容易解析出来。 00:16:47.590 EN: Every one of you should be able to write a parser for N-triples. Then there is turtle, which is a bit more complex and focuses on human readability. 中文初译: 你们每个人都应该能写出一个用于 N 3 的解析器。 然后是海龟, 它比较复杂, 并且专注于人类的可读性。 00:17:00.870 EN: Notation 3, N3 has some advanced features, which also go beyond RDF. RDF XML, which is the official XML serialization of RDF and was the first and for a long time the only one which was standardized by the W3C. 中文初译: 3号注N3具有一些先进的特征,也超越了“RDF”、“RDF”和“XML”,后者是“RDF”正式的“XML”序列,是W3C唯一标准化的第一次和长期一次。 00:17:21.130 EN: And then we have also JSON-LD, which I mentioned the official JSON serialization of RDF and RDF-A, which allows to embed RDF in HTML or XHTML and a new HTML standard. 中文初译: 然后我们还有"JSON-LD", 我提到了正式的 JSON 序列化的“RDF”和“RDF-A”, 它允许将“RDF”嵌入 HTML 或 XHTML 和一个新的 HTML 标准。 00:17:43.630 EN: So notation 3 is designed for human readability. It's a formal language. It adds additional features like formulas, rules, and variables. 中文初译: 所以3号符号是为人类可读性设计的。 它是一种正式的语言。 它增加了额外的特性, 比如公式、规则和变量 。 00:17:59.430 EN: It was developed also by Tim Berners-Lee as a W3C submission. Here's the link where you can read it, and it has a MIME type. 中文初译: 这是Tim Berners-Lee作为W3C提交文件开发的。这里是您可以阅读的链接, 它有MIME类型 。 00:18:11.790 EN: These MIME types are basically like a hierarchy of file formats, which are used on the web. For example, your browser can request documents adhering to certain MIME types. 中文初译: 这些 MIME 类型基本上就像文件格式的等级, 文件格式在网上使用。 例如, 您的浏览器可以要求符合某些 MIME 类型的文档 。 00:18:25.610 EN: Usually the browser wants HTML. That's why the browser asks the web server for HTML. But a browser can also display images and text files. 中文初译: 浏览器通常想要 HTML 。 这就是为什么浏览器要使用 HTML 网络服务器。 但是浏览器也可以显示图像和文本文件 。 00:18:37.570 EN: So that's why he supports different of these MIME types. And notation 3 uses the UTF-8 encoding. And here we see an example of an XML notation. 中文初译: 这就是为什么他支持不同的MIME类型。注3使用 UTF-8 编码。这里我们可以看到一个“XML”符号的例子。 00:18:55.540 EN: So that's how an example looks in XML. Let's maybe have a look how it looks like. If we represent RDF in XML, so we have an RDF tag surrounding basically the RDF document. 中文初译: 所以XML中的例子就是这个。让我们来看看它的样子。如果我们在XML中代表“RDF ” 那么我们有一个“RDF”标签,基本上围绕“RDF”文件。 00:19:10.700 EN: So it begins here in the first line, and it ends in the end. So tags are closed with this backslash. And then in the opening RDF tag, we have some namespaces defined. 中文初译: 所以它从第一行开始,最后结束。 因此标记会以反斜线关闭。 然后在“ RDF” 标签的打开部分, 我们定义了一些命名空间 。 00:19:24.740 EN: So we have a namespace for RDF, and then we have basically the URL for the RDF namespace. You see here also the hash in the end. And we have another one, DC, another namespace, and that resolves to Dublin Core. 中文初译: 因此,我们有一个“ RDF” 的命名空间, 然后我们基本上就有了“ RDF” 命名空间的 URL 。 您可以在这里看到最后的杂草。 我们还有一个, DC, 另一个命名空间, 并且它解决到都柏林核心 。 00:19:41.820 EN: Here in the end, we have actually a slash. And then the RDF document starts, and it starts with a description about a certain resource. 中文初译: 最后,我们这里实际上有一个斜线。然后“RDF”文档开始, 它从描述某种资源开始。 00:19:53.580 EN: And here we have the resource. In that case, it's Wikipedia Tony Ben. And then we have a property here. So this is the subject, the about attribute of the description tag that defines the subject. 中文初译: 这里我们有资源。 在这种情况下, 这是维基百科的托尼本。 然后我们在这里有一个属性。 这就是主题, 描述标记的属性, 来定义这个主题。 00:20:11.940 EN: Then we have the property, which is here, DC title. And here you see that we use now the namespace prefix, DC. So actually the property URI is composed of the namespace for DC. 中文初译: 然后我们有了财产,就是这里,DC标题。在这里,你可以看到我们现在使用的是命名空间前缀,DC。所以实际上,“URI”是由DC的命名空间组成的。 00:20:27.620 EN: So this completes string and then appended the title. And the object is just a string, and here in that case, Tony Ben. 中文初译: 所以它完整了字符串,然后附加了标题。 对象只是个字符串, 在这样的情况下,就是Tony Ben。 00:20:39.100 EN: So, and this is the first triple. And then the second triple is we have DC publisher. So that means, again, we use for the predicate this namespace append publisher, that's the URI of the predicate. And this object, we have Wikipedia. 中文初译: 所以,这是第一个三重。第二个三重是我们有DC出版商。 也就是说,我们用这个名称空间的副出版商来作为首饰, 也就是“URI”的首饰。这个对象,就是维基百科。 00:20:57.240 EN: And then the second property, the second triple ends here, and then the RDF description ends. And here you also see that we use RDF description, basically, and that's why we had to define the RDF namespace, because without having this definition of the namespace up here, this could not be resolved to a full URI. 中文初译: 第二个属性,第二个三重结尾在这里, 然后“ RDF” 的描述结束。这里你还看到我们使用“ RDF” 描述, 基本上, 这就是为什么我们必须定义“ RDF” 命名空间, 因为没有这个名称空间的定义, 这无法被确定为完整的“ URI ” 。 00:21:25.480 EN: But with the namespace, we know we have to use this namespace prefix append description, and then we have the full URI. 中文初译: 但是有了命名空间,我们知道我们必须使用这个命名空间前缀附加描述, 然后我们有完整的“URI ” 。 00:21:36.770 EN: So that was the example which I've shown you here in XML. And now let's look how this looks in notation three. And as we said, notation three is easier readable, and you can also define a prefix. 中文初译: 所以,这就是我在“XML”中向你们展示的例子。现在让我们看看这在三个符号中的外观。正如我们所说,第三个符号更容易读,你也可以定义一个前缀。 00:21:53.670 EN: So we have defined the prefix DC here with this at tag in the beginning, and the first line to this Dublin core. 中文初译: 因此,我们在这里定义了 DC的前缀, 在开头的标记, 以及这个都柏林核心的第一行。 00:22:04.470 EN: We have a full stop, that's very important that the lines end in notation three with the full stop. And then we have two triples. The first triple starts, the subject of the first triple is the URL of the Wikipedia page about Tony Benn. 中文初译: 我们有一个完全停止, 这是非常重要的, 线条以三号符号结束, 然后我们有两个三号。 第一个三号开始, 第一个三号开始的主题是维基百科关于Tony Benn的网页的 URL。 00:22:21.850 EN: And you see the full URLs or URIs are enclosed in this square brackets here. Yeah, that's important that full URIs in N3 have the square brackets around them. 中文初译: 你看,整个 URLS 或“URIs” 都包含在方括号内。 是的, N3 中完整的“URIs ” 应该有方括号。 00:22:38.950 EN: The things which are not full, but are basically shortened abbreviated URIs, IRIs, URIs, they don't have this square brackets. 中文初译: 并不是满的,但基本上被缩短了 缩写为“URIs”、“IRIs”、“URIs” 它们没有这个方括号。 00:22:51.730 EN: And then we have as predicate DC title. Again, here the DC basically stands for this prefix, and then appended as title, and then the object is just a string, and the string is encoded in the quotes. 中文初译: 然后,我们有了作为上游的DC标题。同样地, DC基本上就是这个前缀, 然后又被附加为标题, 然后对象只是一个字符串, 而字符串是在引号中编码的。 00:23:06.550 EN: And then we have a semicolon in the end. Why do we have a semicolon? Because the next triple starts with the same subject. 中文初译: 然后我们最后有一个分号。为什么我们有一个分号?因为下一个三号从同一个主题开始。 00:23:16.840 EN: And that's why a semicolon, that's why the second line or third line here in the document only has two components, the predicate and the object. 中文初译: 这就是为什么分号,这就是为什么 文档中第二行或第三行 只有两个组成部分: 上游和天体。 00:23:26.120 EN: The semicolon basically indicates that the next triple uses the same subject. So we don't have to write the URL for the Wikipedia page again, it's basically omitted. That's why there is a white space here. 中文初译: 分号基本表示下一个三进制使用同一主题。 所以我们不必再为维基百科页面写入 URL, 它基本上省略了。 这就是为什么这里有白色的空间 。 00:23:39.260 EN: Also in N3 documents, you can add white space everywhere in between. How many spaces you do or tabs, it doesn't matter. 中文初译: 另外,在 N3 文档中,您可以在中间处添加空白。有多少空格或标签,并不重要。 00:23:48.360 EN: And that's why it's very important to end each triple either with a semicolon if the subject is reused or with a full stop if it then ends. 中文初译: 因此,结束每三重目标非常重要, 要么是用分号结束, 如果该主题被再利用, 要么是完全停止,如果它结束。 00:23:58.540 EN: And that's why the second triple here ends with a full stop. So N3 is a formal language that goes beyond RDF. It's a superset also of sparkle graph patterns. 中文初译: 这就是为什么这里的第二个三联赛以完全停止结束。所以N3是一种正式的语言, 超越了“RDF”。它也是闪烁图案的超集。 00:24:13.570 EN: We will learn the sparkle query language also later on in this lecture. It's more powerful than turtle and RDF XML. 中文初译: 稍后我们也会在演讲中学习闪亮的询问语言。它比海龟和“RDF”“XML”更强大。 00:24:24.410 EN: And it's based on a context-free grammar which allows it to parse it easily. So some features which are available in N3 are also variables, formulas, universal variables, existential variables, statements, data types, not only strings and integers but also other data types. 中文初译: 它基于一种无上下文的语法, 它可以很容易地解析它。 所以在 N3 中有些功能也是变量、公式、通用变量、存在变量、语句、数据类型, 不仅是字符串和整数, 还有其他数据类型。 00:24:58.090 EN: There can be lists and list elements, expressions and sets. And you can find some further information about N3 down there. 中文初译: 列表中可以列出元素、表达式和组装。您可以在下面找到关于N3的更多信息。 00:25:09.110 EN: So the syntax follows the subject predicate object paradigm. Everything has to be identified by a URI. You can also include relative URIs such as fragment, for example. 中文初译: 因此语法遵循主题的上游对象范式。 所有的东西都必须由“ URI” 来识别。 您也可以包括相对的“ URI ” , 例如碎片等 。 00:25:27.330 EN: So basically then what would happen then? Then the URI of the document itself would be used as a base URI. So the document has a certain location. It is published somewhere. 中文初译: 所以基本上接下来会发生什么呢? 然后文件本身的“ URI” 将被用作一个基础“ URI ” 。 因此,文档有一定的位置。 它在某处发布 。 00:25:38.970 EN: And this location is then used as the base URI and would be prepended before such a relative URI which you have here. 中文初译: 然后这个位置被用作“URI”的基地, 并且会在这里的相对“URI”之前预设。 00:25:51.170 EN: So they are relative to the base URI which defaults to the document URI. And then there are also special types of URIs or special types of subjects or objects which have these underscore as a namespace. 中文初译: 因此它们相对于默认为文档“ URI” 的基底“ URI ” 。 然后还有特殊类型的“ URI ” 或特殊种类的主体或物体, 它们以这些符号作为命名空间 。 00:26:12.870 EN: And everything with the underscore as a namespace is a blank node ID. Blank nodes are things which cannot uniquely, cannot be easily identified with an identifier. 中文初译: 任何带加号作为命名空间的东西都是空节点标识。空白节点是无法独有的,不能轻易用识别符号来识别。 00:26:26.030 EN: We will see a bit later what blank nodes are and then objects can be also literals. So here in that case, for example, the age is 24. 中文初译: 我们稍后会看到空节点是什么,然后物体也可以是字面的。例如,在这种情况下,年龄是24岁。 00:26:40.070 EN: This is a literal. Literal is basically data values. So strings, dates, numbers, these can appear also as objects. 中文初译: 这是字面意思。字面意思是数据值。因此字符串、日期、数字也可以作为对象出现。 00:26:51.890 EN: So for numbers and strings, it doesn't make sense to identify identifiers but they can be directly used in the objects of the statements. 中文初译: 因此,对于数字和字符串来说,识别识别符号是毫无意义的,但是它们可以直接用于对数的对象。 00:27:02.490 EN: And then N3 allows some abbreviations. So URIs relative to the base URI can be empty like in this first example here. 中文初译: 然后N3允许一些缩略语。 所以相对于基底“ URI” 的“ URI” 可以像这里的第一个例子一样是空的 。 00:27:16.790 EN: That basically is a statement which has a subject, the base URI. The base URI, as I said, defaults to the document location. 中文初译: 基本上,这是一个有主题的语句,即“URI”基础词。正如我所说,“URI”基础词默认了文件位置。 00:27:26.110 EN: So that would be a statement about the document itself. And it says that the document has a title here. It uses the Dublin Core vocabulary. 中文初译: 这就是关于文件本身的说明。它说,该文件在这里有一个标题。它使用了都柏林核心词汇。 00:27:37.350 EN: And then we have as an object, a string enclosed in quotes. And then in the end, a full stop. So we can use prefixes to shorten the text. 中文初译: 然后我们有一个对象,一个字符串 被连接在引号中。最后,一个完全停止。 所以我们可以使用前缀来缩短文本。 00:27:50.610 EN: And that's, you see here with the at, you can define the prefix and then it becomes easier readable, right? So because you see the DC prefix stands for Dublin Core, it's much easier to read for us then. When you use a prefix and you use a colon instead of the hash or slash between DC and title, 中文初译: 也就是说,你在这里用字首来定义前缀,然后它更容易读懂,对吗?因此,因为你看DC前缀代表都柏林核心,那么我们读起来就容易得多。当你使用前缀时,你会用结肠代替在DC和标题之间的杂草或斜线, 00:28:23.490 EN: and you don't use the angle brackets anymore. Yeah, that's what I mentioned already. And if you have several statements about the same subject, you can use a semicolon to introduce new predicates or a comma to introduce new objects. So that's what you see here. 中文初译: 并且您不再使用角度括号。 是的,我已经提到过这一点。如果你对同一主题有多个声明, 你可以用分号来引入新的上游或逗号来引入新对象。 这就是你在这里看到的。 00:28:40.310 EN: For example, the document here has certain subsections and then we have a list of subsections separated by commas here. 中文初译: 例如,此处的文件有某些分节,然后我们有一份按逗号分开的分节清单。 00:28:52.090 EN: And that basically, how many triples do we have here? The first line, how many triples are these? These are actually one, two, three triples, yeah? 中文初译: 基本上,我们这里有多少三倍?第一行是多少三倍?这些实际上是一、二、三三倍,是吗? 00:29:06.230 EN: So the subject and the predicate is the same. And then we have basically RDF XML as the first subsection, JSON as the second subsection. 中文初译: 因此,主题和谓词是一样的。然后我们基本上把“RDF”作为第一小节,把JSON作为第二小节。 00:29:16.390 EN: They are the subject and the predicate is the same. And then RDF A as a third subsection. Afterwards, we have a semicolon. 中文初译: 它们是实验对象,而上游是相同的。然后“RDF”A作为第三个分节。随后,我们有一个分号。 00:29:24.890 EN: That means that the subject of these statements is also the subject of the next triple statement, yeah? So that's why basically the subject here, which is the document itself, is also used as a subject for the next triple statement and the property is here made by, and then we have slidebykey.org. 中文初译: 这意味着这些声明的主题也是下一个三重声明的主题,是的吗?这就是为什么这里的议题,即文件本身, 也被用作下一个三重声明的主题, 而财产是由我们在这里做的, 然后我们有幻灯片bykey.org。 00:29:48.370 EN: And again, we have a semicolon. That means, again, the same subject. Again, this document, URI, URL, and then we have the creator of this deck, and then we have a full URI of a person. 中文初译: 再说一遍,我们有一个分号。这又意味着同一个主题。再一次,这个文件,“URI”, URL,然后我们有了这个甲板的创造者, 然后我们有了一个人的完整的“URI”。 00:30:03.710 EN: In that case here, it was a webpage of myself from long time ago. So these were just examples. You can also define types in RDF, basically classes. 中文初译: 在此情况下, 这是很久以前我自己的网页。 所以这些只是例子。 您也可以在“ RDF” 中定义类型, 基本上在班级中定义类型 。 00:30:20.450 EN: So, and that's what you see here. In the first example, we have a person, and we say that person has a type RDFS class. So this is a class of things. 中文初译: 这就是你在这里看到的。第一个例子,我们有一个人, 我们说这个人有“RDFS”类。所以这是一类事情。 00:30:33.030 EN: Classes are very important for organizing URIs or resources because often you have sets of resources like people, organizations, places, and they are assigned typed as classes. 中文初译: 班级对于组织“URIs”或资源非常重要, 因为通常你拥有像人、组织、地方这样的资源, 00:30:49.670 EN: So first you can define a class like that here. You say person is a class, and then, yeah, we can type instances to this class, which we will see later, but N3 allows us to abbreviate this RDF type with a simple A. 中文初译: 所以首先你可以定义像这样的班级。 你说人是一个班级, 然后,是的,我们可以输入这个班级的例子, 我们稍后会看到, 但是N3允许我们用简单的 A 来缩写“RDF”类型。 00:31:14.570 EN: So person, A, class, RDFS class. So that makes it even easier readable, but that's just syntactic sugar. So the A basically stands for RDF type, and RDF type basically resolves to this full URI, and then the type appended to the RDF namespace. 中文初译: 个人, A, 类, “ RDFS” 类。 这样它更容易读懂, 但这只是合成糖。 所以A 基本上代表“ RDF” 类型, 而“ RDF” 类型基本上解决了这个完整的“ URI ” , 然后是“ RDF” 名称空间的附加类型 。 00:31:38.450 EN: So it's very important that even in N3, you only have URIs, blanknotes, and literals, only these three elements. 中文初译: 因此,非常重要的是,即使在N3中, 你只有“URIs”、 白字和文字, 只有这三个元素。 00:31:47.110 EN: And everything has to resolve to a URI if it's not a blanknote or a literal. So when writing own vocabularies, you often notice that you have defined a concept, a class, and it's the same as in another vocabulary. 中文初译: 如果它不是白纸或字面意思的话,一切都要决定“URI ” 。所以在写自己的词汇时,你经常注意到自己定义了概念、阶级, 与其他词汇一样。 00:32:12.780 EN: And N3 has also a special and short mechanism to align vocabularies using the equal sign. And this is a shorthand for owl same as. 中文初译: N3 还有一个特别的短期机制来使用等号对词汇进行统一。这是猫头鹰的简称,与猫头鹰一样。 00:32:25.980 EN: We will talk in two, three weeks about owl. Owl is a special vocabulary, web ontology language. And here we can basically say that woman is the same as a female adult in another resource, because of course on the web, we don't have always one identifier, only one identifier for one concept or one person, but we might have many identifiers. 中文初译: 我们将在二、三周内谈论猫头鹰。猫头鹰是一种特殊的词汇,网络本学语言。在这里我们可以基本上说,在另一个资源中,女性与成年女性相同,因为当然在网上,我们并不总是有一个识别符号,只有一个概念或一个人的识别符号,但我们可能有很多识别符号。 00:32:54.840 EN: That's why we need this mechanism for establishing equivalence between different identifiers. And that can be done with owl same as, and this equal sign is just a shorthand for that. 中文初译: 这就是为什么我们需要这个机制 来建立不同识别特征之间的等同。这可以和猫头鹰一样做, 而这个等效的标志仅仅是一个缩略语。 00:33:06.740 EN: So this is also a triple here. Woman is a subject, owl same as is the predicate, and foo female adult is the object, and then the full stop. 中文初译: 这也是一个三重目标。女人是一个对象,猫头鹰和上游一样, 成年富豪是对象,然后是完全停止。 00:33:17.060 EN: And the equal is just a shortcut for owl same as. So, and here in the second statement, we have title, ARDF property. 中文初译: 与猫头鹰的捷径一样。因此,在第二个声明中,我们拥有所有权,即ARDF财产。 00:33:29.840 EN: That's the subject, predicate, and object. And then we have a semicolon. That means the subject is reused. And then basically title is the same, same as, DC title. 中文初译: 这就是主题、谓词和对象。然后我们有一个分号。 这意味着这个主题被再利用。 然后基本上标题与DC标题相同。 00:33:47.960 EN: Yeah, so it can be also mixed with these other shortcuts, which we have seen already, the colon and the semicolon. 中文初译: 是的,所以它也可以和这些其他的捷径混在一起, 我们已经看到过, 结肠和分号。 00:34:04.550 EN: So we can also express rules in N3, and that's what we see here in this feature. So, and these rules also start with the add symbol, and then we can say for all X, Y, Z, and then we have in curly brackets here a rule, then implies, and then, so this is the head of the rule, 中文初译: 因此,我们也可以用N3来表达规则, 这就是我们在这里看到的这个特征。所以,这些规则也从添加符号开始, 然后我们可以说所有X,Y,Z, 然后我们把一条规则放在卷轴括号里, 然后暗指,然后,这就是规则的头条, 00:34:41.550 EN: and then we have in the end the tail of the rule. So X has parent Y, and then we have a full stop, and Y has sister Z, and that implies X has on Z. 中文初译: 最终我们得到了规则的尾巴。所以X有父Y, 然后我们有一个完全停止,Y有妹妹Z, 这意味着X对Z。 00:34:57.110 EN: So this is already a form of inferencing, and that's a feature of RDF, which distinguishes it from other data formats that you have, can do this inferencing. 中文初译: 所以这已经是一种推论的形式, 这是“RDF”的一个特征, 它区别于您拥有的其他数据格式, 可以做这个推论。 00:35:08.210 EN: And this rules here expresses an inference rule. So when we have, for example, the following data here, we have Joe has parent Ellen, and Ellen has sister Susie. 中文初译: 这里的规则代表了推论规则。所以当我们在这里有,例如以下数据时, 我们有Joe的家长是Ellen, 而Ellen的妹妹是Susie。 00:35:19.240 EN: Then a reasoner can apply the rule here, and if you look at the rule, so the variables X, Y, and Z here, they basically match to these two triples, yeah? 中文初译: 然后一个理性者可以在这里应用这个规则, 如果你看看这个规则, 所以这里的变量X,Y,和Z, 它们基本上与这两个三重匹配,是么? 00:35:33.770 EN: Joe has parent Ellen, basically means that X could be bound to Joe, and then Ellen could be bound to Y, and then we have Ellen again has sister, so this matches the second triple pattern here, and Z then would be bound to Susie. 中文初译: Joe有Ellen的家长, 基本上意味着X可能和Joe有联系, 然后Ellen可能和Y有联系, 然后我们又让Ellen有妹妹了, 所以这符合这里的第二个三重模式, Z然后会与Susie有联系。 00:35:59.670 EN: So now we can resolve the tail of this rule. So we can say X, which was Joe, has on, and Z resolved to Susie, Joe has on Susie. So a reasoner could then evaluate this rule and generate new triples based on this for all rule here. 中文初译: 因此我们现在可以解决这一规则的尾巴。我们可以说X,当时是Joe,已经开演了,而Z对Susie下定决心,Joe对Susie下定决心。这样一位理智者就可以评估这一规则并产生新的三重规则。 00:36:22.270 EN: And that's what reasoner is that. We will look also later in the lecture in more detail how that works, but that's already a simple example. 中文初译: 这就是道理所在。我们稍后还将在演讲中更详细地研究这是怎么回事, 但是这已经是一个简单的例子。 00:36:31.210 EN: But this reasoning is not part of RDF, it's something separate. It's supported by this N3 serialization, but it's not a feature of RDF, it's a feature of N3. 中文初译: 但这个推理不是“RDF”的一部分,而是另外的。它得到了N3序列的支持, 但它不是“RDF”的一个特征, 它是一个N3的特点。 00:36:48.100 EN: So and here is the second example, which is a bit more complicated. We have again for all X, Y, and Z, X wrote Y, Y includes, so we have a rule here inside rule, X lives in Z, and then Z whether Y. So this basically is a rule, which tells us how the weather in a certain location is. 中文初译: 下面是第二个例子,这个例子比较复杂。我们再次为所有X、Y和Z, X写了Y、Y等, 因此这里有一条规则,X住在Z,然后Z是否在Y。这基本上是一个规则, 它告诉我们某个地方的天气如何。 00:37:17.920 EN: So if a location is included in another location, then we can imply that if we know the weather for the surrounding location, we also know the weather for the included location. 中文初译: 因此,如果一个位置包含在另一个位置, 那么我们可以暗示,如果我们知道周围位置的天气, 我们也知道其中的位置的天气。 00:37:31.240 EN: And we see her down this example, Bob lives in Boston. Bob wrote Boston weather sunny. Alice lives in Adelaide. 中文初译: 鲍勃写道波士顿天气晴朗,爱丽丝住在阿德莱德 00:37:46.950 EN: Alice wrote Boston weather cold. A reasoner could then conclude Boston weather sunny. So because Bob lives in Boston here in that case, 中文初译: 爱丽丝写了波士顿天气寒冷的字 一个理性的人就能得出波士顿天气晴朗的结论 00:38:16.930 EN: we trust the statements of those people more who live in a certain location. That's your part of the rule, right, lives in. 中文初译: 我们信任那些住在某个地方的人的言论 这就是你的规则,对,在其中生活 00:38:28.450 EN: And that's why if we would use that rule that we trust people who also live at a certain location, then we would trust basically Bob more than Alice. 中文初译: 这就是为什么如果我们使用这个规则, 相信那些也生活在某个地方的人, 那么我们基本上会信任鲍勃而不是爱丽丝。 00:38:40.550 EN: So that's an example of how such rules can be formulated in N3. So this is the first serialization, which we talk about what are the advantages and disadvantages. 中文初译: 这就是N3中如何制定这种规则的一个例子, 所以这是第一个序列化, 我们谈论的是利弊。 00:38:57.890 EN: It's much more compact and readable than XML. Yeah, XML is more complicated. You have also the possibility of defining types, variables, and even formulas. 中文初译: 它比"XML"更紧凑和易读。 是的,“XML”比较复杂。您也可以定义类型、变量甚至公式。 00:39:09.750 EN: It's more powerful than turtle and n-triple. But what are the disadvantages? Yeah, it goes beyond RDF. So it adds something additional. 中文初译: 它比海龟和三元组更强大。但有什么缺点?是的,它超越了“RDF”。所以它增加了一些额外的东西。 00:39:22.070 EN: These rules which I've just shown you, they are basically not part of RDF. So that makes it can make it a bit incompatible with some RDF tools. 中文初译: 我刚刚给你们展示的这些规则 基本上不是RDF的一部分,所以它可能和一些 RDF 工具不相容。 00:39:35.930 EN: And of course, it's also a bit more complex than turtle or n-triples. And it's a bit more difficult to parse. So you have to add support for all the syntax features there in N3. 中文初译: 当然,它也比海龟或正三纹还复杂一点。 分析起来比较困难一些。 所以你必须增加支持 N3 中所有的语法特征。 00:39:48.730 EN: And that makes it a bit harder to parse when you write a parser, basically a software or that. Now let's look as turtle. And turtle is a subset of N3. 中文初译: 这使得写一个解剖器,基本上是一个软件或那个。现在让我们像乌龟一样看。海龟是N3的子集。 00:40:05.970 EN: Turtle stands for terse RDF triple language. And it uses basically the same syntax as N3, but is a bit more limited. 中文初译: “ Turtle” 代表“ RDF” 三重语言。 它使用的语法与 N3 基本相同, 但范围有限一些 。 00:40:16.750 EN: It doesn't support all the features of N3. So the URIs are also in angled brackets. Literal data values are represented in quotes, as you can see here. 中文初译: 它不支持 N3 的全部特性, 所以“ URIs” 也包含在角度括号中。 正如您在这里看到的, 字数数据值以引号表示 。 00:40:35.650 EN: We can append a language tag to a literal. So for example, you can say that this is the German version of the string. 中文初译: 我们可以在字面上附加语言标记。 比如, 您可以说这是字符串的德语版本 。 00:40:46.830 EN: So you can have strings in different languages. And this is done with this at tag appended to the string. And then the ISO codes for languages are typically used. 中文初译: 因此您可以使用不同语言的字符串。 这是在字符串附加的标签上完成的 。 然后通常会使用语言的 ISO 代码 。 00:40:59.210 EN: So these are either two or four or five lateral codes for different languages. And similarly, we can also indicate data types. 中文初译: 这些是两种或四种或五种不同语言的横向代码。同样,我们也可以指出数据类型。 00:41:08.430 EN: So here in that case, this could be the geo coordinate. For example, we can indicate that this corresponds to the XML schema data type float, which is defined in XML schema. 中文初译: 因此,在这样的情况下, 这个可能是地理坐标。 例如, 我们可以指出, 这与“ XML” 模型中定义的“ XML” 数据类型浮点相对应 。 00:41:21.550 EN: And that's done with this double caret symbol. So we basically can append to a string a double caret symbol indicating then the concrete data type. 中文初译: 使用这个双心符号。所以我们基本上可以在字符串上附加一个双心符号, 以显示具体的数据类型。 00:41:35.050 EN: And the data type again is a URI, like an identifier here in that case, an XML schema identifier. Um, triples are terminated by a dot. That's the same as an N3. 中文初译: 数据类型又是一个“URI”, 就像一个识别符号一样, “XML” schema 标识符。 嗯, 三重被点终止。 这和 N3 是一样的。 00:41:49.920 EN: So we have here subject, then we have the predicate, and then we have the object, and then we have full stop. And white spaces and line breaks are ignored outside of identifiers. 中文初译: 因此,我们在这里有主题,然后我们有了上游, 然后我们有了对象, 然后我们就完全停止了。 白色的空格和线间断在识别码之外被忽略了。 00:42:04.760 EN: And this is a W3C recommendation since 2014. And we have the same abbreviations as an N3. We can define prefixes. 中文初译: 这是自2014年以来W3C建议, 我们的缩写和N3一样, 我们可以定义前缀。 00:42:21.210 EN: For example, by here defining the DBR and DBS prefix. And then we have basically a much shorter notation for the triples or statements if you have defined prefixes. 中文初译: 例如,在这里定义 DBR 和 DBS 前缀。 然后我们基本上可以使用三个词或语句的更短的标记, 如果您已经定义了前缀 。 00:42:37.610 EN: So they become more readable. That's the same as an N3. We can group triples with the same subject together using the semicolon. 中文初译: 这样它们就更容易读懂了。这和N3一样, 我们可以用分号将同一主题的三重组合在一起。 00:42:50.280 EN: Also the same as I explained already. Here you see an example for Berlin, different statements about Berlin. Berlin belongs to the country Germany. And then we have a semicolon. 中文初译: 和我已经解释过的一样。这里你可以看到柏林的例子, 关于柏林的不同声明。柏林属于德国。然后我们有一个分号。 00:43:01.700 EN: That means the next triple uses the same subject. Again, Berlin has a label. And then we have as object Berlin. 中文初译: 这意味着下一个三重使用相同的主题。再次,柏林有一个标签。然后我们用柏林作为对象。 00:43:12.900 EN: And you can also group triples with the same subject and predicate together. So you see here Leipzig is located in. 中文初译: 也可以将同一对象的三重组合为一组,并同时进行前置试验。所以你可以看到莱比锡就在这里。 00:43:22.920 EN: And then you have Saxony. And then you have a comma. That means the same subject and predicate applies. So Leipzig is located in. And then the second one, Germany here. 中文初译: 然后你有萨克森。然后你有一个逗号。 这意味着相同的主题和谓词适用。 所以莱比锡就在这里。第二个是德国。 00:43:33.920 EN: And then we have a semicolon. That means we use again the subject of the triple, which is Leipzig, and then has Meyer, Boccat, Jung. And then we have the full stop. 中文初译: 然后我们有一个分号。这意味着我们再次使用三重主题, 也就是莱比锡, 然后有迈耶,波克喀特,郑。然后我们完全停止。 00:43:44.440 EN: So we can basically express how many triples here in two lines. Three triples in two lines. Yeah. So we can shorten and make it more compact with turtle. 中文初译: 因此,我们基本上可以分两行表示多少个三重。三重三乘两行。是的。这样我们可以缩短长度,使之与海龟更加紧密。 00:44:01.440 EN: What are the disadvantages and advantages of turtle? So the advantages, it's concise. It's also efficient to store. 中文初译: 海龟的劣势和优势是什么? 00:44:09.860 EN: You can compress it. It's easy to read for humans. Disadvantages, yeah, it was a bit limited tool support compared to RDF XML. 中文初译: 您可以压缩它。 它很容易为人类阅读。 缺点, 是的, 它的工具支持比“ RDF” "XML" 略微有限。 00:44:21.600 EN: I think that improved already. Meanwhile, turtle is actually very popular because it's easy to read and also relatively easy to process for machines. 中文初译: 我认为这已经改进了。与此同时,海龟其实是非常流行的 因为它很容易读懂,也相对容易处理机器。 00:44:36.360 EN: Ntriples is the simplest format. And it's again a subset of turtle and N3. And that's a simple line based plain text format. 中文初译: Ntriples 是最简单的格式。它又是一个海龟和N3的子集, 这是一个基于直线的纯文本格式。 00:44:50.010 EN: It doesn't allow the abbreviations and the grouping. So semicolon and comma is not allowed. It's also limited to the ASCII character set. 中文初译: 它不允许缩写和分组。 所以分号与逗号是不允许的, 也仅限于 ASCII 字符集 。 00:45:00.890 EN: So you have problems with Unicode there. And all tools which support N3 or turtle will also support Ntriple because it's a real subset. 中文初译: 所以这里的 Unicode 有问题。 所有支持 N3 或海龟的工具 也会支持Ntriple, 因为这是一个真正的子集。 00:45:16.530 EN: And you should not confuse it with notation 3. N3 or notation 3 is a superset of turtle. Ntriples is a subset of turtle. 中文初译: 你不应该把它和注3混淆,N3或注3是海龟的超集。三 ⁇ 是海龟的子集。 00:45:26.410 EN: And here below you see an example. So you can also not have prefixes. You cannot define namespace prefixes in Ntriples. 中文初译: 在此您可以看到一个示例。 这样您也就不会有前缀。 您无法定义 Ntriples 中的命名空间前缀 。 00:45:34.990 EN: So you really have to write always the subject, the predicate, and the object in such a notation. Subject, predicate, object, and then the next subject, predicate, object, and the third one here. You of course also have literals. 中文初译: 所以,您真的必须总是在这样的符号中写出主体、 上游和对象。 主题、 上游、 物体, 然后下一个主体, 上游、 物体, 第三个在这里。 当然, 您也有字眼 。 00:45:48.470 EN: You can also use the language tags and the data types for literals. That's possible. But all the other syntactic sugar from turtle and notation 3 is not allowed in Ntriples. 中文初译: 您也可以在字面上使用语言标记和数据类型。 这是可能的。 但是所有来自海龟和注解3的同义糖, 在ntriples 中都不允许 。 00:46:03.100 EN: There is also an extension of Ntriples. It's called nquads which adds a fourth component. So you have the normal triple subject, predicate, object, and then another fourth one, a context. 中文初译: 也有一个三极的延伸。 它叫做 nquads, 添加了第四个组成部分。 所以您有正常的三重对象, 上游, 物体, 然后是另一个第四点, 一个上下文。 00:46:19.240 EN: And that might be sometimes important for RDF stores to add from where a certain statement came from or where it belongs to. 中文初译: 有时,对于“RDF”的商店来说,这也许很重要,因为从某份声明的来源或属于该声明的地方添加一些声明。 00:46:32.500 EN: So then you can add this context. For example, here in that example, you can say that this first statement here comes from this document. 中文初译: 然后您可以添加这个上下文。例如,在这里的例子中,你可以说,这里的第一句话来自这份文件。 00:46:51.180 EN: Because of course, you can RDF stores need to process a lot of RDF documents. You maybe gather RDF documents from many locations on the web. 中文初译: 当然,你可以“RDF”商店需要处理许多“RDF”文件。你也许可以从网络上的许多地点收集“RDF”文件。 00:47:00.540 EN: And if you want to store where a certain triple came from, then it's good to have this fourth component where you basically store the origin of a certain triple or statement. 中文初译: 如果你想要存储一个三重来自哪里, 那么拥有这四分之一是件好事。 你基本上储存了 一个三分之一或对白的来源。 00:47:17.270 EN: I have a small question. Regardless of the context, so it's like reference for this triple? No, it's not a reference for this triple. 中文初译: 我有一个小问题。不管上下文如何, 它就像三重引用?不,它不是三重引用。 00:47:28.570 EN: It's just a reference for the origin of this triple, where it came from. OK, thank you. So why one should not use XML for RDF or why we should use XML? 中文初译: 这只是这个三重的起源的参考。 好的,谢谢。 那么为什么一个人不应该使用“ XML” 来表示“ RDF ” 或者我们为什么要使用“ XML ” ? 00:47:52.620 EN: So basically, you can decide what you want to use. XML, Turtle, Ntriple, it doesn't really matter. Since we have the RDF data model, the data model defines the meaning of the data. 中文初译: 所以基本上,你可以决定你想要使用什么。“XML”、“Turtle”、“Ntriple”并不重要。既然我们有“RDF”数据模型,数据模型就定义了数据的含义。 00:48:04.020 EN: And you can use different serializations. So each of these serializations have advantages and disadvantages. So XML, for example, is very well supported in many programming languages and environments. 中文初译: 你可以使用不同的序列。所以每个序列都有利弊。例如,“XML”在许多编程语言和环境中得到很好的支持。 00:48:16.640 EN: It's also widespread in business and academia. And yeah, it was a long time best practice to always provide an XML serialization of RDF documents. 中文初译: 商业和学术界也广泛存在。而且,对,总是提供“RDF”文件的“XML”序列化是一个长期的最佳做法。 00:48:34.220 EN: But meanwhile, I think it changed a bit. And many publish RDF also in different serializations because RDF is complicated to understand. 中文初译: 但与此同时,我认为它有所改变。许多出版“RDF”的连号也不同,因为“RDF”很难理解。 00:48:48.260 EN: And you look at it because you basically encode triples, which is also create a graph in the end, these RDF triples. 中文初译: 你看它,因为你基本上 编码了三倍, 这同时也在最后创建了一个图表, 这些“RDF”三倍。 00:49:00.780 EN: And you encode that in a tree structure because XML has this document object model. So this is a tree, and the trees get very large. 中文初译: 您在树结构中编码, 因为“ XML” 有这个文档对象模型。 所以这是棵树, 树木变得非常大 。 00:49:09.340 EN: And you basically encode a graph inside the tree, and that makes it relatively cumbersome to understand and to read this for humans. 中文初译: 基本上,你把一个图编码在树里, 这样就比较难理解, 为人类读这个。 00:49:19.560 EN: Of course, the idea is not to read RDF, the serializations, but the developers have to read it. And the developers often choose also serializations, which they are more comfortable with. 中文初译: 当然,我们的想法不是读“RDF ” ( RDF ) , 序列,但开发者必须阅读它。 而开发者往往也选择序列,他们更喜欢这些序列。 00:49:31.980 EN: Also, RDF XML blows up the files, but that can be mitigated by compression. It also generates overhead. The documents have to be parsed and processed to obtain the RDF data. 中文初译: 此外,“RDF”“XML”会炸毁文件,但可以通过压缩来减轻。它也会产生间接费用。这些文件必须经过解析和处理才能获得“RDF”数据。 00:49:44.880 EN: So if you have very large data sets, there is some overhead with processing the XML documents. If you just use, for example, a turtle, then it's more compact and also easier to parse. 中文初译: 所以,如果你有非常大的数据组, 处理“ XML” 文件有些管理费。 如果你只使用, 例如龟, 那么它就比较紧凑, 也比较容易分析 。 00:50:07.820 EN: So XML syntax of RDF, I showed you already an example, and here's another one. It uses XML namespaces to disambiguate tag names. 中文初译: 所以“RDF”的“XML”语法,我已经给你们展示了一个例子,这里还有一个。它使用“XML”命名空间来模糊标签名称。 00:50:20.340 EN: RDF tags have their own fixed namespace, usually abbreviated using the RDF prefix. And here you see an example of a document. So it begins with RDF. 中文初译: “ RDF” 标签有自己的固定名称空间, 通常使用“ RDF” 前缀缩写。 这里您可以看到一个文档的示例。 因此它从“ RDF ” 开始 。 00:50:33.640 EN: Then we have the namespace declarations here. In that case, we have five namespaces defined, RDF, RDFs, XSD for XML schema, DBP for DBpedia properties, and Geo for Geo vocabulary. 中文初译: 然后我们在这里有了命名空间声明。 在这种情况下, 我们定义了五个名称空间, “ RDF ” 、 RDFs 、 “ XML” schema 的 XSD 、 DBP 属性的 DBP 和 Geo 词汇的 Geo。 00:50:53.400 EN: And then we have the RDF document itself here. It starts with the description about the resource. In that case, DBpedia resource Leipzig is the subject. 中文初译: 然后我们在这里有了“ RDF” 文件本身。 它从描述资源开始。 在这种情况下, DBpedia 资源 Leipzig 就是主题。 00:51:03.420 EN: And then we have basically the tags for the properties, has mayor, and the object is, again, a resource, Bocat Young. 中文初译: 然后我们基本上有地产的标签,有市长, 目标又是一个资源,“野猫Young”。 00:51:12.880 EN: And then we have another predicate label, and the object is Leipzig. And here we have the language tag in addition, yeah, which could be appended in turtle just with the at sign. 中文初译: 然后我们又有了另一个前置标签, 对象是莱比锡。这里还有语言标签, 是的, 可以在标记时附加在海龟上。 00:51:28.140 EN: Here it's encoded as an attribute to the property. This is the property RDF is labeled, and we encode it with an attribute here, XML lang DE, that the language of the string is German. 中文初译: 这里的编码是属性的属性。 这是属性“ RDF” 标签, 我们用属性“ XML” Lang DE 编码它, 字符串的语言是德语 。 00:51:45.000 EN: Then we have the geo coordinates, geo latitude. And here the object is 51.3333. And we indicate the data type again as an attribute to the property, yeah? 中文初译: 然后我们找到地理坐标,地球纬度。这里的物体是51.3333。 我们再次表示数据类型是属性的属性,是么? 00:52:01.720 EN: Here the property is geo let, and then we indicate that the value, the object of this property has the float data type, what we could do in turtle with the double caret symbol. 中文初译: 这里的属性是地理允许的, 然后我们表示这个属性的值, 对象有浮点数据类型, 我们在海龟身上可以做的, 用双心符号。 00:52:18.660 EN: And the same with the longitude here. So how many triples do we have here? Yeah, we basically can count the properties, one, two, three, four, more properties. 中文初译: 和这里的经度一样。我们这里有多少三倍?是的,我们基本上可以计算属性,一,二,三,四,更多的属性。 00:52:42.050 EN: So the RDF description element stands for a subject, and the URI of the subject is the value of the RDF about attribute. 中文初译: 所以“RDF”描述元素代表一个对象, 而主题的“URI”是属性的“RDF”值。 00:52:52.370 EN: Each element of RDF description stands for a predicate object pair, and the name of the child element is the predicate name, and the value of RDF resource is the URI of the object. 中文初译: “RDF”描述的每一项要素均表示对上游物体,而子元素的名称是上游名称,而“RDF”资源的价值是天体的“URI”。 00:53:05.810 EN: So you can basically decode this into triples, yeah? And this could be, for example, also a question in the exam that we give you a snippet, a small XML, RDF XML document, and we ask you to write down the triple, subject predicate object triples. 中文初译: 所以基本上你可以将它解码成三倍,对吗?比如说,这也可能是考试中的一个问题, 我们给您一个小的“XML”、“RDF”“XML”文件, 我们要求您写下三倍的, 主题的上游物体三倍。 00:53:25.510 EN: So you should be able to read RDF XML. Yeah, so here we have a bit more complicated examples. Literals can be enclosed by predicates as freeform text. 中文初译: 所以,你应该可以读到“RDF”的“XML ” (RDF) 。 是的, 所以我们这里有更复杂的例子。 书本可以作为自由文本被首字母封住。 00:53:38.740 EN: Yeah, that's what we see here, for example, with Borchardt-Jung. Yeah, this is a literal, and it's enclosed by the predicate here, and that allows also to represent larger strings, for example, easily. 中文初译: 是的,这就是我们在这里看到的,比如说博查特-Jung。是的,这是字面的, 并被这里的上游封闭着, 这也可以代表更大的字符串,例如,很容易。 00:53:54.920 EN: One subject can contain several property elements. Yeah, that's what we see here. This description is about Leipzig, and then we have several, one, two, three, four statements about Leipzig. 中文初译: 一个主题可以包含几个属性元素。 是的, 这就是我们在这里看到的。 这个描述是关于莱比锡的, 然后我们有关于莱比锡的 数个、一、二、三、四个声明。 00:54:11.300 EN: What we also see is one object description can nest several further subjects, yeah? And that's exactly what we see here about the mayor, the mayor of Leipzig. So this is the predicate. 中文初译: 我们还看到一个物体描述 可以嵌套几个其他的主体,是吗?这正是我们在这里看到的 关于市长,莱比锡市长。这就是谓词。 00:54:23.200 EN: The subject is Leipzig. The predicate has mayor, and the object is another description, which is nested inside here. 中文初译: 标的物是莱比锡,上游有市长, 物体是另一个描述, 嵌入在这里。 00:54:32.540 EN: So it's a description about, and then we have here Borchardt-Jung. So basically the object of the triple has mayor is Borchardt-Jung, this resource here, but we also have another property about, then this resource, Borchardt-Jung, that his name is, and then we have a string Borchardt-Jung, yeah? 中文初译: 所以这是关于博查特的描述,然后我们在这里有了博查特的Jung。因此基本上,三连队的目标就是市长博查特的Jung, 这个资源,但我们还有另一个财产 关于这个资源,博查特的Jung, 他的名字是, 然后我们有波查特的Jung,是吗? 00:54:55.640 EN: So we have a nested description about the resource DBpedia Borchardt-Jung inside here. But again, it just resolves into subject predicate object statements, clear? 中文初译: 因此,我们有一个嵌套的描述 有关资源 DBpedia Borchardt-Jung 在这里。 但再次,它只是解决了 主题的上游物体说明,清楚了吗? 00:55:18.230 EN: So attributes for literals I explained already. So we can basically indicate literals can be expressed as XML attributes. 中文初译: 所以对于字面的属性我已经解释了。 所以我们基本上可以表示字面属性可以表现为“ XML” 属性 。 00:55:35.610 EN: For example, here in that case, so there are different possibilities how to do that. We have here the resource, the subject is DBpedia or Gleipzig. 中文初译: 例如,在这样的例子中,有不同的可能性可以做到这一点。我们这里的资源是DBpedia或Gleipzig。 00:55:48.770 EN: The property is DBpedia property name, and then the object is here encoded just as an attribute. That's also possible, yeah? 中文初译: 属性是 DBpedia 属性名称, 然后对象在此编码为一个属性。 这也可以, 是么? 00:55:57.570 EN: Or we can encode it just as a string value between two tags, and that's done here for latitude and longitude. It's encoded just as a string value between the opening geolat tag and the closing geolat tag in XML. 中文初译: 或者我们可以把它编码成两个标签之间的字符串值, 并且这里是用于纬度和经度的。 它的编码就像打开的地理标签和关闭的“ XML” 中的地理标签之间的字符串值一样。 00:56:25.030 EN: So and then there's also the base URI. So the base URI defines against which relative URIs are resolved. So here we see the RDF namespace. So the namespace for RDF here as the first one, and the second one is actually the base URI. 中文初译: 所以还有“ URI” 基数。 因此, “ URI” 基数定义了相对的“ URI” 是对应的。 我们在这里看到“ RDF” 命名空间。 因此, “ RDF” 的命名空间是第一个, 第二个是“ URI ” 基数 。 00:56:49.150 EN: So everything which has a relative URI is resolved against this base URI. Here in that case, DBpedia.org resource. 中文初译: 因此,所有有相对“URI”的事物 都与这个“URI”基底“URI”相对。在这种情况下,DBpedia.org资源。 00:56:58.230 EN: And then we have an RDF description about Berlin, and you see Berlin is just a relative URI. That means actually the subject is composed of the base URI and appended as Berlin as a string to come create the subject. 中文初译: 然后我们有了柏林的“RDF”描述, 你可以看到柏林只是相对的“URI ” 。 这意味着这个主题实际上由基础的“URI”组成, 并被作为柏林的字符串附在后面来创建这个主题。 00:57:20.570 EN: And the same with the object here, Germany. So again, the base URI is used and then appended this relative URI in Germany to create the object of the country property. 中文初译: 与此对象相同, 德国。 因此再次使用基底“ URI ” , 然后在德国附加这个相对的“ URI ” 来创建国家财产的对象 。 00:57:38.670 EN: So this base URI is important for resolving relative URIs. So what are the advantages and disadvantages of XML? 中文初译: 所以这个基底“URI”对于解决相对的“URI”很重要。那么“XML”的利弊是什么? 00:57:50.490 EN: We discussed that already. There is good tool support for XML. You can use XML transformation tools via XSLT. There is also parsing and memory representation via DOM and sex. 中文初译: 我们已经讨论过这一点。 “ XML” 有很好的工具支持。 您可以通过 XSLT 使用“ XML” 转换工具, 也可以通过 DOM 和 性来进行解析和内存表达 。 00:58:06.850 EN: So on the other hand, I would say the advantages are outweighed by the disadvantages long and hard to read for humans. 中文初译: 另一方面,我要说,长而难于为人类解读的劣势压倒了优势。 00:58:15.090 EN: And actually, they're also using the tools is a bit complicated because the tools are not primarily made for RDF XML, but they are made for XML. 中文初译: 事实上,他们也使用工具 有点复杂 因为工具不是主要为“RDF”“XML”制造的, 而是为“XML”制造的。 00:58:24.370 EN: And that's why you have to add something to the tools to really be able to process and to handle RDF inside XML. 中文初译: 这就是为什么你必须在工具上添加一些东西, 才能真正处理和在“XML”内处理“RDF”。 00:58:34.650 EN: And I would say it was even a mistake in the beginning of RDF. RDF was defined in 1998, and the W3 was adding a lot of pressure on only using XML for a long time. 中文初译: 我想说这甚至是一个错误 在“RDF”的开头。 “RDF”在1998年被定义, W3对只使用“XML”(XML(XML)) 施加了很长一段时间的压力。 00:58:49.010 EN: And I would say that was a bit a mistake because of these disadvantages. Meanwhile, these other serializations like Turtle, but also RDFa or JSON-LD become much more popular and they are easier to use, especially also for web applications. And now let's look at RDFa, which is very important because it allows to embed RDF into HTML and XML. 中文初译: 我要说,由于这些不利因素,这是一个有点错误。同时,其他的序列化,比如“Turtle”和“RDFa”或“JSON-LD”更受欢迎,更容易使用,特别是用于网络应用程序。现在让我们看看“RDFA”,这是非常重要的,因为它允许将“RDF”嵌入 HTML和“XML”中。 00:59:24.410 EN: RDFa stands for RDF in attributes. That's why the a, a like attributes and the embed that triples can be extracted from HTML. 中文初译: “ RDFA” 代表属性中的“ RDF ” 。 这就是为什么一个相似的属性和嵌入从 HTML 中提取的三倍。 00:59:38.210 EN: A problem of HTML of web pages is they contain text documents and formatting how the documents look like, right? 中文初译: 网页的 HTML 问题在于它们包含文本文档和格式化文件的样子,对吧? 00:59:47.930 EN: But we want to actually, or we want to process data and document formats like HTML are not suited for data. And that's why why this is so important that we can embed a data inside this document. 中文初译: 但我们实际上想要,或者我们想要处理像 HTML 那样的数据和文档格式,而HTML 不适合数据。这就是为什么这一点如此重要,以至于我们可以将一个数据嵌入到这份文件中的原因。 01:00:05.380 EN: And that's what RDFa allows. There can, you can use IRIs. And XML and HATML are typically encoded in Unicode. And there was another format which was doing it a bit similar, which was called microformats. 中文初译: 这就是“RDFA”允许的。 你可以使用“IRI ” 。 而“XML”和 HATML 通常在 Unicode 中编码。 还有另一种格式, 类似, 叫做微格式 。 01:00:26.200 EN: So RDFa is microformats done right for those of you who have heard about microformats. But if you haven't heard about it, you also don't have to because RDFa is actually much better than microformats. 中文初译: 所以“RDFA”是对于你们中那些听说过微格式的人来说, 微格式是正确的。但是如果你还没有听说过的话, 你不必这样做,因为“RDFA”其实比微格式要好得多。 01:00:41.560 EN: So here again, illustrating the motivation a bit. If we have a document on the left-hand side, that's what the browser, the software sees. Also a web crawler, right? 中文初译: 此处再次展示一下动机。如果我们左手边有一份文件, 那就是浏览器和软件所看到的。 也是网络搜索器, 对吧? 01:00:52.740 EN: So we search engines, for example, crawl the web, try to understand the web and then allow to search the web. And on the left-hand side, a search engine or a web browser, they just see, ah, there is a headline, there's a sub-headline, there's something italics, there's some text, there are some links. 中文初译: 因此我们搜索引擎,比如,爬过网络, 试图理解网络,然后允许搜索网络。在左手边,搜索引擎或者网络浏览器, 他们只是看到,啊,有一个标题,有一个小标题, 有斜体,有文字,有些链接。 01:01:14.840 EN: But what we humans see, we see, ah, the headline, that's actually the title of the document. We see the sub-headline, that's the author because it's a name. 中文初译: 但我们人类所看到的,我们可以看到,头条标题, 其实是文件的标题。我们看到子标题, 作者就是因为这是一个名字。 01:01:24.360 EN: And we see what is an italics below, that's actually a date, a publication date, right? So we can see the meaning of a document, but a crawler cannot understand that. 中文初译: 我们看到下面的斜体是什么, 实际上是一个日期,一个出版日期,对吗? 所以我们可以看到文件的含义, 但爬行者无法理解。 01:01:39.280 EN: We also see that some of the links, for example, are tags, which are used to classify the content. Another link is linking to a copyright license, yeah? 中文初译: 我们还看到,例如有些链接是用于对内容进行分类的标签。 另一个链接是与版权许可相联系的,是吗? 01:01:50.700 EN: So we humans can see that, but the machine doesn't understand that. Especially when you have prices, also prices of products, right? 中文初译: 所以,我们人类可以看到这一点,但机器不理解这一点。特别是当你有价格的时候, 产品的价格也是一样,对吧? 01:01:59.880 EN: So the machine cannot understand when you have on one page several products and prices, the crawler cannot understand, does the price belong to the product above or below? 中文初译: 所以机器无法理解 当你在一页上有几种产品和价格, 爬行者无法理解, 价格是否属于以上或以下产品? 01:02:11.800 EN: We recognize it because it's visually maybe closer to the product above, but a crawler cannot really see that and cannot really understand. 中文初译: 我们承认它,因为它在视觉上也许更接近上面的产品, 但是爬行者无法真正看到这一点, 也无法真正理解。 01:02:22.840 EN: And that's why it's so important to add the semantics to the HTML pages that crawlers machines understand the content of web pages as well. 中文初译: 这就是为什么在 HTML 页面中添加语义非常重要, 这样爬行机也能理解网页的内容。 01:02:34.680 EN: And that's what RDFA allows. And RDFA, or the most popular way how to do that is using the schema.org vocabulary. 中文初译: 这就是RDF允许的。和RDF,或者最流行的方法就是使用 schema.org 词汇。 01:02:47.690 EN: And that's initiative of the major search engine operators was started by Google, but also others are involved there, like Bing, Yandex, Baidu, Microsoft. 中文初译: 这是主要搜索引擎操作员的主动行动 是由谷歌发起的, 但还有其他人参与其中,例如宾、扬德克斯、拜都、微软。 01:03:04.920 EN: And it's a vocabulary for structuring the content, the data on web pages. For example, also about movies. So what the user sees is just such a description of the movie avatar, for example, we see there's a director, James Cameron. 中文初译: 这是构建内容的词汇表, 网页上的数据。例如, 有关电影的也一样。 因此用户所看到的 只是对电影阿凡达的描述, 比如说,我们看到有一个导演,詹姆斯·卡梅伦。 01:03:24.680 EN: He's born on August 16, 1954, and it's a science fiction movie. And then you have a link to the trailer, but for a search engine, it's very important to understand what the meaning of this information is. 中文初译: 他出生于1954年8月16日, 这是科幻小说电影。然后你和拖车有联系, 但是对于搜索引擎来说, 了解这些信息的含义是非常重要的。 01:03:39.980 EN: And schema.org is a vocabulary for allowing to encode this kind of information using RDFA in web pages. So when we look at HTML, and I think most of you should know HTML, this is what the browser sees. So we have a diff, for example, 中文初译: Schema.org是允许在网页上使用RDF编码这类信息的词汇表。所以当我们查看HTML时,我想你们大多数人应该知道HTML,这就是浏览器所看到的。例如,我们有一个 diff,例如, 01:04:09.690 EN: and we have a class movie, but the class attributes are only for telling the browser how to format this section here. 中文初译: 我们有一个班级电影,但类属性 只是为了告诉浏览器如何格式化这个部分。 01:04:20.270 EN: It's for assigning CSS cascading style sheets. And then we have a heading here, avatar. We have another class, James Cameron, and another class about the genre, and then the link to the trailer. So that's how the HTML looks like. 中文初译: 这是用来分配 CSS 级链样式表。 然后我们有一个标题, Avatar。 我们有另一个类, James Cameron, 还有另一个类, 关于流派, 然后是拖车的链接。 所以HTML就是这样看的。 01:04:41.230 EN: Now with RDFA, using the schema.org vocabulary, we can actually encode the meaning of it. So we add to the first diff, we add here that we use the vocabulary schema.org, and that the thing which we describe here is of type movie, type of movie. 中文初译: 现在,用RDFA,使用 schema.org 的词汇, 我们实际上可以编码它的含义。 所以我们在第一个 diff 中添加, 我们在这里补充我们使用 schema.org 的词汇, 我们在这里描述的是类型电影, 类型的电影。 01:05:07.490 EN: So the thing which is actually inside here describes a movie that says this attribute type of movie. Then we have the heading here, and we indicate that there is a property, and the property is name, and the name of the movie is avatar. 中文初译: 里面的东西实际上描述了一部描述这种属性类型的电影。 然后我们在这里有了标题, 我们指出有一个财产, 财产就是名字, 而电影的名字是阿凡达。 01:05:31.790 EN: Then we have another diff, and we say the relationship of what is described here in the second diff is a director relationship, and the type of this thing which is now defined is a person. 中文初译: 然后我们又有了另一个差异, 我们说第二个差异中描述的关系 是主任关系, 而现在定义的这种类型 是一个人。 01:05:53.320 EN: And then we actually have the name of the person here, and that's indicated by, we add the span here to indicate the string, which is the name of the person, and we add this property name to the span to indicate that this string here is an object, a literal, and the predicate is the name actually for this object. 中文初译: 然后我们这里实际上有这个人的名字, 上面写着, 我们在这里添加了横线来表示字符串, 也就是人的名字, 我们把这个属性的名称加到宽线上, 以表明这个字符串是一个对象, 一个字面的, 并且这个对象的谓词就是这个对象的名称。 01:06:22.840 EN: And the same we do with the birth date. Yeah, we again add a span around the actual birth date, which is written on the webpage here, the span. 中文初译: 和出生日期一样。是的,我们再次在实际出生日期前后加一个宽幅, 这个宽度写在这里的网页上。 01:06:32.300 EN: But what we do here is, yeah, we indicate that the property is birth date, but instead of using the string here as a literal, because the string is formatted for humans to read, August 16th, 1954, right? 中文初译: 但我们在这里做的是,是的,我们表示 财产是出生日期, 但是没有使用字符串 在这里作为字面上, 因为字符串是格式 供人类阅读,8月16日,1954年8月16日,对不对? 01:06:48.460 EN: There is even a space here before, so it's not a machine-readable representation of a date. And that's why we add the date actually here with the content attribute to this tag and identify the date according to the XML schema data type. 中文初译: 此处甚至有一个空格, 所以它不是一个机器可读的日期表示。 这就是为什么我们在这里添加日期, 加上此标记的内容属性, 并根据“ XML” schema 数据类型指定日期 。 01:07:09.060 EN: So this is the XML schema notation for date where you have the year, then the dash, then the month, a dash, and then the day. 中文初译: 这就是“XML”的图案符号 指您拥有年份的日期, 然后是破折号, 然后是月份, 一个破折号, 然后是一天。 01:07:18.840 EN: So you have four, five, six, 10 digits for a date. Then the diff ends, which describe the person, and then it basically continues again with the movie, and then we have the property genre. 中文初译: 所以,你有一个日期的4,5,6,10位数。然后是 diff 结尾,描述一个人, 然后它基本上又继续和电影一起进行, 然后我们有了属性的流派。 01:07:36.730 EN: So this is now applied again to the movie, and we have here science fiction. So here we use the same string, and we can also now add the language tag, E-N, to indicate that this literal here is in English. 中文初译: 因此,现在这又应用到这部电影上, 我们在这里有科幻小说。所以我们在这里使用同样的字符串, 现在我们也可以添加语言标签E-N, 来表示这个字面是英语。 01:07:55.160 EN: And last, we have another property, created another, like the subject is the movie, the predicate is now a trailer, and the object is the URI of the trailer, yeah? 中文初译: 最后,我们有另一个财产, 创造了另一个, 就像主题是电影, 上游现在是拖车, 物体是"URI"的拖车,是吗? 01:08:13.220 EN: So links also become statements, subject predicate object statements. So links typically indicate you have a link from a webpage to another webpage, right? 中文初译: 因此链接也成为声明, 主题的上游物体声明。 所以链接通常表示您有从网页到另一个网页的链接, 对吗? 01:08:24.660 EN: So the from webpage can be the subject, the another webpage can be the object. But what we typically don't have in the link is the property, yeah, the predicate of the triple. 中文初译: 因此,从网页上可以找到主题, 另一个网页也可以找到对象。 但是我们通常没有链接到的 是属性,是的,三重的谓词。 01:08:34.680 EN: And that's why the predicate is added here with this rel tag, the rel indicates the property. So, and now we have basically added to our snippet, that's how it looked like before. 中文初译: 这就是为什么在这里添加了上层的标签, 上层的标记代表着属性。所以,现在我们基本上已经增加了我们的片段, 这就是它以前看起来的样子。 01:08:53.730 EN: And on the webpage, it looks exactly the same. Everything which we have added was diff and spans and attributes. 中文初译: 在网页上,它看起来完全一样。我们加到的所有东西都是 diff, 横幅和属性。 01:09:00.730 EN: So these are invisible HTML tags, they are not visible. So it looks on the webpage exactly the same, but the difference is that now a machine can understand what's going on, what's represented on the webpage, what's the data. 中文初译: 这些是看不见的 HTML 标记, 它们不可见。 所以它看网页上完全一样, 但区别在于机器现在可以理解 正在发生的事情,在网页上代表什么, 数据是什么。 01:09:15.010 EN: And that's very important. And only because of that, Google can search for restaurants, for example, or for certain things. 中文初译: 这一点非常重要。因为这个,谷歌可以搜索餐馆, 比如说,或者某些东西。 01:09:25.670 EN: So if you use a Google search, let's say, I don't know, Piccolo, let's look for something, a small restaurant, which I know, this one here. 中文初译: 所以如果你用谷歌搜索的话, 比方说,我不知道,皮科洛, 让我们找点东西, 一个小餐厅,我知道,这个在这里。 01:09:41.780 EN: On the right hand side in the Google search, you see information, yeah, data basically. So you have the address here, you have the opening hours there, yeah. 中文初译: 在谷歌搜索的右手侧, 你看到信息, 是的, 数据基本上。 所以这里有地址, 你在那里有开放时间,是的。 01:09:58.760 EN: What else do we have? You have question and answers, you have reviews. So you have a lot of information about the website. 中文初译: 我们还有什么呢?你有问题和答案,有评论。所以你有很多网站的信息。 01:10:06.180 EN: You have the geo-coordinates, you have indicated it on the map here. You have images, you have a categorization that's an Italian restaurant. 中文初译: 您有地理坐标, 您在这里的地图上表明了这一点。 您有图像, 您有一个分类是意大利餐厅 。 01:10:18.120 EN: Where do you think this comes from? And this comes from the website of the restaurants because they represent information in this way, in RDFA. 中文初译: 你认为这是从哪里来的?这个来自餐厅的网站, 因为他们以这种方式在RDF中代表信息。 01:10:30.240 EN: On the webpage. Otherwise, Google could not understand that well what's going on on these webpages. So for our movie example, we now have here how it looks like as a graph. 中文初译: 在网页上。 否则,谷歌无法理解这些网页上发生的事情。所以我们电影的例子, 我们现在有它看起来像一个图表。 01:10:50.180 EN: So we have a movie that one problem is a bit, we have not an identifier for the subject. You actually have maybe ask yourself, what's the subject? 中文初译: 所以我们有一部电影,其中有一个问题有点, 我们没有关于这个主题的识别符号。你也许可以问自己, 主题是什么? 01:11:01.600 EN: And the subject is actually not contained in the document itself. We just know it's a description about a movie, but we don't have an identifier for the subject. 中文初译: 主题实际上并没有包含在文件本身中。我们只是知道它是一个关于电影的描述, 但我们没有这个主题的识别符号。 01:11:13.640 EN: That's why we have actually here a blank note, yeah. We just know this is something and the something is a movie, yeah. 中文初译: 这就是为什么我们实际上在这里有一个空白的音符,是的。我们只是知道这是某种东西,而东西是一部电影,是的。 01:11:20.860 EN: That's what this here says. Type of movie, that's basically indicating this statement. The next one is name avatar. 中文初译: 这就是这里所说的。电影类型,基本上就是这个声明。下一个是阿凡达的名字。 01:11:31.480 EN: So this is basically the second statement here. Then we have director. Again, a link to a director, but we don't have a concrete subject. 中文初译: 基本上,这是这里的第二个声明。然后我们有了导演。再次,一个与导演的联系, 但我们没有具体的主题。 01:11:44.620 EN: That's why it's again a blank note here. Yeah, a note without an identifier. The director is, we have type of person. 中文初译: 这也是为什么这里又是一张空白的纸条。是的,一个没有识别资料的纸条。导演是,我们有种人。 01:11:52.640 EN: So it's basically a person here. Then we have the name. James Cameron is the second statement about the director and we have the birth date. 中文初译: 詹姆斯·卡梅伦是第二个关于导演的声明,我们有出生日期。 01:12:02.640 EN: And that's the third statement of the director. And then we go back again to the movie and we have the genre. And that's exactly what is this statement here, science fiction genre. 中文初译: 这是导演的第三个声明。然后我们又回到电影里, 我们有了这种风格。这就是这个声明, 科幻小说。 01:12:15.220 EN: Can you actually see my cursor? I think I can also draw here. Yeah, here you see the genre. And finally, the last, the trailer link creates another statement here, a link to the trailer. 中文初译: 你能看到我的光标吗?我想我也可以在这里画图。是的,这里你可以看到模式。最后,最后一个,拖车链路 创造了另一个声明,一个与拖车的链接。 01:12:41.440 EN: So, and there is also a service RDF play, RDF A play. And there you can try this out and you can actually create some examples and play around with it. 中文初译: 所以,还有一个服务“RDF”的游戏,“RDF”的游戏。在那里你可以尝试一下这个, 你可以创造一些例子, 并玩弄它。 01:12:56.760 EN: And you can copy and paste RDF A here. And then it basically shows you the graph. It's a nice tool for RDF A. So then some more examples, schema.org. 中文初译: 您可以在这里复制并粘贴“ RDF” A 。 然后它基本上展示了图表。 这是一个很好的工具,用于“ RDF” A 。 所以,然后还有一些例子, schema.org 。 01:13:21.080 EN: Maybe I'll also show you schema.org. You can go to the website schema.org and it looks very modest, but it's one of the most important or the most important vocabulary for the web. 中文初译: org。你可以去网站 schema.org,它看起来很谦虚, 但是它是网络最重要的或最重要的词汇之一。 01:13:38.770 EN: If you click on schemas on top, you see a number of these, they call it schemas, basically definition of how you can define things. 中文初译: 如果你点击上方的图案, 你会看到其中的一些图案, 他们称之为图案, 基本定义如何定义事物。 01:13:50.290 EN: And here, for example, creative works, we have movie, we can click on movie and then we get a list of the properties and the expected pipes you can use for movie. 中文初译: 例如,在这里,创意作品, 我们有电影, 我们可以点击电影, 然后我们得到一个清单 属性和预期管道 你可以用在电影中。 01:14:02.420 EN: And you see there is much more than just the director and the birth date. And you can scroll down and then you can also look at examples and RDF A examples. 中文初译: 你可以看到的不仅仅是导演和出生日期。 你可以滚动下来,然后你也可以看一些例子和“RDF”的例子。 01:14:14.700 EN: For example, this one here. So here we have a bit more complex example about JAWS 3D, location that it's movie theaters defined here and so on. 中文初译: 例如,这里的这个。这里我们有一个比较复杂的例子 有关JAWS 3D, 它的位置是在这里定义的电影院等等。 01:14:28.960 EN: So we could, for example, copy this and go to RDF A play just to, so we copy this in here. We see how it's rendered as a webpage on the right hand side. 中文初译: 例如,我们可以复制这个,然后直接去“RDF”的剧本, 所以我们在这里复制这个。我们看看它是如何在右手边作为一个网页提供的。 01:14:43.250 EN: And let's look on the buttons. We see how the graph, the RDF graph actually looks like there is an item, it's a screening event. 中文初译: 让我们看看这些按钮。我们可以看到图表,RDF的图形 看上去就像有一个项目,这是一个放映活动。 01:14:54.430 EN: The name is JAWS 3D. The description is JAWS 3D shown in 3D. Then it has a location, which is a movie theater. It has 10 screens and there is another location, another movie theater, I know, work presented. 中文初译: 名为 JAWS 3D。 描述是 3D 中显示的 JAWS 3D。 然后它有一个位置, 是一个电影院。 它有10个屏幕, 还有另一个地方, 另一个电影院, 我知道, 展示了工作 。 01:15:15.950 EN: This is actually the movie itself and that's the JAWS 3D movie. And then also the language and the video format can be added. 中文初译: 这其实是电影本身和JAWS 3D电影。然后语言和视频格式也可以添加。 01:15:25.830 EN: So here we can nicely then see and play around with such examples. And that's also something you should be able to do for the exam. 中文初译: 因此在这里,我们可以很好地看到和玩弄这些例子。这也是你应该能够做的考试。 01:15:37.040 EN: That's also sometimes an exam question we have. We give you an RDF A snippet like this one and you should draw us the graph. 中文初译: 这有时也是我们的考试问题。我们给了你一个“RDF”这样的片段,你应该给我们画图。 01:15:50.800 EN: So schema.org also allows review or ratings of creative works of organizations or products, which are written by persons usually. 中文初译: Schema.org也允许对通常由个人撰写的组织或产品的创作作品进行审查或评分。 01:16:03.140 EN: And also you can represent social networks, a person knows, works for, is colleague of, has parents, siblings, spouse, child, relative. 中文初译: 您也可以代表社会网络, 一个人知道,工作, 是同事, 有父母,兄弟姐妹,配偶,孩子,亲戚。 01:16:12.720 EN: All these things can be represented in RDF A or also in a movie. So here we have Avatar is a movie and it has reviews and the review rating value is six. 中文初译: 所有这些东西都可以在“RDF” A 或电影中出现。所以我们这里的Avatar是一部电影,它有评论,审查评级值是6。 01:16:25.860 EN: This is the average rating, but then we have also concrete author of a review. His name is Peng Chen and he is a person and he knows someone else who is Anton, who is also a person. 中文初译: 这是平均评分,但我们也有具体的评论作者。他的名字叫彭陈,他是一个人,他认识另一个人也是安东,也是一个人。 01:16:41.100 EN: And this is actually another rating that's not the average rating. It's the rating of this particular author and the other author Anton gave the movie an 8.5. 中文初译: 这其实是另一个不是平均评分的评级。这是这个作者的评级, 另一个作者Anton给了电影8.5。 01:16:51.280 EN: So you can represent this information also in RDF A using the schema.org vocabulary. And that's why when you enter Avatar in the search engine it actually shows us the result and we have this information on the right hand side. 中文初译: 所以您也可以使用 schema.org 词汇表在“ RDF” A 中代表这些信息。 这就是为什么当您输入 Avatar 进入搜索引擎时, 它向我们展示了结果, 我们在右手边有这个信息 。 01:17:13.500 EN: We have actually the ratings here. We have the release date, we have the director, the budget and so on. And all this information Google adds to its knowledge graph. 中文初译: 事实上,我们这里有收视率。我们有发布日期,有主任,预算等等。所有这些信息都加到谷歌的知识图中。 01:17:24.780 EN: Google operates probably the largest knowledge graph in the world, like a large RDF or a semantic database. And they populate this knowledge graph by crawling information from a lot of web pages. 中文初译: 谷歌可能是世界上最大的知识图,比如一个大型的“RDF ” 或语义数据库。它们通过从许多网页上收集信息的方式将这一知识图投放其中。 01:17:41.700 EN: Also creating it manually. They also have people creating it. So some information is also manually verified and added to the knowledge graph, but only because you can express information, encode information on web pages using RDF A. 中文初译: 手动创建它。 他们也有人创建它。 所以有些信息也是人工验证的, 并添加到知识图中, 但仅仅因为您能用“ RDF” A 在网页上表达信息, 编码信息 。 01:17:59.560 EN: This becomes more possible on such a large scale. Yeah, and then there are queries. Yeah, maybe that's for today. Maybe we do the still the queries. 中文初译: 这在如此庞大的规模上变得更有可能。是的,然后还有查询。也许这是今天的事。也许我们还是做这些查询吧。 01:18:22.640 EN: So what are queries? So we need an RDF A of course, also mappings from prefixes to URIs. And that can be done by in scope prefix declaration. 中文初译: 那么,什么是查询?所以我们当然需要一个“RDF” A, 还要从前缀到“URI”进行绘图。这可以通过范围前缀声明来完成。 01:18:40.080 EN: And then parsing them. And so there is always a default prefix mapping and the mapping to use when there is no prefix, when there's no prefix defined in RDF A is this default prefix. 中文初译: 然后解析它们。所以总是有一个默认的前缀映射和绘图, 当没有前缀时使用, 当“ RDF” A 没有定义前缀时, 这个默认的前缀就是这个默认的前缀 。 01:19:20.190 EN: So, but there are done in this queries basically define compact URIs, allow us to define compact URIs. So, and here is basically how this is done. 中文初译: 所以,但是在这样的询问中,我们做了一些基本定义了“URIs ” , 让我们来定义“URIs ” 。 因此,这里基本上就是这样做的方式。 01:19:34.030 EN: So we can, these queries compact URIs are short notation for URIs. And there is a prefix usually assigned and then we can define such a compact URI using a prefix, a colon and then a reference. 中文初译: 所以我们可以, 这些询问“ URI ” 是“ URI ” 的缩略语。 通常会指定一个前缀, 然后我们可以使用前缀、 结肠和引用来定义这样的“ URI ” 。 01:19:58.630 EN: So it's basically the same as what we have seen in Turtle and N3 with the namespace prefixes. So the same we can use here in RDF A as well and define basically short URIs to use inside a document. 中文初译: 因此它基本上和我们在“ Turtle” 和 N3 中看到的那样一样, 带有命名空间前缀。 所以我们也可以在“ RDF” A 中使用同样的符号, 并定义一个文档中的简称“URIs ” 。 01:20:20.430 EN: And maybe let's look at some examples. Yeah, basically we see the namespace prefixes defined here in the HTML tag. 中文初译: 也许让我们来看看一些例子。 是的,我们基本上看到在 HTML 标记中定义的命名空间前缀。 01:20:38.400 EN: So this is the tag surrounding the whole HTML document. And there we have the namespace declarations and then we can use these namespaces inside the attribute values. 中文初译: 这就是围绕整个 HTML 文档的标签。 我们在这里有了命名空间声明, 然后我们可以在属性值中使用这些命名空间。 01:20:52.220 EN: So for example, here in this, in the body tag, we have the about attribute. So that means that we now have defined a URI which is the subject of all triples and we use DBR colon lib3. 中文初译: 例如,在这里,在身体标签中,我们有关于属性的标记。这意味着我们现在定义了“URI”,这是所有三重主题的主题,我们使用DBR 冒号3。 01:21:12.020 EN: So that's basically a compact URI which uses the DBR namespace here, dbpediorg slash resource. So we can resolve this to a URI and then use it as a subject for the triples inside this document. 中文初译: 基本上,这是一个紧凑的“ URI ” , 它使用 DBR 命名空间, dbpediorg slash 资源。 这样我们就可以用“ URI ” 来解决这个问题, 然后把它用作此文档中三重内容的主题 。 01:21:31.760 EN: And the same, then this is the subject. Then we have a property here, RDFS label. And the object of this property is Leipzig with the language tag de. 中文初译: 同样,这就是主题。然后我们在这里有一个属性,“RDFS”标签。这个属性的客体是莱比锡,上面有语言标记。 01:21:44.290 EN: And then we have in another paragraph encoded the latitude and the longitude, and both have the data type float, but here the values are directly taken from the HTML strings. 中文初译: 然后我们在另一个段落中编码了纬度和经度, 两者都有数据类型浮动, 但这里的数值直接取自 HTML 字符串 。 01:22:04.130 EN: And these are then the object of the respective latitude and longitude triples with latitude and longitude property or predicate. 中文初译: 然后这些是各自的纬度和经度三倍的物体, 具有纬度和经度属性或上游。 01:22:17.080 EN: So here in that case, we actually have indicated a concrete subject. It's about dbpediorg resource Leipzig. So we indicated the subject itself, but this could be also omitted. 中文初译: 因此,在这个例子中,我们实际上已经指明了一个具体的主题。它是关于 dbpediorg 资源 Leipzig 的。 所以我们表明了这个主题本身, 但也可以忽略这一点 。 01:22:31.400 EN: If this is not there, then an empty subject would be created and that's exactly this blank notes which we have seen in the avatar. 中文初译: 如果不存在,那么空主题就会被创造出来 这正是我们在阿凡达看到的空白音符 01:22:40.600 EN: Then it would be something like some resource which is not uniquely identified, which is just identified by such a blank note, but still we could say it's a city, for example, it has the name Leipzig and that's what happened in the avatar movie. 中文初译: 然后,它就会像某种资源 它不是独特的识别, 只是被一个空白的字条所识别, 但我们仍然可以说这是一个城市, 比如说,它的名字叫Leipzig, 这就是发生在阿凡达电影里的事情。 01:23:01.920 EN: So in RDFa, and that's important, we don't have to explicitly define the subject. If the subject is not explicitly defined, a blank note, an empty note basically is generated. 中文初译: 所以在“RDFA”中,这很重要, 我们不需要对主题做出明确的定义。 如果主题没有被明确定义, 空白便条, 空便条基本上就产生了。 01:23:15.400 EN: That's important aspect and that actually happens quite often. For example, here in that case, so this movie we just know that this something has a type and the type is a screening event, but we don't have identified an identifier for the subject here. 中文初译: 这是一个重要的方面,而且实际上经常发生。例如,在这样的情况下,这个电影, 我们只知道它有一种类型, 是一种筛选活动, 但是我们没有为这个主题找到一个识别符。 01:23:39.620 EN: That's why also in this RDF play, we just have item one and item two, for example here, and item three. So these are just arbitrary blank note identifiers for these items because nothing is given directly in the webpage content itself. 中文初译: 这也是为什么在这个“RDF”游戏中,我们只有项目1和项目2,例如这里,还有项目3。所以这些只是这些物品的任意空白笔记识别符号, 因为网页内容本身没有直接给出任何信息。 01:24:02.980 EN: Now, and as I said, on schema.org, you can see a lot of properties. Of course, we need to identify what can be used. 中文初译: 现在,正如我所说,在 schema.org上,你可以看到很多特性。当然,我们需要确定什么可以使用。 01:24:10.640 EN: For example, here we have this geo let, geo long, or the label. So these kind of properties, they need to be identified, and that's what schema.org allows. 中文初译: 例如,我们这里有这个地理放行、地理长或标签。所以这些属性需要被识别, 这是 schema.org 允许的。 01:24:23.460 EN: It basically defines the properties because every webpage author, if they would use different properties, again, we could not use it. 中文初译: 它基本上界定了财产,因为每一个网页作者,如果他们使用不同的财产,我们也不能使用它。 01:24:32.780 EN: It needs to be defined which properties to use, and that's exactly what schema.org is about, defining properties you can use to describe things on the web. 中文初译: 需要定义要使用的属性, 这正是 schema. org 的本质, 定义您可以用来描述网络上的东西的属性。 01:24:44.110 EN: And here in that case, we have seen that for movies, and you can look a bit around. It became, meanwhile, very detailed. 中文初译: 在这样的情况下,我们看到了电影的景象 你可以四处看看。与此同时,它变得非常详细 01:24:50.360 EN: So there are a lot of possibilities how to describe movies, and that not only exists for movies, but there are a lot of other classes or other possibilities. 中文初译: 所以有很多描述电影的可能性, 不仅存在于电影中, 而且还有很多其他的类别或其他可能性。 01:25:02.640 EN: So we have here creative works, which includes also music recording, TV series. We have events. We have organizations. 中文初译: 因此,我们这里有创意作品, 包括音乐录制、电视系列。 我们有活动。我们有组织。 01:25:13.740 EN: We have persons. We have places, businesses, restaurants, products, offers, reviews, actions, and so on. So you can look around a bit on schema.org and familiarize yourself with that. 中文初译: 我们有个人。我们有地方, 商业,餐馆,产品,提供, 评论,行动等等。所以你可以看看周围的 schema.org 并熟悉一下这个。 01:25:29.660 EN: Okay, so with that, I would like to end today's lecture. Thank you very much for joining today. 中文初译: 好了,这样的话,我想结束今天的演讲,非常感谢你们参加今天的会议。