- From: Asbjørn Ulsberg via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Jan 2017 08:55:51 +0000
- To: public-hydra-logs@w3.org
While I agree that we can and should flesh out Hydra's requirements and test them in the real world before moving the HTTP terms to its own vocabulary, I think the friction involved in doing this after Hydra has reached 1.0 REC status is so huge that it's probably not worth it. With enough implementations, moving to an external vocabulary would amount to a lot of friction as well, but as long as we do it before we reach Recommendation status, it's at least to expect that things change, but after 1.0 REC, we would have to wait for 2.0 REC to do anything about this. Perhaps that's the right course to take -- I don't know. But I would like to attempt making the move before 1.0, if possible. -- GitHub Notification of comment by asbjornu Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/109#issuecomment-270859445 using your GitHub account
Received on Friday, 6 January 2017 08:55:57 UTC