W3C home > Mailing lists > Public > www-tag@w3.org > August 2011

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

From: Larry Masinter <masinter@adobe.com>
Date: Mon, 15 Aug 2011 00:11:56 -0700
To: Noah Mendelsohn <nrm@arcanedomain.com>, Ashok Malhotra <ashok.malhotra@oracle.com>
CC: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D05D41A7C27@nambxv01a.corp.adobe.com>
I'm belaboring this point because I think a lot of people are confused by it, and at the risk of being pedantic:

Noah: "techniques for identifying documents and for bookmarking application states have evolved correspondingly."
=>
Larry: "techniques for designing applications so that application state and document views of application state can be identified and bookmarked."a


Noah: "Many Web applications are used to present or edit documents. Such documents should be identified with URIs that can be used for linking, e.g. from other Web pages or in e-mails"

Larry: "Many Web applications are used to present or edit documents. Such applications should be designed so that the documents are readily identified with URIs that can be used for linking, e.g. from other Web pages or in e-mails."


IF you have an application,  and it has   states you would like to bookmark, or it displays something you think of as a "document" you'd like to identify  independent of the application state
THEN: If the application wasn't designed right, you're just out of luck. You actually have to redesign the application to enable this.

So the advice isn't "how to identify documents" or "how to bookmark application state".
The advice is "how to design applications" so that those things are possible.

Larry



-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Noah Mendelsohn
Sent: Sunday, August 14, 2011 9:10 PM
To: Ashok Malhotra
Cc: www-tag@w3.org
Subject: 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 Monday, 15 August 2011 07:12:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:39 GMT