Questions regarding best practice: Use fragments as entity identifiers

Team,

I could use a little help fleshing out a spot in the LDP Best Practices and
Guidelines.

One of the recommendations in the Deployment Guide was written in the wiki
as follows:

---
*Use fragments as entity identifiers*

Fragments are nice because they can be expressed as relative URIs on the
document describing them.
---

I'm not sure who first wrote that, but if you could provide me with more
detail, it would be helpful. Or anybody, for that matter.

I understand the use of fragments in RDF. It's how I define properties on
an Instance in OWL, for example. If I have a representation of a Person
(Instance of Person), the fragment #hasName represents the hasName property
of that Person which may or may not be defined in the same RDF document.

But is it really a Best Practice? Or simply a Guideline? There is some
somewhat confusing debate on the web.

Also, can you represent why it is a useful practice using an example
representation of a resource?

What do you think we really need to say here to make this point a little
more meaningful?



-- 
Cody Burleson