TPF/LDF - why the explicit coupling with Hydra?

LDF is a conceptual framework and TPF is just one possible (Hydra-based)
implementation for LDF. Given that there are many things that could be
implemented (or proposed) using Hydra semantics, why the explicit
side-by-side promotion of LDF and TPF on the Hydra website? The
presentational style suggests that to know Hydra, one should also
understand LDF and TPF, which doesn't seem to be the case to me after
looking deeper. Is there something about LDF/TPF that I have missed as
being fundamental to correct use of Hydra? Or is it more the intention that
if Hydra catches on in the greater semweb community, that LDF/TPF would be
relegated to a subsection along with other equally-useful proposals and
specifications which are derived from or implemented with Hydra? Note that
this is not an attack on LDF/TPF, I just don't quite understand why the two
are presented in a style that suggests that they're implicitly coupled
somehow.

Nathan

-- 
*Google*: axefrog@gmail.com
*Skype*: axefrog
*Twitter*: @NathanRidley
*Website*: http://axefrog.com / http://nathanridley.com
*Phone: *+61 (0) 475 072789