<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="entry.xsl"?>
<entry>
<title>June 04, 2007</title>

<extlink>
<mylink>index.html</mylink>
<linktext>
Journal Index file
</linktext>
</extlink>

<para id="p1">
<subtitle>My Blog</subtitle>
<body>
I have a blog on Google's free blog site. Try the link below.
</body>
</para>

<extlink>
<mylink>http://brucesalem.blogspot.com</mylink>
<linktext>My Blog on Google</linktext>
</extlink>

<para id="p2">
<subtitle>Bluefish 1.0</subtitle>
<body>
Although this isn't much different from using Xemacs to edit this xml file, I am using Bluefish 1.0 on this XML file to see how well it handles other formats. It does syntax highlighting, which is good; but I suppose I would have to try to violate XML syntax by putting in an unbalanced tag or seeing if it can figure out my DTD or schema and check me. This file is still using an DTD and an XSLT, not yet a schema, although I can see that schemas are superior.
</body>
</para>

<para>
<body>
It doesn't look like bluefish can grok anything automagicaly about my XML by just seeing that I have a DTD doc. It does get that this is an XML file. I was able to set a more comfortable font size in its preferences menu item.
</body>
</para>

<toplink></toplink>

<para id="p3">
<subtitle>Design Plans</subtitle>
<body>
I am trying to find good tools with which to re-do my web content as XML with Style and define a schema in place of DTD because of the XML syntax of the data definition and potential better control over the definitions. The pitfall to avoid is to over specfify the design. The DTD is simple enough and open-ended to do a very simple page design per entry object. XML is pretty much just a brief-hand for HTML with rendering standardized in a style sheet. It could evolve into a set of viwes and even views into a data base of entry objects, but right now it is just s shortcut.
</body>
</para>

<toplink></toplink>

</entry>
