Re: [rss-public] Re: RSS : a "namespace" in itself ?
- On 5 Feb 2009, at 05:20, James Holderness wrote:
> rcade wrote:FWIW, SimplePie used to support the Userland namespace, but dropped
>> I look forward to seeing the results of your test,
> Results now up on my blog:
support for it seeming it was used nowhere and does have a cost. It
appears (looking with grep…) to have been introduced for 1.0 Beta 2
and removed for 1.0 RC1 (i.e., the last release with support was 1.0
Beta 3 Bugfix 2). However, these versions oddly seem to match
element's expanded names case-insensitively (I'm sure I thought there
was some good compat. reason for this at the time). Furthermore,
versions prior to 1.0 Beta 2 (though maybe not 0.8, but I never had
anything to do with that) will have worked with all but the prefixed
variations (due to not using a namespace-aware XML parser).
To my knowledge, nothing broke by moving to a namespace-aware parser,
and nothing broke removing support for the Userland namespace.
- 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 email@example.com, "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.