ACTION-586: Updating client-side state to deal with document identity

Ashok:

As we agreed, I've forked a version of the client-side state draft and 
added suggested edits to highlight the importance of assigning URIs to 
documents in Web Applications. In keeping with Larry's suggestion, I've 
framed things in terms of positive advice on using URIs.

I also tweaked the Abstract to remove some of the emphasis on # syntax, and 
I made a few clerical changes, such as adding the missing Table of Contents 
entries for chapter 6. I think we could still do more to improve the focus 
and the wording of the abstract, but the main point of this draft is the 
new coverage of links for documents. I'm curious what you think of it.

The marked up draft with my changes is at [1]. You can find insertions and 
proposed deletions by looking for class="ins"/class="del" respectively in 
the source; I'll be glad to help with the merge if the changes prove 
agreeable. I think you and I will be talking by phone tomorrow, so please 
take a look if you can before we chat.

Finally: you had mentioned the possibility of linking my blog entry [2]. My 
bias tends toward putting what we need into the finding itself, but I'm 
glad to add the link if you feel it would be appropriate. I'd put it at the 
end of what's now section 5.2 [3]. Certainly the blog entry goes into more 
detail, gives examples, and explores the possibilities for using a document 
model in apps where that might not have been a clear choice..

Thank you!

Noah

[1] http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20110814
[2] 
http://blog.arcanedomain.com/2011/03/identifying-documents-in-web-applications/
[3] 
http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20110814#IdentifyDocs

P.S. Tracker, this relates to ACTION-586

Received on Sunday, 14 August 2011 19:10:20 UTC