- ... “RSS is an XML vocabulary.” ... “It can incorporate other vocabularies if they have a namespace. Namespaces must be declared with `xmlns`Message 1 of 42 , Feb 2, 2009View Source* secou <secou@...> [2009-02-02 16:30]:
> RSS is an XML dialect.“RSS is an XML vocabulary.”
> It can handle external namespaces declared by "xmlns"“It can incorporate other vocabularies if they have a namespace.
Namespaces must be declared with `xmlns` attributes.”
> But, hum, do you consider RSS as "namespace" in itself? Or isNo. Yes.
> it incorrect to use this word.
> In fact, I try to explain "namespace", in an RSS/Atom andSee above.
> modules/extensions view, describing it as a group of elements
> all possibly used in a specific goal, and needing to be
> declared to avoid polysemic confusion.
> But how would you explain that RSS is a namespace... but that
> you don't have to declare it the usual way... (with "xmlns") ?
> Is the "<rss version=2.0>... </rss>" section enough to say that
> the RSS namespace is the basic namespace I the newsfeed ?
Aristotle Pagaltzis // <http://plasmasturm.org/>
- 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 aMessage 42 of 42 , Feb 12, 2009View SourceAwesome! 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.