SharePoint Labs

Office | SharePoint | Search | Architecture | Stuff

Astoria and Blog Publishing

Astoria and Blog Publishing

  • Comments 2

Hi,

After hearing news about Astoria Project, I realized it will be a good candidate for blog publishing. 

You can manage feeds with Windows RSS Platform and although it is named RSS, it really support any RSS or Atom version (Syndication). But It has not support (and it is not intented for it) publishing support (Atom is in draft ietf http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-14.txt)

There are several API (Atom, MetaWeblog, LiveJournal, Blogger...moving to GData), and I think there is the possibility of improvement here.

You can read more about Astoria Project at its web site, but a brief summary from the site, seems helpful:

The goal of Microsoft Codename Astoria is to enable applications to expose data as a data service that can be consumed by web clients within a corporate network and across the internet. The data service is reachable over HTTP, and URIs are used to identify the various pieces of information available through the service. Interactions with the data service happens in terms of HTTP verbs such as GET, POST, PUT and DELETE, and the data exchanged in those interactions is represented in simple formats such as XML and JSON.

I was just imagine a module for Community Server or Microsoft Office SharePoint Server 2007, in order to interact with the blog engine to publish and manage posts and related information, and update weblog clients to use it as Windows Live Writer.

The DataService should match a standard schema, for blogs, so having a http://server/blogs/blogs.rse would show the entities (Tags, Categories, Posts, etc..), and URIs for the system would be possible in a quicker way:

  • All Categories
    •  http://server/blogs/blogs.rse/Categories
  • All Posts for Tags with name "SharePoint"
    • http://server/blogs/blogs.rse/Tags[TagName eq 'SharePoint']/Posts

The client could have the possibility to interact in XML or JSON, so AJAX interfaces should become easier to build and test.

Some of the issues with others API should be address, as for example:

  1. Retrieve posts using search queries.
  2. REST interaction
  3. XML or JSON parsing

It would be great to create a prototype ;) isn't it?

Cheers! 

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • You could be onto something...

    Of the existing APIs Atom seems the most promising, but there seems to be a lack of consistency about how to implement authentication, and Google have effectively ruined Atom by wrapping it in the over-architected, under-designed, overly-tied-to-things-they-don't-tell-us piece of smelly stuff that is GData.

    The MetaWeblogAPI is an effective standard, but as far as I'm concerned XML-RPC has fundamental design flaws (or if I'm in a good mood, deficiencies that derive from the fact that it was created early in the life of XML ).

    Anyone implementing a new API (which normally I wouldn't recommend, but hey there's room for improvement) should consider the need for functions to *list* blog posts without returning the entire body of each one (it's one of my pet peeves).

    Is there any time frame for Astoria?

  • Hi,

    At this point Astoria is an experimental project, so There is not a time frame. You can give feedback about it at http://astoria.mslivelabs.com/

    Your pet peeve would be in the query string options...stay tuned!

Page 1 of 1 (2 items)