Troubleshooting BlogML - Introduction
Having a good documentation for software is something mandatory nowadays. I see some negative feedbacks about various software for documentation. Unfortunately people (even non-technical people) don't want to spend sometime to get what they need. In most cases, I see duplicate questions about something that is already answered but if you don't answer then they begin saying "this frustrated software ..." or "I'm giving up with this ..." and same statements! I hate people who expect others to put the food on the table for them and they just know how to eat!
However, above paragraphs were an introduction to move the thread to BlogML, our open source mark up language for blog content definition. In the recent months we got many users both from .NET community and from non-technical users. Some users had problems to get their migrations done with BlogML so sent some feedback about the BlogML project. Now that we have an official site for BlogML and have planned to provide good documentation about it, I thought it would be helpful if I write a short post as an introduction to BlogML troubleshooting and keep writing more detailed posts on my blog in the future to save myself from answering a question many times and also users to find their answers easier. So here is the first post as an introduction!
First let me talk about the BlogML issues in general. During these two years when I've been a member of BlogML project and have worked with many guys to help them migrate between blogging tools, saw some common issues with BlogML. From one view, these issues can be grouped in four categories:
- Problems with schema
- Problems with BlogML .NET API
- Problems with export tool
- Problems with import tool
As is obvious, the latest two cases aren't something that we directly can take care of them because converters are written with community members not ourselves.
The other annoying point is unfortunately most of the questions and reported issues are something that we have already answered in the default download packages but users do not attend to them at all and again just come up and ask about these issues!
One common question for users is "Do you have an export or import tool for my blogging tool?". This is something obvious: as long as someone writes a converter then we have that tool available otherwise we just can say that we're sorry! Fortunately we currently support all famous blogging tools and services like Community Server, Subtext, DasBlog, Windows Live Spaces, Blogger and WordPress and a converter for BlogEngine.NET is coming! But if you're using a blogging tool that doesn't have a converter written yet and if you're a technical guy then it's possible to create some database mappings to generate your BlogML XML content from database easily. This is a solution that some guys have used to generate their BlogML content.
The other common question is about the percentage of the content that may be lost during a migration with BlogML. I'm proud to say that BlogML is able to move the content of all common blogging tools easily. All common features for blogging tools and services are built for default BlogML structure. We also have provided some extensibility points like extended properties to let you store data as key/value pairs for BlogML objects and use them easily. Furthermore, we're going to add new blogging features and extensibility points to BlogML in next version. I agree that people may have different thoughts about BlogML based on the blogging tool that they use but in my opinion my Community Server converter along Subtext converter are two good examples of converters that could be able to implement BlogML features in good details. Users of these two converters have been happy with them so far!
In the abovementioned introduction I gave four different categories about BlogML issues. In the upcoming posts, I discuss more about troubleshooting BlogML issues based on these categories.
[advertisement] Axosoft OnTime 2008 is four developer tools in one: bug tracking, project wiki, feature management, and help desk. It manages your development process so developers can focus on coding. Installed or Hosted – Free Single-user license -- Free 30-day team trial.
10 Comments : 09.10.07

#1
Jeff Bishop
09.10.2007 @ 9:15 PM