TruerWords Logo

Search TruerWords

This is one of my journal's many "channels."
This chanel only shows items related to "CMS."

Sign Up  Log On
Friday, December 1, 2017

Manton Reece has finally 😃 opened up to more of the general public, and so I have an account. is like a federated twitter, where everybody owns their own content instead of storing it all on a central service like Twitter.

I'll almost certainly keep the paid service they offer, but more interesting to me is finding ways to integrate with the service.

It looks good, Manton! Nice work!

Friday, April 14, 2006

Greg's Conversant-Ruby Scripts

Greg has produced a set of Ruby scripts for editing your Conversant site's templates, javascripts, and stylesheets *locally*. It downloads them all via xml-rpc. You edit them in your local editor, then run the upload script and it sends back whatever has been modified.

Very handy when you're doing a lot of work on a site... such as when you're trying to perfect your design for your next entry in the patterns contest!

Thursday, December 1, 2005

Weblog II is Finally "Out There"

After years of private beta (man that's embarrassing to admit out loud), Macrobyte has finally released Weblog II, our 'next generation' weblogging system for Conversant.

Big, smart, easy to use.. and that just describes the lead developer behind it! Weblog II is even better than that!

(No, seriously, Weblog II is fully buzzword compliant. There's even a super-simple wizard for converting your old Conversant weblog to a Weblog II page.)

Greg said, "It's about time!" I agree. It's been like having a lazy, 30 year old kid still living at home with his parents. "Get out there and earn your keep, lazy bones!"

Friday, March 18, 2005

Phil Responds (sorta) re: HTML Comments and Linking Technologies

I thought Phil was ignoring me. I wrote to him on the 7th, after posting about HTML comments and embedded RDF, to ask what he thought of my suggesting regarding invisible links pointing to autodiscovery documents.

He wasn't ignoring me, he just couldn't put his brain into gear for this one. (I'm not picking on him, that's what he said!).

He asked people to comment on my idea. Unfortunately, most of the comments have nothing to do with the problem at hand, and many of the commentors apparently don't understand the issue. (They talk about everything from the usefulness of trackback to the second coming of <blink>.

For the record, and perhaps to help bring the discussion back to the real point, here's the bulk of the email I sent to him:



At the end of that post, I had an idea/suggestion for linking to autodiscovery (or other types of metadata) documents that would seem to work with pages having multiple items (which has always been one of the two big problems with using a <link> elements in the head).

I realize it's not perfect, as the <a> tag doesn't actually have any identifying information that would allow the machine to associate it with a post on a page containing more than one (such as a weblog's home page). So, what about something like this?

<a rel="trackback:" href=""></a>

The single value in the rel attribute manages to both identify it as a trackback-related url, and identify the server object it supports. It appears to be a legal value, as the spec only says that the value of rel must be a string with the space separating multiple values (but we're only providing one long value).

It's logical, too, making it very easy to automate.

Any thoughts on this? I'm interested not just for the sake of trackback, but because other technologies will have a chance to "bloom" if this hurdle can be overcome.

He didn't publish that email, which is good, but without it the people being asked to comment would really have very little on which to comment.

Hopefully he'll post a follow-up with a link to this entry, so some more relevant discussion can take place.

Monday, March 7, 2005

Creative Commons, Trackback, HTML Comments, and Embedded RDF

How many years do I have to work with HTML before I stop discovering important technical points of which I should have been aware all along?

Today's rather embarrassing example regards the format of HTML comments. This completely took me by surprise.

HTML comments have the following syntax:

    <!-- this is a comment -->
    <!-- and so is this one,
    which occupies more than one line -->

White space is not permitted between the markup declaration open delimiter("<!") and the comment open delimiter ("--"), but is permitted between the comment close delimiter ("--") and the markup declaration close delimiter (">"). A common error is to include a string of hyphens ("---") within a comment. Authors should avoid putting two or more adjacent hyphens inside comments.

Information that appears between comments has no special meaning (e.g., character references are not interpreted as such).

Note that comments are markup.

In other words, comments don't end with "-->". They end with "--" followed eventually by an occurence of '>'.

This explains problems I've seen for years but never bothered to dig into deeply enough. I thought that the HTML comment delimiters were simply a "balanced pair", similar to the < and > that mark the start and end of a tag. A "<!--" followed at some point by a "-->".

Practical implications? There are a few. The most obvious (in my world) is that one can't reliably "comment out" the results of some Conversant macros. For example, if the macro returns a user-defined string from a database (such as a message subject), that string might include a "--". If it does, then the very next '>' will close the comment.

Trackback "autodiscovery" data is RDF embedded in HTML comments. It looks something like this:

<rdf:RDF xmlns:rdf=""
    dc:title="HTML Comments -- They Don't Work How You Thunk"
    trackback:ping="" />

See the problem? The dc:title attribute of the Description element contains a "--", and so the comment is closed by the very next '>'. That leaves the </rdf:RDF> and the --> outside of the comment, and in fact Firefox displays the --> on the web page!

Creative Commons Licenses work in a similar way: they embed licensing information in the HTML via comments. They're not bitten by this comment syntax problem, though, because they have more control over the attribute values of the tags, and can intentionally avoid the double-hyphen problem.

See Kendall Grant Clark's Creative Comments: On the Uses and Abuses of Markup for a discussion of the semantic problems with this approach, and Phil Ringnalda's throrough review of the trackback problem (years old).

I didn't see any mention, in my brief research, of using a technorati-style link to solve the problem. Instead of embedding the RDF in the html, we could link to an RDF autodiscovery file with an invisible-to-people link like <a href="" rel="autodiscovery"></a>. Any reason that wouldn't work?

Comments appreciated.

December, 2018
Sun Mon Tue Wed Thu Fri Sat
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31  
Dec  Jan


Channel RSS: RSS Feed for channel

is Seth Dillingham's
personal web site.
Truer words were never spoken.