Right. So in the Delicious case, there are really two URLs:

1. URL of the iCalendar feed

2. URL of the “home page” for the event source, to be used in case per-event URLs are missing (as they often are)

Since #1 is implicit — it is the URL that is being bookmarked — the only explicit part is #2, which we’ve been writing as url=http://…

In another context, like Ed’s semantic wiki, you’d need to spell out both explicitly. Hence:

feedurl=http://…
homeurl=http://…

There are two levels: per-location, and per-feed.

Per-location, e.g. Keene or Ann Arbor, it looks like this:

tz=Eastern
title=events+in+and+around+keene
img=http://elmcity.info/media/keene-night-360.jpg
css=http://elmcity.info/css/elmcity.css
contact=judell@mv.com
where=keene+nh
template=http://elmcity.info/media/tmpl/events.tmpl
lat=42.93
lon=-72.27

In your semantic wiki that would be:

{{Location
|tz=Eastern
|title=events in and around keene
…etc…
}}

Then there’s the per-feed level. Here the metadata could be done like so:

{{Feed
|title=Cheshire Medical Center
|homeurl=http:cheshire-med.com
|feedurl=http://fusecal.com/calendar/ical/741782?h=2bbbaf0a-13cb-11de-9ce1-00163e284ee0
|tags=trusted,ics,feed
}}

I think you could do this all on one page. You’d wind up with an HTML infobox for the location metadata, plus one for each feed. The generated HTML can’t be easily parsed, but that’s no problem, I could just fetch the Edit link and read the structured source.

Is there a compact description by reference of the contents of the http://delicious.com/a2cal file that you are pulling from, in particular I assume you are pulling XML or JSON – I don’t want to have to reconstruct the HTML if it’s not needed. It might be as simple as a pointer to the right delicious spec page.