LDP Resource description

[DiegoPino]

Each resource will be characterized by an object derived from the same interface.
Persistent storage will be handled by another class/classes. The idea is that a Resource Definition itself and any Storage related tasks can be handled as completely different things. Moreover, storage can be implemented as a collection of different strategies and driven by rules.

Each of this objects will handle an unique hash as ID, an URL as seconday ID a native mime-type for its payload, a few timestamps, the payload itself and a LDP Resource Class description.