- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 04 Feb 2014 11:22:42 -0500
- To: public-hydra@w3.org
- Message-ID: <52F113D2.9030202@openlinksw.com>
On 2/4/14 10:39 AM, Markus Lanthaler wrote: > OK, this is the second thread. This one is trying to find an answer to the > following question: > > "Should hydra:returns and hydra:statusCodes be removed to avoid tight > coupling?" - ISSUE-32 It is also much easier if you use full URIs instead of prefixes. Then you can state: "Should <http://www.w3.org/ns/hydra/core#returns> and <http://www.w3.org/ns/hydra/core#statusCodes> be removed to avoid tight coupling?" - ISSUE-32. I am then just a click away (no visits to prefix.cc etc..) from de-referencing the description of what those URIs denote. BTW -- what system is actually being used for issue tracking? Is it a W3C issue tracker of Github issue tracker ? -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 4 February 2014 16:23:04 UTC