[uf-discuss] Microformats and Football

Tue Feb 13 07:13:36 PST 2007

Dear friends,

This is my first post to the list, so please forgive me if this is
inappropriate.

I´m trying to find information about microformats in sports, more
specifically football (soccer for the americans). I´m involved in a project
that will expose lots of data such as match results, scouts, player
information and the like, and could not help but think about using
microformats to expose this data.

Any suggestions or ideas?

Yours thankfully,

Danilo Medeiros

-----Mensagem original-----
De: microformats-discuss-bounces at microformats.org
[mailto:microformats-discuss-bounces at microformats.org] Em nome de
microformats-discuss-request at microformats.org
Enviada em: terça-feira, 13 de fevereiro de 2007 09:33
Para: microformats-discuss at microformats.org
Assunto: microformats-discuss Digest, Vol 21, Issue 28

Send microformats-discuss mailing list submissions to
	microformats-discuss at microformats.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://microformats.org/mailman/listinfo/microformats-discuss
or, via email, send a message with subject or body 'help' to
	microformats-discuss-request at microformats.org

You can reach the person managing the list at
	microformats-discuss-owner at microformats.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of microformats-discuss digest..."

Today's Topics:

   1. Re: SOURCE+URL to indicate authoritative hCard (was	UID+URL
      vs. VIA) (Brian Suda)
   2. Re: [advocacy] Contacting Blogger (was Re: [uf-discuss]
      Rel-tag	issues...) (James Craig)
   3. RE: Training events in hResume (Steve Ganz)
   4. Re: [advocacy] Contacting Blogger (was Re: [uf-discuss]
      Rel-tag	issues...) (Ben Buchanan)
   5. Re: SOURCE+URL to indicate authoritative hCard (was	UID+URL
      vs. VIA) (Ryan King)
   6. Re: SOURCE+URL to indicate authoritative hCard (was	UID+URL
      vs. VIA) (Scott Reynen)
   7. Re: Tutorial on AHAH (such a cool technology!) (Benjamin West)
   8. Re: Training events in hResume (Rob Crowther)
   9. Re: Tutorial on AHAH (such a cool technology!) (Ara Pehlivanian)

----------------------------------------------------------------------

Message: 1
Date: Mon, 12 Feb 2007 20:49:34 +0000
From: "Brian Suda" <brian.suda at gmail.com>
Subject: Re: [uf-discuss] SOURCE+URL to indicate authoritative hCard
	(was	UID+URL vs. VIA)
To: "Microformats Discuss" <microformats-discuss at microformats.org>
Message-ID:
	<21e770780702121249m21e0d79bh74e833fffa4dca31 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 2/12/07, Scott Reynen <scott at randomchaos.com> wrote:
> On Feb 12, 2007, at 1:05 PM, Ryan King wrote:
>
> >> Has anyone looked at using the SOURCE property from vCard to 
> >> indicate a more authoritative hCard?  It seems to be much closer to 
> >> what we're talking about than UID.  The value is already defined as 
> >> URI.
> >
> > SOURCE is already used by X2V to indicate the URL at which the 
> > current hCard is available. I don't think we'd be able to override 
> > that at this point.

SOURCE is just the 'source' of where the the hcard came from.

2.1.4 SOURCE Type

   If the SOURCE type is present, then its value provides information
   how to find the source for the vCard.

-brian

--
brian suda
http://suda.co.uk

------------------------------

Message: 2
Date: Mon, 12 Feb 2007 13:25:10 -0800
From: James Craig <jcraig at apple.com>
Subject: Re: [advocacy] Contacting Blogger (was Re: [uf-discuss]
	Rel-tag	issues...)
To: Microformats Discuss <microformats-discuss at microformats.org>
Message-ID: <02536C42-DF21-46EF-A564-0E97733329A8 at apple.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Scott Reynen wrote:

> This may not solve 100% of issues, but I think Blogger could make  
> over 90% of plain-old web hosts work with the current rel-tag spec  
> by simply uploading tagname/index.html instead of tagname.html and  
> then point links to tagname/ (which resolves to index.html on most  
> plain-old web hosts).

The simplest solution is usually the best, eh? Good idea. *slaps  
forehead*

For the record though, I still think there should be markup-only  
fallback, such as putting the tagName in a title attribute.

either
<a rel="tag" href="/search/tag/foo">All uses of FOO</a>
or
<a rel="tag" title="foo" href="/search?tag=foo">All uses of FOO</a>

------------------------------

Message: 3
Date: Mon, 12 Feb 2007 13:53:01 -0800
From: "Steve Ganz" <steve at ganz.name>
Subject: RE: [uf-discuss] Training events in hResume
To: "'Microformats Discuss'" <microformats-discuss at microformats.org>
Message-ID: <00ae01c74ef0$2cfe7660$6501a8c0 at FIVE>
Content-Type: text/plain;	charset="US-ASCII"

On Sunday, February 11, 2007 6:49 PM Rob Crowther wrote

