Re: RSS : a "namespace" in itself ?
- Although I agree that using backend.userland.com might be a better
solution, I'm not personally comfortable with hi-jacking their domain
without permission. Even if we did get permission, what if they make a
stink of it later on? I'm fearing this path.
--- In email@example.com, "rcade" <cadenhead@...> wrote:
> Along those lines, I think "http://backend.userland.com/rss2" is a
> better choice for the namespace URI than
> "http://www.rssboard.org/rss-namespace", given James' tests and the
> Google Code Search result. So I'm revising my suggestion.
- Awesome! I think then that most of us are in agreement, we just need
to decide whether to go with the userland or rssboard namespace. I'm
going to start a brand new thread (this one is too loud to follow).
--- In firstname.lastname@example.org, "scamden" <sterling@...> wrote:
> After some further research: Visual Studio only generates a
> if the URI points to a file with extension .xsd that either cannot
> opened or is not in a valid XSD format.
> SlickEdit, on the other hand, generates a popup warning any time
> the URI is not an XSD.
> I fully understand that having the URI point to an XSD is optional,
> but I think that it is optimal. I'm happy, though, if we just
> a URI that has no file extension. We can point it at an HTML
> for now, and then later if we decide to develop an XSD we can point
> there instead.