BurningbirdOne of the things I liked about movable type is that you could choose the formatting on a post by post basic. That doesn’t necessarily work well in a dynamic environment, but I did add an option in the post edit page to choose whether you want the content formatted (using default formatting as per WordPress/Wordform, or plugin), or if you’ll apply your own (X)HTML.
This is a test to see how it works
This is a test
update
Woo hoo. Worked first time, right out of the box. I’m so bad.
In the last 24 hours, I managed to get three major components of Wordform finished. Go me.
The first was the external application-via-plugin dashboard that allows user-selected filler. With this you can use one or more plugins to provide whatever you want within the dashboard area. For instance, I currently have a list of updated posts through my Feed-on-Feed installation, as well as a list of updated posts from the Burningbird weblogs.
The second was getting the Meta option to work. If you access the individual posts or pages within the site, and there’s metadata defined for them, the RDF/XML is returned. I still have to finish the interface for adding the data, but it shouldn’t be complicated. You can see my test cases at http://weblog.burningbird.net/me/rdf/ and here. I’ll add code to create a link to the files in the header, and another option whereby if you pass in ‘meta’ rather than ‘rdf’, you’ll get an HTML table of the information, in human viewable format.
With this functionality, if anyone wants to provide metadata support for a specific vocabulary, such as Creative Commons or the Vegetarian schema (yes, true schema), all they have to do is create a plugin that provides the HTML for the form fields (to enable the user to fill in the blanks on the statements) and make some simple API calls to process the data. From the advanced editing page, an option listing all available schemas (as plugins) is provided and clicking on one opens up the form to grab the data and update the database. Once metadata has been created for a page or a post, attaching a ‘/rdf/’ or ‘/meta/’ to the permalink for either returns the formatted data.
No more worries about putting the data into comments in XHTML. No more worries about combining data from different schemas, since it’s all RDF/XML.
The final option I finished today was fulltext, which you can see in the last post.
Still lots of work to do, but these were the three big infrastructure items left. Onwards.
Recovered from Wayback Machine.
In the last 24 hours, I managed to get three major components of Wordform finished. Go me.
The first was the external application-via-plugin dashboard that allows user-selected filler. With this you can use one or more plugins to provide whatever you want within the dashboard area. For instance, I currently have a list of updated posts through my Feed-on-Feed installation, as well as a list of updated posts from the Burningbird weblogs.
The second was getting the Meta option to work. If you access the individual posts or pages within the site, and there’s metadata defined for them, the RDF/XML is returned. I still have to finish the interface for adding the data, but it shouldn’t be complicated. You can see my test cases at http://weblog.burningbird.net/me/rdf/ and here. I’ll add code to create a link to the files in the header, and another option whereby if you pass in ‘meta’ rather than ‘rdf’, you’ll get an HTML table of the information, in human viewable format.
With this functionality, if anyone wants to provide metadata support for a specific vocabulary, such as Creative Commons or the Vegetarian schema (yes, true schema), all they have to do is create a plugin that provides the HTML for the form fields (to enable the user to fill in the blanks on the statements) and make some simple API calls to process the data. From the advanced editing page, an option listing all available schemas (as plugins) is provided and clicking on one opens up the form to grab the data and update the database. Once metadata has been created for a page or a post, attaching a ‘/rdf/’ or ‘/meta/’ to the permalink for either returns the formatted data.
No more worries about putting the data into comments in XHTML. No more worries about combining data from different schemas, since it’s all RDF/XML.
The final option I finished today was fulltext, which you can see in the last post.
Still lots of work to do, but these were the three big infrastructure items left. Onwards.
I’m tired of splitting my focus between 3 or 4 projects and never quite finishing any of them. Instead, I’m going to focus on one–coding Wordform–so I can put the first release of the code out on the street for the daring of you to trip over. I have some writing to do, and the store and Tinfoil to finish, and I want to spend time in the Ozarks in the next couple of weeks finishing my photos of mills — but I’ll feel better doing all of these things if this one item is checked off.
What this means is this weblog and my others may be going through some interesting times in the next few days as I start modifying some of the core infrastructure elements. Expect things to break; copy your comments before posting; ignore the purple paint, broken glass, and hole in the floor.
For those who are Catholic, I am sorry at the loss of the leader of your church today. There were many things I admired about Pope John Paul II: his dedication, hard work, and the common touch he had that made him so endearing. In the end, though I did not agree with many of his opinions and some of the actions he took (or did not take), I can respect him as a man who was fearless in the face of adversity, and had earned the love of many.