Proof that anyone can do it RSS 2.0
 Saturday, July 24, 2004

I know you already know, but if you haven't done it already (unless you're WAY brighter than me), you too will someday spend an hour troubleshooting a stylesheet before you realize you've got a friggin' capital letter where you shouldn't. 

Saturday, July 24, 2004 6:40:31 PM UTC  #    -
XML
 Thursday, June 24, 2004

In helping to convert a three-ring-bound procedure manual to something better, I’ve noticed that even though the Internet has been around for years, people struggle with parts of its concept

Background
The manual I’m talking about here is a very technical document.  It details procedures for fingerprint examiners to follow in all aspects of their jobs.  It’s existed in a three-ring binder for many, many years, and is critical to the job for reasons that aren’t important in this context.

Problem
The problem is that the document is ‘ordered’.  Like most ‘normal’ documents, it has a table of contents, with chapters that group similar content together.  Unfortunately, no one reads it that way.  When you need it, you need a specific part of it, but no one reads the whole thing (or even a whole chapter) in the normal course of business.  It’s a reference for those times when you can’t remember a very specific item or task. 

Observation
There probably are some neat terms out there that describe this concept better, but I’m calling them ‘Ordered documents’ and ‘Unordered documents’ (and hereby claiming the rights to all profits that my ‘new’ terms generate<evil laugh/>).  An ordered document is like a novel...you read chapter 1 in order to understand chapter 2, then on to chapter 3, etc. You don't (usually) skip around the book and read just certain parts of it unless your bookmark falls out. 

An unordered document is more like our manuals (probably like most technical documents). We might go directly to the recipe for a Ninhydrin solution, then click from there over to safety protocols, then to standards and procedures, etc. We don't read through anything start to finish (well, most people don't anyway).

The web works like this…it’s littered with links in places that will take you abruptly to somewhere else. Many people intuitively understand this concept when they see it.  But when writing documents, we struggle because the only way most of us know how to write documents is in 'order'. Putting a 'link' in the middle of a paragraph is still uncomfortable to many people.  Worse yet is converting a document that has been ‘ordered’ for its whole life. 

Solution
Yeah, right.  There are a number of solutions out there, probably many I’ve never even heard of; for this case, I’m pushing DocBook (not Dita…sorry Jes!).  I’ve spent a ton of time all over Bob Stayton’s site and have managed to squeeze out some good proofs of concept

Thursday, June 24, 2004 9:28:31 PM UTC  #    -
XML
 Tuesday, June 01, 2004

A current Windows Forms project of mine requires the caching of a fair amount of data.  Specifically, I want to store, in memory, on the client, a selection of XML data.  When it's done, this should behave something like ASP.NET's session object...so I'll have access to user information and preferences without having to hit the data source every time to get it. 

It's no problem to instantiate a class that retrieves and holds this information, but making that information available to other forms in the application (without again reloading an instance of the class and re-retrieving the data) is escaping me.  I explored Microsoft's Caching Application Block, and while it appears to offer the kind of behavior I'm after, it's a bit more complicated than I need (and depends heavily on SQL Server...I want to avoid that). 

Anyone have any suggestions out there?

Tuesday, June 01, 2004 8:07:44 PM UTC  #    -
.NET | XML
 Tuesday, May 04, 2004

Being new to the whole blogging thing, I'm still learning what exactly this application is doing with my rambling text.  I've noticed that many of the hits on this blog are rss aggregators (mostly from rssreader.com), and this article has now explained that concept. 

I like the idea of getting all the news I care about brought directly to me...I wish I'd thought of that.

Tuesday, May 04, 2004 12:07:43 AM UTC  #    -
XML
 Tuesday, February 10, 2004

Jeremy Esland has convinced me that XML is the answer to many of the data problems I am encountering in a variety of projects.  The more I learn about XML, the more I'm sure it's the answer. 

In a related side-note, Jeremy also introduced me to the eXist project.  eXist is a powerful XML storage and retrieval solution that can be run and accessed in a variety of ways. 

Now if I could just get my .NET code to retrieve some documents from eXist...

Tuesday, February 10, 2004 2:24:25 PM UTC  #    -
.NET | XML | eXist
Archive
<March 2010>
SunMonTueWedThuFriSat
28123456
78910111213
14151617181920
21222324252627
28293031123
45678910
Quick Quips
    About the author/Disclaimer

    Disclaimer
    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

    © Copyright 2010
    John Bowen
    Sign In
    Statistics
    Total Posts: 152
    This Year: 0
    This Month: 0
    This Week: 0
    Comments: 164
    Themes
    Pick a theme:
    All Content © 2010, John Bowen
    Theme modified from the 'Business' theme created by Christoph De Baene (delarou)