|
Hans-Juergen,
One note I feel obligated to address, you called it "Brian's Approach". I am "representing" this approach. It was implemented by my team on a huge project. I specifically remember that it was Gary Meyer an Architect from SAIC that proposed adding "UpdateTime". I did have a lot to do with this design, however I could potentially be suffering from an enlarged ego already. The tokenizer in XMLFoundation was implemented by Sean Rohr, the #1 development resource on my team. I hope that by disseminating some of the glory and credit my ego may be brought in check. I represent this design, I understand it fully, I implemented most of it. it's not all mine. I don't know if any of you saw the TV commercial about the guy at Intel that invented USB, They made him out to be a rock star, like Bjarne Stroustrup is. Honestly - yes - I see this as the biggest new thing in XML. I believe it's going to rock the spot and I believe it is the ONLY solution where BigData meets XML. The design works (great) however I know that what made it great is the great input that made it that way. I value input. Brian > Date: Sun, 23 Mar 2014 22:35:40 +0000 > From: hrennau@yahoo.de > To: xml-dev@lists.xml.org; arjun.ray@verizon.net > CC: xmlboss@live.com > Subject: Re: AW: [xml-dev] RFC for XML Object Parsing > > Gentlemen, > > I am not sure if such historical facts and details are really important in the present context. At any rate, what interests me is the relationship between Brian's initiative and current XML. And what strikes me is the following. The XML model defines the information content of a given document; a document is the content which it is, and any glimpse beyond the document is out of scope. In particular, there is no room for distinguishing between a resource and its representation, - resource and representation are always one. But Brian's approach, so it seems to me, would build into the information content of a document a statement establishing a relationship with a seperate instance of information content (the data referenced by the oid), assigning to one (the data containing the oid) the role of being an update of the other - assigning to both the roles of subsequent states of the resource which assumes those states, but is not identical to them. And this > is certainly an interesting idea. > > Hans-Juergen > > -------------------------------------------- > Arjun Ray <arjun.ray@verizon.net> schrieb am So, 23.3.2014: > > Betreff: Re: AW: [xml-dev] RFC for XML Object Parsing > An: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org> > Datum: Sonntag, 23. März, 2014 22:29 Uhr > > [Default] On Sun, 23 Mar > 2014 12:11:47 -0600, Brian Aberle > <xmlboss@live.com> > wrote: > > | Call it what you > may, HTTP 1.0 didn't have it. It was added to HTTP > | because it was needed. > > I'm afraid your historical recall is > faulty. > > The fact of the > matter is that caching was taken seriously quite > early. From an archive of the early years of > the www-talk mailing > list (referenced at > http://lists.w3.org/Archives/Public/www-talk/2013SepOct/0002.html): > > > http://inkdroid.org/tmp/www-talk/0237.html > http://inkdroid.org/tmp/www-talk/0433.html > http://inkdroid.org/tmp/www-talk/0453.html > > What eventually became > HTTP/1.0 was initially named HTTP2 - because it > was the second spec. The original spec was > like Gopher, and had no > provision for header > fields at all. (When HTTP/1.0 was finally named, > this precursor was then jokingly dubbed > HTTP/0.96) > > The initial > drafts of HTTP2 were by Tim Berners-Lee and Dave Raggett, > in early 1993. The Last-Modified header date > back to then, with hints > that the HEAD verb > could be used to determined the modification status > of a document. This was superseded by Roy > Fielding's "conditional GET" > proposal in early 1994 > > http://inkdroid.org/tmp/www-talk/3465.html > > This was implemented in > servers (and caching servers) before the > -ahem= market-leading browsers (a recurring > tale on the web, sigh). > > And eventually, the official HTTP/1.0 spec had > If-Modified-Since: > > > http://www.rfc-base.org/txt/rfc-1945.txt > > > > _______________________________________________________________________ > > XML-DEV is a publicly archived, unmoderated list hosted by OASIS > to support XML implementation and development. To minimize > spam in the archives, you must subscribe before posting. > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > Or unsubscribe: xml-dev-unsubscribe@lists.xml.org > subscribe: xml-dev-subscribe@lists.xml.org > List archive: http://lists.xml.org/archives/xml-dev/ > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php |