In message
[EMAIL PROTECTED], Brian
Suda [EMAIL PROTECTED] writes
It is not a valid review yet, you are missing a few things.
[...]
B) create an outer div container. You have a class=photo which is
another hReview property - assuming you are actually intending that to
be part of the hReview,
Currently I use an hAtom+XOXO mix for search results on my pages, but
I have found that hAtom works sufficently for most -- I just wasn't
sure if this was a 'proper' use of it... but I figure it probably is
since you can have RSS for search too...
-- Singpolyma
On 8/30/06, David Janes [EMAIL
Hi,
i'm investigating the use of geo on one of my sites, and i have two open
questions with regards to this:
1) i didn't find what reference system the geo microformat should use.
Although i suppose it is WGS84, neither the original vCard specs nor the
microformats explicitely mention this.
Hi all,
Given recent moves in the job listing by bloggers, I think 'hJob' and
syndication of job data might be a nice near-term topic for discussion.
Thoughts? Links to alternate proposals?
Don Park
___
microformats-discuss mailing list
On Aug 30, 2006, at 9:36 AM, David Janes wrote:
The reason I think that (2) is needed is:
(a) profiles are not manditory, so we can't depend on their presence
(b) the search-results consumer, knowing that there is hAtom search
results, may want not to read the URL at all (prefering a proxy to
On Aug 30, 2006, at 9:52 AM, David Janes wrote:
I'm not sure how to be clearer: my first message in this thread
suggests in point (2) add a single-field extension to OpenSearch XML;
my second message says adding a MIME type is not the solution [1].
OK, so an extension to OpenSearch since
On 8/30/06, Andy Mabbett [EMAIL PROTECTED] wrote:
finnaly, the reviewer hCard is also incorrect:
p id=creditspan class=reviewer vcard fnAndy Mabbett/spanbr
span class=dtreviewed title=200603March 2006/span/p
you need to nest the class=fn inside the class=vcard
p id=credit class=reviewer
On Aug 29, 2006, at 11:28 PM, David Janes wrote:
(2) one could add an extra field to the OpenSearch XML (a description
file about how your results are returned) indicating that the file is
hAtom
There are two problems here, and I think we should avoid approaching
both at once. Just as a
more light:
http://wiki.unto.net/OpenSearch_and_microformats
//Ed
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On Aug 30, 2006, at 8:21 AM, Don Park wrote:
Given recent moves in the job listing by bloggers, I think 'hJob' and
syndication of job data might be a nice near-term topic for
discussion.
Thoughts? Links to alternate proposals?
http://microformats.org/wiki/job-listing-examples
I was going to suggest the same thing, so it's good to see this work
already underway.
My post is a bit dramatic, but what's important about the current
research on this is that it could be used by either applicant *or* job
provider.
I'm not sure if I understand the theory behind the twiki of OpenSearch and
Microformats.
Are you suggesting I modify the opensearch.xml file to include microformat
values, so that when A9 and other search engines gather the content, they
can insert the microformat into their results?
A9 does not
On Aug 30, 2006, at 10:33 AM, Chris Messina wrote:
Just as I can post my own hResume, being able to post jobs
descriptions that I think I'd be good at is an equally important
design goal for this mF. I also think that it's design, perhaps a
slight break with convention, should creatively tackle
Bruce, thanks for clearing that up.
On 8/29/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
Mike,
On 8/29/06, Michael McCracken [EMAIL PROTECTED] wrote:
Do you just mean the ability to mark up a relation between two citation items?
For instance, if BibTeX had a convention of things like this:
On Aug 30, 2006, at 12:36 AM, Andy Mabbett wrote:
I suppose
div class=hreview item
isn't allowed?
http://microformats.org/wiki/hcard-faq#nesting-properties
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
I agree with both of you; and I'm also a big supporter of codifying
existing practices. At the same time, and this may be anathema to the
discussion, but the design of a data format inherently reveals the
underlying politics and biases of the designers.
I'm only suggesting that we make sure that
A question, perhaps: could we design hJob such that it could form a
dovetail joint of sorts with hResume? That is, with any given hResume or
hJob could I find a corresponding set of values that might match the
original query as expressed in either format?
Perhaps. :-) I tend to favor emergent
On 8/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
[... snip ...]
I'm not convinced that a formalized Dublin Core microformat class set
is necessary for a good citation microformat, and I do think it'd be a
distraction to getting the main goal completed.
A reasonable argument; I have no
On 30 Aug 2006, at 13:29, Graham Higgins wrote:
On 29 Aug 2006, at 15:42, Brian S wrote:
you shouldn't make assumptions about what the 'A.' and 'B.'
mean... i did in my example (otherwise it would have been a pretty
boring reply).
There is a service which attempts at guessing the N
On Aug 30, 2006, at 10:43 AM, Ted Drake wrote:
This is a sample product result from the search result page. Where
would the
OpenSearch/hAtom microformats be added?
For the results section, you'd just be adding hAtom to the results,
which someone more involved with hAtom would probably
I am looking for some ammunition on making the case for using hCard
over a standard .vcf file exported from Outlook for a static contact
listing that will likely not change anytime in the future.
--
jeremy flint
www.jeremyflint.com
www.kineticcom.com
Once you have the page marked-up you can easily convert it to ANY
format, not just vCards. You can also submit the page to sources like
kicthen.technorati.com and aggregate the data. It can more-easily be
mashed-up with other data.
-brian
Jeremy Flint wrote:
Well, we ended up not using a
On 8/30/06 11:29 AM, Bruce D'Arcus [EMAIL PROTECTED] wrote:
As for using hCalendar, I think that would be great to mark up
conferences, meetings, etc, in citations, but I don't think a citation
microformat should *require* it. According to the hcard-authoring wiki
page, a minimal hCalendar
Le 30 août 06 à 22:21, Don Park a écrit :
Given recent moves in the job listing by bloggers, I think 'hJob' and
syndication of job data might be a nice near-term topic for
discussion.
Thoughts? Links to alternate proposals?
For inspiration
http://vocab.org/bio/0.1/
On Aug 30, 2006, at 12:42 PM, Michael McCracken wrote:
I'm not convinced that a formalized Dublin Core microformat class set
is necessary for a good citation microformat, and I do think it'd be a
distraction to getting the main goal completed.
A modular system with hDC broken out does seem a
On 8/30/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
On 8/30/06, Timothy Gambell [EMAIL PROTECTED] wrote:
For example, BibTeX's author field implies the medium of the cited
work (if it has an author, it must be text). This makes it difficult
to reuse terminology: what if I'm talking about
26 matches
Mail list logo
