Comments on: APP and Dare, the sitting duck http://www.goland.org/appanddare/ Technology, Politics, Food, Finance, etc. Thu, 04 Mar 2010 05:45:06 +0000 http://wordpress.org/?v=2.9 hourly 1 By: SSIS Junkie : OData gunning for ubiquity across Microsoft products http://www.goland.org/appanddare/comment-page-1/#comment-335061 SSIS Junkie : OData gunning for ubiquity across Microsoft products Mon, 21 Dec 2009 18:51:03 +0000 #comment-335061 [...] far as when an influential team within Microsoft were probably going to reject AtomPub and instead use their own proprietary alternative) and back in March 2008 I noted with interest an announcement by George Moore on the Live Services [...] [...] far as when an influential team within Microsoft were probably going to reject AtomPub and instead use their own proprietary alternative) and back in March 2008 I noted with interest an announcement by George Moore on the Live Services [...]

]]> By: Jamie T http://www.goland.org/appanddare/comment-page-1/#comment-206353 Jamie T Thu, 28 Feb 2008 21:17:32 +0000 #comment-206353 So, is this blog entry still relevant given the announcements on Feb 28th, 2008? i.e.: "Microsoft is making a large investment in unifying our developer platform protocols for services on the open, standards-based Atom format (RFC 4287) and the Atom Publishing Protocol (RFC 5023)." (http://dev.live.com/blogs/devlive/archive/2008/02/27/213.aspx) Has Web3S disappeared? An appropriate blog post would be much appreciated Yaron. cheers Jamie So, is this blog entry still relevant given the announcements on Feb 28th, 2008?

i.e.: “Microsoft is making a large investment in unifying our developer platform protocols for services on the open, standards-based Atom format (RFC 4287) and the Atom Publishing Protocol (RFC 5023).”
(http://dev.live.com/blogs/devlive/archive/2008/02/27/213.aspx)

Has Web3S disappeared? An appropriate blog post would be much appreciated Yaron.

cheers
Jamie

]]> By: Administrator http://www.goland.org/appanddare/comment-page-1/#comment-165006 Administrator Wed, 11 Jul 2007 04:39:31 +0000 #comment-165006 Sergey - but wouldn't you want to be able to get them directly? For example, if I do an update to a SII that makes the SII into a JPEG then wouldn't I later want to be able to do a read and get back an Image/JPEG and not some XML encoded nightmare? An implementer can also use the deferred content feature to make sure that the XML encoded glop doesn't show up in normal requests. Sergey – but wouldn’t you want to be able to get them directly? For example, if I do an update to a SII that makes the SII into a JPEG then wouldn’t I later want to be able to do a read and get back an Image/JPEG and not some XML encoded nightmare?

An implementer can also use the deferred content feature to make sure that the XML encoded glop doesn’t show up in normal requests.

]]> By: Sergey Beryozkin http://www.goland.org/appanddare/comment-page-1/#comment-164164 Sergey Beryozkin Thu, 05 Jul 2007 12:26:49 +0000 #comment-164164 Thanks, I fixed it, doing first blogging steps... Updating contained SIIs directly does look like a neat idea. In context of updates it's clearer why it makes sense to model them as individual resources, as the scoping is clear from their URIs...Can contained SIIs be characterized as write-only resources ? Thanks, I fixed it, doing first blogging steps…
Updating contained SIIs directly does look like a neat idea. In context of updates it’s clearer why it makes sense to model them as individual resources, as the scoping is clear from their URIs…Can contained SIIs be characterized as write-only resources ?

]]> By: Administrator http://www.goland.org/appanddare/comment-page-1/#comment-163450 Administrator Wed, 04 Jul 2007 05:00:57 +0000 #comment-163450 Sergey - Allow anonymous postings! I had found your blog post earlier and was trying to respond but you don't allow people to just enter their name and e-mail address. In answer to your question allowing SIIs to be addressed is useless in the case you identified which is why my current position is that the 'core' Web3S spec should not define a way to address SIIs. But as an optional feature being able to address SIIs is useful because it allows you to use a more appropriate content-type. For example, if someone wants to store an XML document as a SII they have to do it by embedding it into another XML document. This typically involves nastiness like CDATA although we will be providing a better solution. But if you can address the SII directly then you can just upload the XML doc directly as an Application/XML file. We are also likely to add binary support along side SII support so again, direct addressing means you can pull down a JPEG file as a binary stream using an SII address instead of a base 64 encoded stream in a XML or JSON file. Sergey – Allow anonymous postings! I had found your blog post earlier and was trying to respond but you don’t allow people to just enter their name and e-mail address.

In answer to your question allowing SIIs to be addressed is useless in the case you identified which is why my current position is that the ‘core’ Web3S spec should not define a way to address SIIs.

But as an optional feature being able to address SIIs is useful because it allows you to use a more appropriate content-type. For example, if someone wants to store an XML document as a SII they have to do it by embedding it into another XML document. This typically involves nastiness like CDATA although we will be providing a better solution. But if you can address the SII directly then you can just upload the XML doc directly as an Application/XML file.

We are also likely to add binary support along side SII support so again, direct addressing means you can pull down a JPEG file as a binary stream using an SII address instead of a base 64 encoded stream in a XML or JSON file.

]]> By: Sergey Beryozkin http://www.goland.org/appanddare/comment-page-1/#comment-163340 Sergey Beryozkin Tue, 03 Jul 2007 10:38:37 +0000 #comment-163340 Two comments are here : http://sberyozkin.blogspot.com/2007/06/some-comments-on-web3s.html I like the idea about merge and somewhat confused about the utility of exposing the fine-grained resources like "lastname" Two comments are here :

http://sberyozkin.blogspot.com/2007/06/some-comments-on-web3s.html

I like the idea about merge and somewhat confused about the utility of exposing the fine-grained resources like “lastname”

]]> By: John D. Heintz http://www.goland.org/appanddare/comment-page-1/#comment-162639 John D. Heintz Thu, 28 Jun 2007 20:21:07 +0000 #comment-162639 Yaron, My latest <a href="http://johnheintz.blogspot.com/2007/06/web3s-pushes-secondary-resources.html" title="blog post" rel="nofollow">blog post</a> is a response to your comments. Here is my summary: Web3S doesn't naturally support RESTful primary resource identifiers for EIIs. It can, but only with optional elements and server-specific guarantees about identifiers. A generic Web3S client could never "know" what canonical and primary resources were identified. Thanks for listening, John. Yaron,
My latest blog post is a response to your comments.

Here is my summary:
Web3S doesn’t naturally support RESTful primary resource identifiers for EIIs. It can, but only with optional elements and server-specific guarantees about identifiers. A generic Web3S client could never “know” what canonical and primary resources were identified.

Thanks for listening, John.

]]> By: John D. Heintz http://www.goland.org/appanddare/comment-page-1/#comment-162485 John D. Heintz Wed, 27 Jun 2007 17:26:13 +0000 #comment-162485 Yaron, thanks for responding to my comments (<a href="https://www.blogger.com/comment.g?blogID=16853210481690002&postID=1416302995596127417" title="see Yaron's comment here" rel="nofollow">see Yaron's comment here</a>). I'm still thinking about your words and looking through the spec. Also, you may want to package that up as a post to your own blog (so more people will see it). Yaron, thanks for responding to my comments (see Yaron’s comment here).

I’m still thinking about your words and looking through the spec.

Also, you may want to package that up as a post to your own blog (so more people will see it).

]]> By: RESTful Live Contacts for Internet-scale social networking « Jon Udell http://www.goland.org/appanddare/comment-page-1/#comment-161572 RESTful Live Contacts for Internet-scale social networking « Jon Udell Thu, 21 Jun 2007 13:54:43 +0000 #comment-161572 [...] Windows Live.” There was no mention of UPDATE. However, the spec was published in order to solicit feedback, and I’ll be interested to see what comes of [...] [...] Windows Live.” There was no mention of UPDATE. However, the spec was published in order to solicit feedback, and I’ll be interested to see what comes of [...]

]]> By: John Panzer http://www.goland.org/appanddare/comment-page-1/#comment-161406 John Panzer Wed, 20 Jun 2007 13:57:47 +0000 #comment-161406 Yaron -- Looking forward to seeing your emails on atom-protocol. I feel your pain w.r.t. time crunches :). Yaron — Looking forward to seeing your emails on atom-protocol. I feel your pain w.r.t. time crunches :).

]]>