[uf-discuss] rel-tag name case-sensitivity

2006-08-17 Thread Wolfgang Machert

Hello,

Since rel-tag relies on URLs for its tag names, I wonder whether or  
not rel-tag was designed with case-sensitivity in mind (as URLs are  
case-sensitive)

i.e. whether

  http://technorati.com/search/microformat

is a different tag than

  http://technorati.com/search/Microformat


Technorati seems to do its search case-insensitive so am I right to  
assume that tag names behave the same?
If thats how it is it would be helpful to mention this at the  
Specification.


Thanks,
Wolfgang

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Getting started with microformats

2006-08-17 Thread Graham Higgins

Hi,

Relatively new subscriber here. Sorry for the lag in this response.

On 9 Aug 2006, at 18:41, Chris Messina wrote:


We could offer either a case study (XCorp started by locating all
references to people and locations on their website. They then marked
up their pages using hcard. Specifically, this is the code they
changed...)


I've been puzzling over this for a while. I'd like to offer an hcard  
but ...


In my case, there is a set of key individuals who, for operational  
reasons, are not directly contactable. Specifically, they choose not  
to publish their email address or direct line number. An assistant's  
name, email and direct line is advertised as the point of contact for  
the key individual.


I don't see any way of expressing this adequately using μf. Or have I  
just not thought hard enough?


Cheers,

Graham Higgins.




___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Getting started with microformats

2006-08-17 Thread Ciaran McNulty

I did think about using the agent field --- unfortunately, in this
instance John Smith is (in real life) an agent and John Doe is the
agent's assistant. I have a feeling that using the agent's agent
field for the agent's assistant's hcard or the associate agent's
hcard is just going to cause confusion all round.


The vCard 'agent' field strongly means that the enclosed vCard is an
assistant or proxy of the main vCard, it doesn't mean 'agent' in any
of the other senses of the name.

 This type typically is used to specify an area
 administrator, assistant, or secretary for the individual associated
 with the vCard. A key characteristic of the Agent type is that it
 represents somebody or something that is separately addressable.


Looks like it's an unfortunate semantic conflation which is
restricted to this particular domain of discourse.


I suppose if you're using 'agent' to mean something else then yeah,
but that's a risk that all the microformat class names run.

-Ciaran
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] citation: another example of practice in the wild

2006-08-17 Thread David Osolkowski

On 8/16/06, Michael McCracken [EMAIL PROTECTED] wrote:


Yes, I missed that, it does. I think we'd have to use it as a child
element on the link:
a href=link-to-fulltext class=identifierabbr class=format
title=application/pdfPDF/abbr full text link/a


I think it would be better to mark that up as a
href=link-to-fulltext class=identifier type=application/pdffull
text link/a.  No sense reinventing things that already exist in
HTML.

- David
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Getting started with microformats

2006-08-17 Thread David Osolkowski

On 8/17/06, Ciaran McNulty [EMAIL PROTECTED] wrote:


I believe the markup looks something like:

div class=vcard
  span class=fnJohn Smith/span can be reached via his secretary
  span class=agent vcard
span class=fnJohn Doe/span on
span class=tel020  /span
  /span
/div

See http://microformats.org/wiki/hcard-examples#2.4.2_VCARD

A smart parser will convert that correctly and I suspect even a
slightly more simplistic parser would manage to churn out two vCards
with the same telephone number for both parties.


Would this not be subjected to the same parsing issues as nested
hCards in general (see
http://microformats.org/discuss/mail/microformats-discuss/2006-August/005130.html)?
I'd think a smart parser could properly deal with nested hCards, but
Brian seemed pretty convinced any parser would mess things up.

- David
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Getting started with microformats

2006-08-17 Thread Graham Higgins


On 17 Aug 2006, at 14:03, Ciaran McNulty wrote:


I did think about using the agent field --- unfortunately, in this
instance John Smith is (in real life) an agent ...
The vCard 'agent' field strongly means that the enclosed vCard is  
an assistant or proxy of the main vCard, it doesn't mean 'agent' in  
any of the other senses of the name.


Well yes, that is strictly true in the context of RFC 2426 but it  
does seem to be a somewhat infelicitous choice of label, given that  
it is a user-facing data structure.


 This type typically is used to specify an area administrator,  
assistant, or secretary for the individual associated with the  
vCard. 


Thanks for drawing my attention to that, fie on me for missing it the  
first time through.


A key characteristic of the Agent type is that it represents  
somebody or something that is separately addressable.


Just in case I've misunderstood: in this context, does your  
understanding of the term addressable yield any special meaning  
beyond the generic capable of being manipulated independently? The  
term doesn't seem to be defined any more precisely in the RFC and I  
rather hoped to be able to provide the URI of an hCard for transclusion.


Anyway, reporting back: thanks for the assist. I now have a chunk of  
XHTML which can be processed by Brian Souda's xhtml2vcard parser  
(mostly) correctly - the hcard owner is incorrectly assigned the  
agent's title --- the agent template of the xsl stylesheet is  
commented out with a remark referencing further work to be done.


The XHTML can also be processed (mostly) correctly by Tantek's  
favelet (which uses the technorati stylesheets) --- the agent fn is  
omitted from the vCard but I couldn't say whether this is expected  
behaviour. For my own purposes, I rectified the omission by adding it  
in a note.


Thanks again,

Graham.




___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss