Subject:
|
Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
Newsgroups:
|
lugnet.publish
|
Date:
|
Wed, 1 Sep 2004 01:28:55 GMT
|
Viewed:
|
2842 times
|
| |
|
|
In lugnet.publish, Dan Boger wrote:
> > * GEOGRAPHY (One only)
> > - TBD
> >
> > This is a very handy concept that requires more investigation. If
> > used, the list of geographies should be from an existing W3C standard,
> > should one exist with enough granularity to be useful.
>
> Are we sure we want to limit it to one only? That pushes the burden
> onto the filters... For instance, say there's an event in Boston. The
> GEOGRAPHY tag would say something like "US-MA-Boston", let's assume.
> That makes it easy for filters who care about US only events (US-*), MA
> only events (US-MA-*), or events in Boston. But what about our remote
> NELUGgers, who live in NH? Now, their filter will look something like
> "US-(MA|NH)-*"... And the poor WAMALUGgers would have something like
> "US-(DC|VA|MD)-*". Starts to get messy.
>
> Of course, if we push it to the publishers, the same problem exists,
> except now the work is done only once (the publisher needs to figure out
> the areas that would care), and not on each subscriber's end.
>
> Perhaps a solution would be to have a system that can tell you how far
> an event is from you. If the GEOGRAPHY was just a lat/long, I could
> easily subscribe to events that are within 50 miles of my home, etc.
I did an hour of surfing today, and came up with a few things, none of which
really strikes me as being perfect.
The most easily-implemented regional listing is the ISO-3166-2 standard:
http://en.wikipedia.org/wiki/ISO_3166-1 (Click "Local ISO codes" next to the
country in question). This gets down to the state/province level, and while it's
not very granular, it is standard and kept up to date.
The US is divided by state (mostly), Canada by province, Australia by territory,
and so on, which isn't exactly granular. But the UK is much more finely divided,
The need for this element, as I see it, is to provide some localization in a
simple way. If somebody has to do a complex lookup of a region/subregion every
time they post a feed, they probably won't use this element. But if a standard
ISO list can be referenced, or even a small web app built for content creators
to use, it shouldn't be too difficult to convince people to use the element.
So, is there a good enough reason to search for a spec more granular than the
ISO-3166-2 standard (which is worldwide)? One that would outweigh the content
creators' pain in implementation?
> On Tue, Aug 31, 2004 at 11:01:44AM +0000, Larry Pieniazek wrote:
> > > "SNOT" and "Micro" are technically not themes, and Mosaic/Sculpture
> > > also skirt this category; however, they are arguably important
> > > enough to merit their own Theme entry. As updated Themes become
> > > prevalent in LEGO Communities, they can be added to the LENNI
> > > namespace.
> >
> > I wonder if there ought to be a way to denote that a theme is fan
> > created? Ala PCS or Sea Monkeys? Also, is there merit in allowing
> > hierarchy (Space/PCS or Castle/Forestmen for example)?
> >
> > That may be excessive complexity, not sure.
>
> Especially if the theme remains a selection from a "fixed list". A punt
> would be to say "put PCS in the keywords", but that's really not a good
> solution.
Huw also recommends breaking the Themes into two parts. Here are a couple of
questions:
1. Are "LEGO-Defined Themes" and "Broad interest categories" (as two examples)
mutually exclusive? In other words, would they fit together in the same list?
2. Is there value to the content provider or content consumer to being able to
filter by "Micro Scale" AND "Trains"? Or does the fact that you can defined two
Themes in an item render this moot?
3. Would "Interest Grouping" be a better term than "Theme", and could that
encompass all the types of filtering we've discussed?
- Kelly
|
|
Message has 1 Reply:
Message is in Reply To:
12 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
