Re: Structured Publishing -- Joe Reger shows the way...

[James M Snell]

Bob Wyman wrote:

I’ve written a blog post pointing to a wonderful demo of tools for 
doing structured publishing in blogs that Joe Reger has put together. 
Given that Atom has built-in support for handling much more than just 
the text/HTML that RSS is limited to, I think this should be 
interesting to the Atom community.


http://bobwyman.pubsub.com/main/2005/09/joe_reger_shows.html

What can we do with Atom to make the vision of Structured/Semantic 
publishing more real?


bob wyman

There really isn't anything we HAVE to do with Atom to make it suitable 
for Structured publishing. The format's content model is already more 
than adequate for this kind of thing. For instance, Joe Reger's software 
could easily stuff the XML data instances that conform to a logs XML 
Schema into the atom:content element while including the text 
description of the log into the atom:summary. The only thing that really 
needs to happen here is for someone to begin writing the code that makes 
this happen.


- James

Re: Atom 1.0 ootb with MT3.2

[Bill de hÓra]

Tim Bray wrote:
> 
> On Sep 9, 2005, at 5:03 AM, Bill de hÓra wrote:
> 
>>
>>
>> Here's the feedvalidator results for my journal served up as  Atom1.0 as
>> per MT3.2's Atom1.0 template
>>
>> http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.dehora.net%
>> 2Fjournal%2Fatom.xml
> 
> 
> I'm getting a 404 on that (or rather the feedValidator is) -Tim

Yeah, sorry. I have a ticket in to transfer the domain, but wasn't
expecting anything to happen until next week (who'da thunk anything to
do with DNS could happen on the same working day).

cheers
Bill

Re: Atom 1.0 ootb with MT3.2

[Tim Bray]

On Sep 9, 2005, at 5:03 AM, Bill de hÓra wrote:




Here's the feedvalidator results for my journal served up as  
Atom1.0 as

per MT3.2's Atom1.0 template

http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.dehora.net% 
2Fjournal%2Fatom.xml


I'm getting a 404 on that (or rather the feedValidator is) -Tim




I also see it uses tag: uris as the atom:id value. I think I'll change
the template to use the http: URI generated by MT3.2 for the  
individual

entries instead of the tag: (what the rest of the world calls
permalinks). I haven't tried to import/export to see if the atom:id is
preserved across installations.

Speaking of URIs and IDs, there is a gotcha around archive URIs if you
are upgrading to MT 3.2 [1].

cheers
Bill

[1]

Re: Atom 1.0 ootb with MT3.2

[A. Pagaltzis]

* Bill de hÓra <[EMAIL PROTECTED]> [2005-09-09 14:10]:
> I also see it uses tag: uris as the atom:id value. I think I'll
> change the template to use the http: URI generated by MT3.2 for
> the individual entries instead of the tag: (what the rest of
> the world calls permalinks).

Just make sure it doesn’t change the permalink when you edit the
entry title. A lot of software still has this habit. (And if MT
3.2 doesn’t, it would be nice to know so, too.)

Regards,
-- 
Aristotle Pagaltzis // 

Atom 1.0 ootb with MT3.2

[Bill de hÓra]

Here's the feedvalidator results for my journal served up as Atom1.0 as
per MT3.2's Atom1.0 template

http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.dehora.net%2Fjournal%2Fatom.xml


I also see it uses tag: uris as the atom:id value. I think I'll change
the template to use the http: URI generated by MT3.2 for the individual
entries instead of the tag: (what the rest of the world calls
permalinks). I haven't tried to import/export to see if the atom:id is
preserved across installations.

Speaking of URIs and IDs, there is a gotcha around archive URIs if you
are upgrading to MT 3.2 [1].

cheers
Bill

[1]