ldp-ISSUE-8 (Removing Profile): Better define or just not use the "Basic profile" terminology [Linked Data Platform core]

ldp-ISSUE-8 (Removing Profile): Better define or just not use the "Basic profile" terminology [Linked Data Platform core]

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

Raised by: Olivier Berger
On product: Linked Data Platform core

The term "Basic Profile" is quite central to the editor's draft for the moment.

However, one has to really notice the "profile" definition to understand that a profile is a specification. Then of course, it makes sense to have the current LDP core specification called "basic profile".

However, maybe due to the popularity of Web 2 sites and other social networking platforms, "profile" can be misunderstood as "user profile", i.e. an identity or other set of characteristics.

I'm afraid the use of profile here is ambiguous for potential implementers who may not have followed the WG work. And it gets worse with (LD) "Basic Profile Resource" which could be understood as a basic "Profile Resource" (a user profile described by a HTTP Resource, i.e. WebID ?) :-/

Shouldn't we either at least define "basic profile" in a very prominent place in the document, or get rid of it and speak of "Linked Data Basic Specification" which is more explicit.

Then BPRs could become something else : Core REST Resources, Core Linked Data Resources, or whatever else that doesn't contain Profile.

I think this is really central if we want to make sure the standardization that is seeked can really deliver to the very many REST services implementers that should become enlightened by the Linked Data approach (read all the AJAX services out there of the Web 2 ecosystem).

Received on Friday, 28 September 2012 14:58:40 UTC