> Today I've been working on completing the hResume markup on my CV [1].
>  I have a section devoted to training courses I've been on 
> and other lectures/presentations I've attended.  Can anyone 
> advise, would this be better marked up as 'education', or 
> just plain hCal or perhaps even just use rel-tag, like it's a 
> skill?  It seems to me that education is really school and 
> university rather than attending training courses or 
> lectures, but I could be interpreting it wrong, I couldn't 
> find much in the way of examples.

	It really comes down to how you want this information categorized
elsewhere when it's out of the context of your visually formatted CV. In
other words, the hResume parsers that might consume your CV will not take
the heading of "Training" with it and will lump the lectures/presentations
with your "Education".

> I have started marking them up as class="training vevent".

	That makes sense.

Best,
Steve

------------------------------

Message: 4
Date: Tue, 13 Feb 2007 09:27:54 +1100
From: "Ben Buchanan" <microformats at 200ok.com.au>
Subject: Re: [advocacy] Contacting Blogger (was Re: [uf-discuss]
	Rel-tag	issues...)
To: "Microformats Discuss" <microformats-discuss at microformats.org>
Message-ID:
	<6ca82b0f0702121427t365c5e2k4c91c90279a87ede at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

> This may not solve 100% of issues, but I think Blogger could make
> over 90% of plain-old web hosts work with the current rel-tag spec by
> simply uploading tagname/index.html instead of tagname.html and then
> point links to tagname/ (which resolves to index.html on most plain-
> old web hosts).

I'm hoping they switch to the tagname/index.html solution - it seems
logical enough and the only downside would be some more FTP overhead
(which I for one am more than willing to wear). Unless of course
there's something in Blogger's code base which would come into play.

Personally I'd like to see the directory+index.html solution for all
Blogger pages, it'd pave the way to eventually allow other formats
like PHP, for one thing. But anyway, that's off the topic.

cheers,
Ben

-- 
--- <http://weblog.200ok.com.au/>
--- The future has arrived; it's just not
--- evenly distributed. - William Gibson

------------------------------

Message: 5
Date: Mon, 12 Feb 2007 14:40:46 -0800
From: Ryan King <ryan at technorati.com>
Subject: Re: [uf-discuss] SOURCE+URL to indicate authoritative hCard
	(was	UID+URL vs. VIA)
To: Microformats Discuss <microformats-discuss at microformats.org>
Message-ID: <5F5453C6-9141-4EE6-B1E1-3ECEFE672D61 at technorati.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On Feb 12, 2007, at 12:49 PM, Brian Suda wrote:

> On 2/12/07, Scott Reynen <scott at randomchaos.com> wrote:
>> On Feb 12, 2007, at 1:05 PM, Ryan King wrote:
>>
>> >> Has anyone looked at using the SOURCE property from vCard to
>> >> indicate a more authoritative hCard?  It seems to be much closer
>> >> to what we're talking about than UID.  The value is already
>> >> defined as URI.
>> >
>> > SOURCE is already used by X2V to indicate the URL at which the
>> > current hCard is available. I don't think we'd be able to override
>> > that at this point.
>
> SOURCE is just the 'source' of where the the hcard came from.
>
> 2.1.4 SOURCE Type
>
>   If the SOURCE type is present, then its value provides information
>   how to find the source for the vCard.

SOURCE in vCard is essentially the same as self in Atom (AFAICT).

-ryan

--
Ryan King
ryan at technorati.com

------------------------------

Message: 6
Date: Mon, 12 Feb 2007 17:13:19 -0600
From: Scott Reynen <scott at randomchaos.com>
Subject: Re: [uf-discuss] SOURCE+URL to indicate authoritative hCard
	(was	UID+URL vs. VIA)
To: Microformats Discuss <microformats-discuss at microformats.org>
Message-ID: <DD1FA3FF-0C9E-4518-9630-F6955907D66E at randomchaos.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On Feb 12, 2007, at 4:40 PM, Ryan King wrote:

>> SOURCE is just the 'source' of where the the hcard came from.
>>
>> 2.1.4 SOURCE Type
>>
>>   If the SOURCE type is present, then its value provides information
>>   how to find the source for the vCard.
>
> SOURCE in vCard is essentially the same as self in Atom (AFAICT).

I think SOURCE is actually closer to VIA in Atom, as "the source of  
the information provided in the containing element," which is why I  
suggested it.  As I understood the arguments between UID+URL and VIA  
(and I may well have missed some key points), UID+URL is good because  
it's already in vCard, but bad because not all UIDs point to more  
authoritative hCards.  And VIA is good because the source of  
information is always more authoritative than the derivative, but bad  
because it's not already in vCard.  So SOURCE+URL seems good because  
the source of information is always more authoritative than the  
derivative, and also good because it's already in vCard.

vCard's SOURCE is taken from RFC 2425, which offers an explanation  
that sounds to me like what we're trying to accomplish:

> The SOURCE type is used to provide the means by
> which applications knowledgable in the given directory service
> protocol can obtain additional or more up-to-date information from
> the directory service.

"Additional or more up-to-date information" is what we're looking for  
in an authoritative hCard, right?

Peace,
Scott

------------------------------

