Re: rel=tag problem

On Fri, 14 Mar 2008 15:58:46 -0600,  Scott Reynen
<Scottrandomchaos.com> wrote:
>  I believe you're wrong.  I'm not aware of any
resolution to the
>  outstanding issue of multi-word tags:
>  http://microformats.org/wiki/rel-tag-issues#Multi-wor
d_tags

But the specification clearly states that spaces should be
encoded
with + or %20, and wordpress is encoding them as dashes.

http://microformats.org/wiki/rel-tag#Encoding_issues

Doesn't this symanticly change a "multiple word
tag" into a
"compound-word-tag", and isn't this precisely why
the specification
states that spaces should be + and %20 (as it is in the
HTML
standard)?

> this is a non-issue because the meaning of tags is
>  contextually dependent on the tag space, so there's no
possibility for
>  standardization around what tags mean, whether they're
single- or
>  multi-word.

I'm not sure I follow what you mean here.  Since the meaning
of a tag
is dependent on the space - whether its a "multiple
word tag" vs a
"compound-word-tag" ... doesn't that mandate that
spaces are encoded
distinctly (as both the microformat and html standard
state)?

In any case thank you for the reply.  I look forward to
figuring this
out, because as it stands wordpress blogs are not aggregated
in the
same/correct? tag cloud space as posts from other blogging
tools are
... and it seems to be because wordpress is determined to
change
"multiple word tags" into
"one-single-compound-word-tag" no matter
what.  It's very frustrating when trying to participate in
distributed
groups/conversation/projects and you can't even manually set
the
spaces correctly (as per the microformat specification
stated at the
above url) and wont show up in the correct tag listings.

- Dave
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

On Mon, Mar 17, 2008 at 3:23 AM, David Meade
<meade.davegmail.com> wrote:
>  But the specification clearly states that spaces
should be encoded
>  with + or %20, and wordpress is encoding them as
dashes.
>  
http://microformats.org/wiki/rel-tag#Encoding_issues

It's a SHOULD, not a MUST - + or %20 is best practice,  but
wordpress
is free to use a different scheme if they already have a
system in
place that rel-tag is being bolted on to.

It would be great if they could change it, but we have to be
aware
that the concept of tagging both predates and is more widely
known
than rel-tag.

>  > this is a non-issue because the meaning of tags
is
>  >  contextually dependent on the tag space, so
there's no possibility for
>  >  standardization around what tags mean, whether
they're single- or
>  >  multi-word.
>
>  I'm not sure I follow what you mean here.

It pretty much means aggregation is hard.  Aside from issues
like
encoding of spaces, which we've been discussing here,
there's a whole
host of other issues.

As an example, a wiki about metal might have 'lead' as a
tag, whereas
a site about dogs might have a 'lead' tag that's a synonym
for
'leash'.

This is the reason that URL prefixes are included in the
semantics of
tagging - different tagspaces will associate different
meanings with
different tags, compound or otherwise.  Aggregation where
URLs are
discarded is always going to be a lossy process at best and
that
applies to character encoding too.

-Ciaran McNulty
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss