W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

ldp-ISSUE-9 (Properties in BPR representations): Should properties used in BPR representations be BPRs? [Linked Data Platform core]

From: LDP <sysbot+tracker@w3.org>
Date: Tue, 02 Oct 2012 14:12:15 +0000
Message-Id: <E1TJ3Cp-00033g-Mg@tibor.w3.org>
To: public-ldp-wg@w3.org
ldp-ISSUE-9 (Properties in BPR representations): Should properties used in BPR representations be BPRs? [Linked Data Platform core]

http://www.w3.org/2012/ldp/track/issues/9

Raised by: Raúl García Castro
On product: Linked Data Platform core

"4.1.8 Predicate URIs used in BPR representations should be HTTP URLs. These predicate URIs must identify BPRs whose representations are retrievable. BPR servers should provide an RDF Schema [RDF-SCHEMA] representation of these predicates."

I understand that predicate URIs SHOULD be HTTP URLs.

But saying that "These predicate URIs MUST identify BPRs whose representations are retrievable", implies that the properties MUST be BPRs and, therefore, MUST be HTTP resources and, therefore, MUST be identified by HTTP URLs.

However, before, it is written that "SHOULD be HTTP URLs".
Am I missing something here?


I also disagree with the fact that properties are BPRs.

It is a common practice to reuse properties from vocabularies that you don't own. Therefore, you don't have any control about them (for example, the rdf:type property).

I think that the restriction here could be that "These predicate URIs MAY identify BPRs whose representations are retrievable".

And, then, also change the last sentence to: "BPR servers MAY provide an RDF Schema [RDF-SCHEMA] representation of these predicates." (even if we don't mention how, should we?).
Received on Tuesday, 2 October 2012 14:12:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC