April 27, 2003

FOAF and weblogs

Three things about FOAF and weblogs! Firstly, Ben Hammersley has written a piece for the Guardian on the latest project of the Six Apart folks behind the Moveable Type weblog publishing system. They're launching a new service, TypePad providing what looks to be a very full-featured hosting service. While MT is pretty easy to install, TypePad looks pretty cool. As well as rumoured FOAF support, it has a built-in photo album facility. The combination of those two could be quite interesting...

Oh, the other two FOAF/weblog things: I wanted to announce the existence of the foaf:weblog property a bit more widely. FOAF now has the ability to represent the address of your weblog, clearing the way for FOAF aggregators to support queries like "Find me weblogs of people who... (work for / live in / etc...)", matching against any of the other FOAF properties listed.

Finally, it's time to finish setting up the weblog we're running at http://rdfweb.org/ for FOAF and related projects. This mostly involves tweaking our MT installation and adding back the navigation and suchlike...

Posted by danbri at April 27, 2003 11:22 PM
Comments

foaf:weblog - great!

But what do you think the best way to point to the RSS 1.0 feed of the blog?

rdf:seeAlso seems to be in common use to point to other RDF files, but how best to combine this with foaf:weblog? Three alternatives spring to mind:

two statements (simple)

rdf:seeAlso -> http://example.com/feed.xml
foaf:weblog -> http://example.com/feed.xml

using blank node :

rdf:seeAlso -> bNode -> foaf:weblog -> http://example.com/feed.xml

I'm not sure what was planned for foaf:Document, how about

rdf:seeAlso -> foaf:Document -> foaf:weblog -> http://example.com/feed.xml

Posted by: Danny on April 28, 2003 04:40 PM

How about this ?

<foaf:weblog>
<foaf:Document rdf:about="http://example.org/weblog/">
<rdfs:seeAlso rdf:resource="http://example.com/feed.xml"/>
</foaf:Document>
</foaf:weblog>

Posted by: Masahide Kanzaki on June 2, 2003 03:48 AM

But some variables are immortal. These variables are declared outside of blocks, outside of functions. Since they don't have a block to exist in they are called global variables (as opposed to local variables), because they exist in all blocks, everywhere, and they never go out of scope. Although powerful, these kinds of variables are generally frowned upon because they encourage bad program design.

Posted by: Thomas on January 20, 2004 07:34 AM

This back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec

Posted by: Enoch on January 20, 2004 07:34 AM

But variables get one benefit people do not

Posted by: Cassandra on January 20, 2004 07:34 AM

Note the new asterisks whenever we reference favoriteNumber, except for that new line right before the return.

Posted by: Ralph on January 20, 2004 07:35 AM

This back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec

Posted by: Jerome on January 20, 2004 07:35 AM

When Batman went home at the end of a night spent fighting crime, he put on a suit and tie and became Bruce Wayne. When Clark Kent saw a news story getting too hot, a phone booth hid his change into Superman. When you're programming, all the variables you juggle around are doing similar tricks as they present one face to you and a totally different one to the machine.

Posted by: Jasper on January 20, 2004 07:35 AM

Earlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.

Posted by: Joan on January 20, 2004 07:35 AM

That gives us a pretty good starting point to understand a lot more about variables, and that's what we'll be examining next lesson. Those new variable types I promised last lesson will finally make an appearance, and we'll examine a few concepts that we'll use to organize our data into more meaningful structures, a sort of precursor to the objects that Cocoa works with. And we'll delve a little bit more into the fun things we can do by looking at those ever-present bits in a few new ways.

Posted by: William on January 20, 2004 07:35 AM

The rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:

Posted by: Guy on January 20, 2004 07:35 AM

But variables get one benefit people do not

Posted by: Robert on January 20, 2004 07:35 AM

very impressive

Posted by: handylogos on January 22, 2004 01:34 PM

greetings

Posted by: doc on January 24, 2004 10:38 PM

nice site

Posted by: rainer on January 24, 2004 10:39 PM

greeting

Posted by: rainer on January 24, 2004 10:40 PM
Post a comment