WoT Models - document & payloads pushed to github

Hi all, 

as discussed this/last week, we have pushed to the Github 2 elements today:

1. The WoT Standard Recommendation
The latest snapshot of the WoT recommendation (bt.ly/wot-label). It's not the "final" one, but it's been the one we got comments on for a while and used as a working document for everyone to feedback on. As not everyone had access to it, we decided to PDF it for you to see, and it's both available in github: https://github.com/w3c/wot/tree/master/TF-AP <https://github.com/w3c/wot/tree/master/TF-AP> (WoT-Label v0.1.pdf) and attached in this mail. It contains our current thinking and plan, so *please* let us know your comments/suggestions on how we can improve this. 

We will send a shorter/crispier/refined version of this document by the end of this week (still in PDF/Word), which we'll use as basis to formulate an initial submission to the W3C. The goal of this is have an initial technical basis that the IG can built upon and improve over time.

François will be taking care of converting this initial submission into an HTML document that will live in our Github and we all can use as "master" reference document. Although, there were suggestions to convert this into markdown (easier to manage/manipulate), and as much as I'd prefer this, at the end of the day the outcome for w3c will have to be in their standard HTML style, and I don't think François will be thrilled to keep migrating changes from a markdown document into an HTML document manually. 

If someone is willing to write a "Github markdown-to-W3C-compliant-HTML" automated converter, then of course would be best to keep the "master as markdown"

2. JSON Payloads examples
You will also find in the Github JSON sample + models of the various things, resources, actions, etc. (https://github.com/w3c/wot/tree/master/TF-AP/JSON%20Payloads <https://github.com/w3c/wot/tree/master/TF-AP/JSON%20Payloads>) that you're welcome to comment on (but please let me know before you change those, e.g. using pull requests, so we can keep the changes of those documents organized process). 

I'm planning to add readme.mds for those over the next few days, so that this repository becomes a stand-alone useful resource we can point people to and enrich (e.g. for coap people to drop coap-specific examples/encodings of those, same for JSON-LD augmented versions of it, etc.).  

It's clearly not complete, but I believe it's an useful first step towards having a solid basis upon which we can build further. 

Feedback/thoughts/suggestions very welcome!

Thanks, 

Vlad