- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 10 Feb 2014 16:27:02 -0500
- To: public-vocabs@w3.org
- Message-ID: <52F94426.9070007@openlinksw.com>
On 2/10/14 3:00 PM, Sam Goto wrote: > Thus we probably need an alternative for the time being. One option > would be (as I mentioned to you in another mail) to separately > describe Web resources and "app resources". How about distinguishing Web Resources and Web Services (instead of "app resources") ? The crux of the matter here is that we have a Service and its distinguishing characteristics. Making these characteristics discernible and comprehensible to user agents is the challenge at hand. Ultimately, we are going to either describe URI templates using RDF documents or they are going to exist as literal relation values for which user agents (as many do today) will have to learn about via API docs. If we don't want to be too RDF heavy, then look to the fact that the URI template language is an open standard that has been implemented by a number of folks. [1] http://tools.ietf.org/html/rfc6570 -- URI Template [2] http://shuyo.wordpress.com/2008/07/24/implementations-of-uri-templates-in-various-languages/ -- old implementors list (we [OpenLink Software] for instance are missing from the list) . -- 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 Monday, 10 February 2014 21:27:27 UTC