community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: Where's the code?
Date Thu, 22 Jun 2017 00:01:58 GMT
On 22 June 2017 at 00:56, Shane Curcuru <> wrote:
> I like Owen's common urls idea elsethread, which would be great for
> projects that are willing to use those URLs, but that's not something
> we're likely to require.
> Rich Bowen wrote on 6/21/17 4:40 PM:
>> On Jun 21, 2017 20:12, "Shane Curcuru" <> wrote:
>> If we're doing something new, why not use rel="" values?
>> We could even abuse the rel= attribute to add some of our own keys if we
>> really wanted to.  This would make link checking super-easy for sites
>> that use it.
>> Not a clue what you're suggesting. Can you be more specific? Or give an
>> example?
> HTML standard(s) allows a rel="" attribute on <a...> tags.  One value is
> rel="license", which "indicates that the hyperlink leads to a document
> describing the licensing information".
> Various unofficial microformats also use things like rel="friend" for my
> homepage link that points to Rich's blog, because he's a friend.
> We could (ab)use this to add our own set of rel="trademark" values that
> the Whimsy site checker (either for policy links, or for recommended
> links like these) could scan for.  This is more valuable when some
> projects want the link *text* to say "source repository" and other
> projects want it to say "github repo" or the like.
> But if we're going to propose patches to a bunch of websites, having a
> set of rel= values that we consistently use might be a really simple way
> to add structure to the links, even if we're making up our own values.

In which case, maybe an "asf-" prefix would be sensible to avoid
possible clashes with official rel names.

> - Shane
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message