RDF 303重定向说明 [英] RDF 303 redirect clarification

问题描述

我想确认有关303重定向协议含义的一些信息.

I'd like to confirm something about the 303 redirect protocol implication.

如果出于灵活性的目的，确实遵循使用斜杠URI而不是哈希URI来构建RDF(相对于词汇的资源/实例文件)的惯例，这是否意味着每个资源实例都必须定义一个重定向(如果我们需要它们，令人讨厌的)?意味着我们必须使用purl定义303重定向，以便将每个资源重定向到我们认为合适的相同或不同文件?

If one does follow the convention of building RDF (resources/instances file as opposed to vocabularies) using slash URI instead of hash URI for flexibility purpose, does it mean that each resource instance must have a redirect defined (if we want them dereferencable)? Meaning we must define with purl a 303 redirect for each resource to either the same or different file as we see fit?

此外，有人可以告诉我信息资源和非信息资源(也称为现实世界对象)之间的区别是什么?更具体地说，资源描述框架不代表信息资源描述框架吗?也许对网络上的资源有一个更好的解释会有所帮助.

Also, along the way can someone tell me what is the difference between an information resource and a non-information resource (also called real world object)? More specifically, does not Resource Description Framework stand for Information Resource Description Framework? Maybe a better explanation of what is a resource on the web would help.

有人可以帮助澄清这些概念吗?

Can someone help clarify those concepts?

推荐答案

您可以将信息资源视为 Web文档 ， 非信息资源作为 事物 . (不是定义，只是为了让您有个大概的想法.)

You could think of information resource as Web document, and of non-information resource as thing. (Not a definition, just so you get a rough idea.)

我试图解释此答案中的区别:

I tried to explain the difference in this answer:

HTTP URI可以标识页面本身或该页面所涉及的内容.您不能仅仅通过查看URI就能识别出页面或事物.

a HTTP URI could identify the page itself OR the thing the page is about. You can't tell if an URI identifies the page or the thing by simply looking at it.

示例(采用Turtle语法):

Example (in Turtle syntax):

<http://en.wikipedia.org/wiki/The_Lord_of_the_Rings> ex:author "John Doe"

该可以表示具有URI http://en.wikipedia.org/wiki/The_Lord_of_the_Rings的HTML页面是由"John Doe"创作的.或可能意味着该HTML页面(→小说)所描述的内容是由"John Doe"创作的.

This could mean that the HTML page with the URI http://en.wikipedia.org/wiki/The_Lord_of_the_Rings is authored by "John Doe". Or it could mean that the thing described by that HTML page (→ the novel) is authored by "John Doe".

这是一个好习惯，可以让其他人在重用您的URI或数据时可以区分这一点.但是，这不是必需的.有些人认为这不是问题，也不值得付出努力.

It’s a good practice to make it possible that others can differentiate this when re-using your URIs or your data. However, this is not required; some think that this is a non-issue or not worth the effort.

关于这种区分的讨论称为 httpRange-14问题(" HTTP取消引用功能的范围是什么?").

The discussion about this differentiation is known as the httpRange-14 issue ("What is the range of the HTTP dereference function?").

一些可能的解决方案是:

Some possible solutions are:

• 哈希URI (请参见此答案中的示例)
• 303个URI (请参见此答案中的DBpedia示例)
• 属性类别(不是很新，可能不太知名；请参阅我的问题，并带有简要说明)

• Hash URIs (see example in this answer)
• 303 URIs (see DBpedia example in this answer)
• Property categories (rather new and probably not well-known; see my question with a brief explanation)

因此，当您使用斜杠URI"并且关心差异(我认为应该这样做)时，是的，您将必须使用303重定向.

So when you use "slash URIs", and you care about the differentiation (and I think you should!), then yes, you would have to use a 303 redirect.

否则，如果您发送200，则所有遵循

Otherwise (if you’d send 200), all user agents that follow TAG’s resolution would think that your URI identifies an information resource.

这篇关于RDF 303重定向说明的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！