- From: Dan Connolly <connolly@w3.org>
- Date: Mon, 07 Apr 2008 16:42:22 -0500
- To: Brian Suda <brian.suda@gmail.com>
- Cc: public-grddl-wg <public-grddl-wg@w3.org>
On Fri, 2008-04-04 at 14:09 +0000, Brian Suda wrote: [...] > What are people's thoughts. Is it worthwhile to have a single master > profile, or is the modular approach better? The downside of a massive > profile would be that it "squats" on all the terms. So if you are only > using XFN, it is redefining all the other terms within the page as > well. That cost seems pretty small, to me. Where does it show up? I guess a straightforward GRDDL implementation would run several pieces of XSLT, but if that cost got big, somebody could produce an optimized XSLT transformation to replace the individual pieces. When I have actually tried to exploit data from multiple microformats on one page, I tend to need a little bit more smarts/semantics than the microformats specs give you... things to connect events to people or something; I can't remember the details just now. So I end up making my own profile. I think the specific case was http://www.w3.org/2007/07dc-lhr/aa-lhr Hmm... it seems that I just used eRDF... I thought I had made stronger conclusions from my markup than the microformats specs warranted. I guess I made the stronger connections explicit with eRDF. The eRDF transformation seems to explicitly check for the eRDF profile; it doesn't work when invoked indirectly, so this idea didn't work: http://www.w3.org/2002/12/cal/cardcaletc > The up-side is that it is only 1 URL to include. > > I can bring it up on the microformats list for a clarification if one is needed. -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ gpg D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Monday, 7 April 2008 21:42:51 UTC