VoID Requirement from Kjetil Kjernsmo on 2014-10-12 (public-hydra@w3.org from October 2014)

From: Kjetil Kjernsmo <kjetil@kjernsmo.net>
Date: Sun, 12 Oct 2014 17:59:55 +0200
To: public-hydra@w3.org
Message-Id: <201410121759.55222.kjetil@kjernsmo.net>

All,

I think I'm about to require people to enable a VoID description in my TPF 
implementation. I already offer an optional VoID generator, so for this 
implementation, it shouldn't be a big deal for my users if they actually had 
to enable it to use the TPF. 

Given that, I was wondering if any of you would think such a requirement is 
a Bad Idea[tm]?

Apart from the control returned with every fragment, it is also a nice place 
to go looking for control, and its URI is also the subject of the 
collection. Therefore, I was thinking that perhaps a VoID description should 
be a SHOULD in the TPF spec?

Cheers,

Kjetil

Received on Sunday, 12 October 2014 16:00:38 UTC