Jump to content

BlogML

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 94.116.0.41 (talk) at 12:38, 10 June 2012 (→‎History). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

BlogML is an open format derived from XML to store and restore the content of a blog.

History

BlogML was originally created by Darren Neimke in August 2005 by starting a Workspace on GotDotNet community. In July 2006, BlogML was moved to CodePlex for better Open Source development and some other developers joined this project.[1] BlogML has hit three versions so far. Versions 0.9 and 1.0 released on GotDotNet and version 2.0 released on CodePlex. After moving this project to CodePlex, Keyvan Nayyeri joined this project and added some new features for BlogML 2.0.

In addition to BlogML specification, there is a rich set of .NET Framework APIs provided by the BlogML team for .NET developers to work with markup easier.

BlogML is supported by many .NET blogging tools such as Community Server, Subtext, Single User Blog, BlogEngine.NET, DasBlog and Orchard Project. Also there are some implementations for other blogging engines and services such as Blogger.

Main goals

BlogML is created for some main goals[citation needed]:

  1. Ability to port blog content between Blog Engines:
    1. This is the case where you might have a blog based on .Text version 0.95 and you want to upgrade to Community Server. Having an "Export to BlogML" in .Text and an "Import from BlogML" function in Community Server would totally solve this problem.
  2. Ability to port blog content between Blog Engine Versions:
    1. Same as above.
  3. Ability to port blog content between Storage Providers:
    1. This is the case where you might be using a blogging engine such as Single User Blog and you are running from one provider - such as DotTextProvider (where the content reads and writes to an existing .Text schema) and you want to continue to use Single User Blog but move to a new data structure. In this case you would configure Single User Blog to use the DotTextProvider and run an "Export to BlogML" function, then you would re-configure your provider to your native provider and run the "Import from BlogML" function.
  4. Ability to easily back-up a blog:
    1. Here you would run some sort of scheduled job to automatically run the "Export to BlogML" function and save the output as a compressed backup file somewhere.

License

BlogML is licensed under BSD license.

References