Message: 7
Date: Mon, 12 Feb 2007 17:00:31 -0800
From: "Benjamin West" <bewest at gmail.com>
Subject: Re: [uf-discuss] Tutorial on AHAH (such a cool technology!)
To: "Microformats Discuss" <microformats-discuss at microformats.org>
Message-ID:
	<8ad71be30702121700pb61c8a9tef42c06a1bf06f7c at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Roger,
Neat stuff. I thought it was pretty good, but take some issue with the
following:

  <a href="javascript:ahah('Waldorf-Astoria-Photo.html','Photo');">photo</a>

The best practice is to wire the event up, and to use a button when
the element is not truly a link.

Something more like:

  <button
onclick="ahah('Waldorf-Astoria-Photo.html','Photo');">photo</button>

or even better:

<button id="photo_changer" type="button" >photo</button>
<script type="text/javascript>
// must be done either after onload fires or after the element appears
in the DOM...
// find the element.
photoButton = document.getElementById('photo_changer');
// wire up the event.
photoButton.onclick = function () {
  ahah('Waldorf-Astoria-Photo.html','Photo');
};
</script>

-Ben

On 2/10/07, Costello, Roger L. <costello at mitre.org> wrote:
> Hi Folks,
>
> I have created a tutorial on AHAH (Asynchronous HTML and HTTP)
>
>        http://www.xfront.com/microformats/AHAH.html
>
> Comments welcome.
>
> /Roger
>
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>

------------------------------

Message: 8
Date: Tue, 13 Feb 2007 11:23:09 +0000
From: "Rob Crowther" <robertc at gmail.com>
Subject: Re: [uf-discuss] Training events in hResume
To: "Microformats Discuss" <microformats-discuss at microformats.org>
Message-ID:
	<3ce2ebd20702130323n28897ca9h33521323803dcccc at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 12/02/07, Pat Ramsey <ramsey.pat at gmail.com> wrote:
> Training being a learning experience, I would think marking it up as
> education is appropriate.
>
But work is (or perhaps should be) a 'learning experience' too.  It's
not quite the same thing, but most application forms I've filled in
have had separate sections for Education and Training.

A quick google for some examples:

1 -
http://www.chichester.gov.uk/your_council/council_jobs/copy_of_job_appln_for
m1.cfm
(link to Word doc on page) - Has an 'EDUCATION & PROFESSIONAL
QUALIFICATIONS' section, separate boxes for schooling, professional
qualifications and 'other relevant training' but all under the same
heading.

2 -
http://www.tendringdc.gov.uk/NR/rdonlyres/E8AE5F2D-4F09-46F7-8044-9A45A924CD
CE/0/ApplicationForm130306.pdf
- seperate sections for Education and Professional Qualifications

3 - http://www.unison.org.uk/acrobat/B1491.pdf - separate sections for
Education and Training, though the distinction is that anything which
leads to a qualification is Education, and everything else is
Training.  This is perhaps a more useful practical distinction than
the slightly nebulous concepts I had in mind.

4 - http://www.scope.org.uk/downloads/jobs/jobapp_may05.doc - similar
to 3, things with an exam are Education, other things are Training.

5 - http://www.rhul.ac.uk/personnel/application.pdf - similar to 1,
all in one section but sperate boxes for School, Further/Higher
Education, Formal Qualifications and Other Training

6 - http://www.broxtowe.gov.uk/application_form_april_2006.pdf -
Education and Training all in the same box/section.

On the basis of the above examples, I would suggest that a distinction
between education and training could be useful as clearly employers
sometimes see them as distinct concepts.

Rob

------------------------------

Message: 9
Date: Tue, 13 Feb 2007 07:30:46 -0500
From: "Ara Pehlivanian" <ara.pehlivanian at gmail.com>
Subject: Re: [uf-discuss] Tutorial on AHAH (such a cool technology!)
To: "Microformats Discuss" <microformats-discuss at microformats.org>
Message-ID:
	<923a87360702130430w46d10241q5265c9a645e33cfe at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 2/12/07, Benjamin West <bewest at gmail.com> wrote:
> Roger,
> Neat stuff. I thought it was pretty good, but take some issue with the
> following:
>
>   <a
href="javascript:ahah('Waldorf-Astoria-Photo.html','Photo');">photo</a>
>
> The best practice is to wire the event up, and to use a button when
> the element is not truly a link.
>
> Something more like:
>
>   <button
onclick="ahah('Waldorf-Astoria-Photo.html','Photo');">photo</button>
>
> or even better:
>
> <button id="photo_changer" type="button" >photo</button>
> <script type="text/javascript>
> // must be done either after onload fires or after the element appears
> in the DOM...
> // find the element.
> photoButton = document.getElementById('photo_changer');
> // wire up the event.
> photoButton.onclick = function () {
>   ahah('Waldorf-Astoria-Photo.html','Photo');
> };
> </script>
>
> -Ben
>

Just one thing, <button> isn't a valid HTML tag. You'd be better off
using <span> (unless you're working with the XML DOM of course).

A.

------------------------------

_______________________________________________
microformats-discuss mailing list
microformats-discuss at microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

End of microformats-discuss Digest, Vol 21, Issue 28
****************************************************