<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx</link><description>The goal of Astoria is to make data available to loosely coupled systems for querying and manipulation. In order to do that we need to use protocols that define the interaction model between the producer and the consumer of that data, and of course we</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#4851558</link><pubDate>Mon, 10 Sep 2007 09:53:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4851558</guid><dc:creator>MSDN Blog Postings  » Astoria Design: payload formats</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/09/10/astoria-design-payload-formats/"&gt;http://msdnrss.thecoderblogs.com/2007/09/10/astoria-design-payload-formats/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>What's your take on the wire formats Astoria should support?</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#4855568</link><pubDate>Mon, 10 Sep 2007 22:16:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4855568</guid><dc:creator>Pablo Castro's blog</dc:creator><description>&lt;p&gt;As much as I'd like to say that formats are a low-level thing that most consumers of the technology shouldn't&lt;/p&gt;
</description></item><item><title>191 Miles to Astoria</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#4873307</link><pubDate>Wed, 12 Sep 2007 03:49:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4873307</guid><dc:creator>Man vs Code</dc:creator><description>&lt;p&gt;A couple of months ago I became Development Lead for Project Astoria . The goal of Project Astoria is&lt;/p&gt;
</description></item><item><title>191 Miles to Astoria</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#4873537</link><pubDate>Wed, 12 Sep 2007 04:06:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4873537</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;A couple of months ago I became Development Lead for Project Astoria . The goal of Project Astoria is&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#4931799</link><pubDate>Sat, 15 Sep 2007 22:19:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4931799</guid><dc:creator>Benjamin</dc:creator><description>&lt;p&gt; &amp;nbsp; What about Astoria for Orcas Beta 2? &lt;/p&gt;
&lt;p&gt; &amp;nbsp; Please I need the new version!&lt;/p&gt;
&lt;p&gt; &amp;nbsp; Thanks for all!&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5000382</link><pubDate>Wed, 19 Sep 2007 22:02:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5000382</guid><dc:creator>Jeni Tennison</dc:creator><description>&lt;p&gt;Great to see Atom being used here. I've been covering some similar ground with regard to how to best use Atom with an object-oriented data structure, which I've &amp;lt;a href=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://www.jenitennison.com/blog/node/54&amp;quot;"&gt;http://www.jenitennison.com/blog/node/54&amp;quot;&lt;/a&gt; title=&amp;quot;Web 2.0 Project: Using Atom and XML with Graph Data Structures&amp;quot;&amp;gt;written up a bit on my blog&amp;lt;/a&amp;gt;. I think the main differences from the approach you outline here are (a) that I view the elements within atom:entry as being &amp;lt;em&amp;gt;metadata&amp;lt;/em&amp;gt; so wouldn't put actual &amp;lt;em&amp;gt;content&amp;lt;/em&amp;gt; in them and (b) to avoid having lots and lots of requests flying around, I'm thinking of having some embedding of data within the payload, even when that data is also available as a separate feed.&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5009114</link><pubDate>Thu, 20 Sep 2007 11:49:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5009114</guid><dc:creator>Danny</dc:creator><description>&lt;p&gt;As you can guess, I'm a bit disappointed by RDF being low priority, it being an entity-relationship model designed for the Web...&lt;/p&gt;
&lt;p&gt;But ok, support for RDF/XML format isn't critical for Semantic Web interop - e.g. there is some work ongoing right now on &amp;lt;a href=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://n2.talis.com/wiki/RDF_JSON_Brainstorming&amp;quot;&amp;gt;RDF/JSON&amp;lt;/a&amp;gt;"&gt;http://n2.talis.com/wiki/RDF_JSON_Brainstorming&amp;quot;&amp;gt;RDF/JSON&amp;lt;/a&amp;gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;What is critical, is the maximal use of URIs to name things - wherever possible for entities, ideally relationships (i.e. typed links) too. &lt;/p&gt;
&lt;p&gt;So...please check out &amp;lt;a href=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://en.wikipedia.org/wiki/Linked_Data&amp;quot;&amp;gt;Linked"&gt;http://en.wikipedia.org/wiki/Linked_Data&amp;quot;&amp;gt;Linked&lt;/a&gt; Data&amp;lt;/a&amp;gt;!&lt;/p&gt;
</description></item><item><title>Astoria and Web3S converge</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5020224</link><pubDate>Fri, 21 Sep 2007 01:41:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5020224</guid><dc:creator>SSIS Junkie</dc:creator><description>&lt;p&gt;Three weeks ago I wrote this blog entry that raised a question mark over why Microsoft were coming out&lt;/p&gt;
</description></item><item><title>URI Format - Part 1 - Addressing resources using URI path segments</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5035271</link><pubDate>Fri, 21 Sep 2007 19:30:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5035271</guid><dc:creator>Project Astoria Team Blog</dc:creator><description>&lt;p&gt;Deciding on something that becomes a public interface of a developer-oriented technology is a tricky&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5211251</link><pubDate>Sun, 30 Sep 2007 17:46:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5211251</guid><dc:creator>Andres Aguiar</dc:creator><description>&lt;p&gt;Wouldn't be possible to have a pluggable framework for serialization formats so if someone wants RDF he could write it?&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5217007</link><pubDate>Mon, 01 Oct 2007 03:54:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5217007</guid><dc:creator>pabloc</dc:creator><description>&lt;p&gt;@Danny: thanks for the support. I knew you weren't to be happy about it, but I think you just nailed the point: while RDF is an important component is not the core piece. The high-order bit, data with augmented semantics expressed in computer-consumable ways, is still there in Astoria.&lt;/p&gt;
&lt;p&gt;@Andres: regarding exposing the serialization framework, my primary concern is that I really don't want to invent another public serialization infrastructure for the .NET Framework. We already have a few and they handle most applicaiton scenarios. Unfortunately it didn't quite work out for Astoria (we tried really hard), but that doesn't mean that they shouldn't be used for other things. Furthermore, formats in Astoria go beyond serialization sometimes...aspects such as interaction models and even certain semantics may be forced down by a given protocol in order to be fully compliant. Most likely we'll go out without an open hook for formats for the first release and then see what the user feedback is to decide how to proceed after that.&lt;/p&gt;
&lt;p&gt;-pablo&lt;/p&gt;
</description></item><item><title>Need leads?</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#5466970</link><pubDate>Tue, 16 Oct 2007 07:00:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5466970</guid><dc:creator>Need leads?</dc:creator><description>&lt;p&gt;Top leads boca raton sales and marketing firm knowledge may take a bit of time to happen upon.&lt;/p&gt;
</description></item><item><title>SoCal MSDN events for Web Developers - slide deck and links</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#6667832</link><pubDate>Wed, 05 Dec 2007 19:11:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6667832</guid><dc:creator>Contagious Curiosity</dc:creator><description>&lt;p&gt;Presentations given in Irvine and Riverside, CA - here's the deck and links for more information about&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#6733771</link><pubDate>Tue, 11 Dec 2007 13:53:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6733771</guid><dc:creator>Ben</dc:creator><description>&lt;p&gt;WCf's binary xml is very nice for internal use , speaking of which non IIS hosting ( windows services ) is a big plus for small sit5es which keep stuffing up the WCF security.&lt;/p&gt;
&lt;p&gt;Regards, &lt;/p&gt;
&lt;p&gt;Ben&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#7032254</link><pubDate>Tue, 08 Jan 2008 23:25:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7032254</guid><dc:creator>Rick</dc:creator><description>&lt;p&gt;Have you guys considered STEP/P21 as a format? &amp;nbsp;(see ISO 10303-21 on wikipedia). &amp;nbsp;It's commonly used for manufacturing and engineering data. &amp;nbsp;It can represent very complex relationships in a very compact, elegant, and easy-to-read way.&lt;/p&gt;
</description></item><item><title>The ADO guy on ADO.NET Data Services</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#7314499</link><pubDate>Wed, 30 Jan 2008 02:16:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7314499</guid><dc:creator>Ricardo Fiel</dc:creator><description>&lt;p&gt;Scott Hanselman just published his 97th podcast, titled ADO.NET &amp;amp;quot;Astoria&amp;amp;quot; Data Services with&lt;/p&gt;
</description></item><item><title>re: Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#7520283</link><pubDate>Thu, 07 Feb 2008 19:56:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7520283</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;From the point of view of interoperability with other systems, i would say some kind of access to the serialisation is invaluable.&lt;/p&gt;
&lt;p&gt;BTW, the same argument applies to the URL syntax. The way that filters are represented is partly a stylistic choice and other REST implementation will make a different choice. Again, for interoperability, some means of intercepting the incoming request would be good. It would have to be at a different level than the current query interceptors though...&lt;/p&gt;
</description></item><item><title>AtomPub support in the ADO.NET Data Services Framework</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#7687639</link><pubDate>Thu, 14 Feb 2008 10:07:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7687639</guid><dc:creator>Project Astoria Team Blog</dc:creator><description>&lt;p&gt;We have been looking for the last few months at adding first-class support for AtomPub to Project Astoria&lt;/p&gt;
</description></item><item><title>AtomPub support in the ADO.NET Data Services Framework</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#7687861</link><pubDate>Thu, 14 Feb 2008 10:44:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7687861</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;We have been looking for the last few months at adding first-class support for AtomPub to Project Astoria&lt;/p&gt;
</description></item><item><title>Project Astoria Team Blog : Astoria Design: payload formats</title><link>http://blogs.msdn.com/astoriateam/archive/2007/09/09/design-feedback-requested.aspx#8574934</link><pubDate>Thu, 05 Jun 2008 13:26:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8574934</guid><dc:creator>Weddings</dc:creator><description>&lt;p&gt;The goal of Astoria is to make data available to loosely coupled systems for querying and manipulation. In order to do that we need to use protocols that define the interaction model between the producer and the consumer of that data, and of course w&lt;/p&gt;
</description></item></channel></rss>