Simple and elegant
For some reason I'd always thought base was something set in the http header
rather than the markup
The longer I spend with html the less I think I know
Anyway thanks for your help
On 23/4/07 13:22, Brian Suda [EMAIL PROTECTED] wrote:
On 4/23/07, Michael Smethurst [EMAIL
OK, ok, ok... My mistake
I'd assumed that uf parsers couldn't handle non full path urls... Silly on
my part
In mitigation:
- I'm not sure the uf wiki makes this clear
- All the examples on the wiki seem to use full path urls
- By default using url_for on RoR gives full path urls (check twitter).
On 4/23/07, Michael Smethurst [EMAIL PROTECTED] wrote:
But the question remains:
Microformats aside, if I'm making a new website from scratch (no legacy
code/markup) and I want to encourage others to hack, mashup, interwingle it
with other data is it best to use /radio4 or
Brian Suda [EMAIL PROTECTED] writes:
you can have the best of both worlds. In each a href= just use
/radio4. This makes the link relative. But then you can also add a
base href=http://bbc.co.uk/; when this is in your HTML it will make
all the hrefs absolute (or it should for any decent
On 4/23/07, Brian Suda [EMAIL PROTECTED] wrote:
you can have the best of both worlds. In each a href= just use
/radio4. This makes the link relative. But then you can also add a
base href=http://bbc.co.uk/; when this is in your HTML it will make
all the hrefs absolute (or it should for any
On 4/23/07, David Janes [EMAIL PROTECTED] wrote:
The advantage of using the base element is that you can easily
switch it to something like base href=http://my-dev-site.bcc.co.uk;
and you don't have to rewrite all the hrefs within the HTML.
With the slight downside that it makes your code a
On 4/19/07, Michael Smethurst [EMAIL PROTECTED] wrote:
Afternoon all
Standard practice at the beeb has always been to use link urls relative to
the root:
href=/radio4/today
Clearly these are of little use in a microformat (or any attempt to use html
as an api)
So my question is - are there
David Janes [EMAIL PROTECTED] writes:
The reason that there has been little discussion is that the rules for
dealing with this are well understood and settled. This document [1]
will give you everything you need -- written in 1995.
Regards, etc...
[1] http://www.ietf.org/rfc/rfc1808.txt
I
On 4/20/07, Nic James Ferrier [EMAIL PROTECTED] wrote:
David Janes [EMAIL PROTECTED] writes:
The reason that there has been little discussion is that the rules for
dealing with this are well understood and settled. This document [1]
will give you everything you need -- written in 1995.
Mike Kaply [EMAIL PROTECTED] writes:
On 4/20/07, Nic James Ferrier [EMAIL PROTECTED] wrote:
David Janes [EMAIL PROTECTED] writes:
The reason that there has been little discussion is that the rules for
dealing with this are well understood and settled. This document [1]
will give you
On Apr 20, 2007, at 6:08 AM, Nic James Ferrier wrote:
David Janes [EMAIL PROTECTED] writes:
The reason that there has been little discussion is that the rules
for
dealing with this are well understood and settled. This document [1]
will give you everything you need -- written in 1995.
Afternoon all
Standard practice at the beeb has always been to use link urls relative to
the root:
href=/radio4/today
Clearly these are of little use in a microformat (or any attempt to use html
as an api)
So my question is - are there any problems we should be aware of in
switching to full
Hello Michael,
What's the problem with using relative URLs (in Microformats)?
Any software that looks for Microformats can figure out the absolute
URL itself (from the relative URL).
There shouldn't be any problem.
And thus... there is no need for you to switch from relative URLs to
absolute
On Apr 19, 2007, at 9:45 AM, Michael Smethurst wrote:
Afternoon all
Standard practice at the beeb has always been to use link urls
relative to
the root:
href=/radio4/today
Clearly these are of little use in a microformat (or any attempt to
use html
as an api)
It's not clear that
14 matches
Mail list logo
