obfuscation isn't effective to combat spam,
but that's not our
dogfood.
I think we'd all be more than willing to hear suggestions for spam
fighting methods that are equally effective. Or, at least, an offer to
police the recent updates page. :)
-ryan
the semantic of I think this is NSFW
you could use xFolk or hReview and tag the link as 'nsfw'.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.x was
ridiculously buggy.)
4) If this were an existing project with PHP 4.x support, then sure,
maintain support if the cost is reasonable. But for any new project,
I'd say to start on a 5.x codebase.
--
Ryan Parman
http://ryanparman.com
documents in order to understand the correct way to do things. Oh, and
create an automated unit testing suite. It'll save you tons of time in
testing.
--
Ryan Parman
http://ryanparman.com
On Apr 10, 2008, at 6:01 AM, Ciaran McNulty wrote:
On Thu, Apr 10, 2008 at 1:40 PM, Mark Ng
On Apr 10, 2008, at 10:04 AM, Julian Bond wrote:
Ryan Parman [EMAIL PROTECTED] Thu, 10 Apr 2008 09:05:47
As someone with a background in parsing RSS/Atom, I can say from
years of experience that RSS is only occasionally XML and that you
typically find far more HTML in a feed than XML
on those links, which makes them
ignored[1].
-ryan
1. http://microformats.org/wiki/xfn-clarifications#me_nofollow_interaction
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats
On Mar 20, 2008, at 8:27 AM, Costello, Roger L. wrote:
Thanks Ryan! Representative hCard -- nice!
I'm glad you like it.
On a meta point, I'd like to suggest that before people post to this
list saying this is broken that you first do some research on the
wiki and elsewhere. There's a good
smaller, but would lead to people who
encounter those edges cases asking for re-inclusion.
So, in a way, whether values besides 'contact' and 'me' are valuable,
it doesn't matter that much at this point, there are more important
things to work on.
-ryan
This is not a big problem, its mostly solved with [1]
-ryan
1. http://microformats.org/wiki/representative-hcard
On Mar 18, 2008, at 5:31 AM, Costello, Roger L. wrote:
Hi Folks,
Flickr uses XFN. Here is a sample Flickr page that uses XFN:
http://www.flickr.com/people/tantek
On Mar 18, 2008, at 11:38 AM, Costello, Roger L. wrote:
Hi Folks,
Below is a list of social networks that use XFN (special thanks to
David Janes). Following that is a list of social networks that use
FOAF.
Why email these, why not just put them on the wiki?
-ryan
it be too much to ask for this feature to work with *already
deployed content on the web*?
/rant
Come on, microsoft, you're so close to getting it right here!
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
actions as well) in the hopes of
further
minimizing community misbehaviors, and making it clearer to newcomers
what
kinds of behavior are or are not acceptable.
Ryan King (on behalf of the microformats admins[3])
[1] http://microformats.org/wiki/how-to-play
[2] http://microformats.org/wiki
would work in hCalendar.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
/specs/web-apps/current-work/#contact:
| contact: Gives a link to contact information for the current
document.
I've given this feedback to the HTML-WG already. Ian Hickson, one of
the editors, has said he'll address it in HTML5.
-ryan
On Feb 11, 2008, at 6:33 AM, Rickards, Julian (NDM) wrote:
-Original Message-
Please make sure your page is at least well-formed:
http://validator.w3.org/check?uri=http%3A//www.mndm.gov.on.ca/
mndm/mines/lands/pro/contact_e.asp%23devosst
Ryan:
I fixed the page and now it is valid
/contact_e.asp%23devosst
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
that the framers of the HTML 4.01 spec
intended the world set to be interpreted in that way -- far more
likely
they were referring to the layman's definition of the word.
Specs aren't generally written in layman's terms.
-ryan
___
microformats-discuss
as a # and the xmpp url
appears as part of my website url.
I'm, most likely, doing something wrong, but I can't figure it out.
Can anyone help me with this?
There appear to be bugs in that service. Your markup is good, other
than the style=display:none. :)
-ryan
,
span class=country-namePortugal/span
This can be simplified:
a class=url locality href=http://maps.google.com/maps/
msie=UTF8msa=0msid=107254219936498773072.0004442d0067029758c0ll=40.20
36,-8.407588spn=0.010046,0.019033t=kz=16om=0Coimbra/a,
span class=country-namePortugal/span
-ryan
local.yahoo.com. I think its in the 10s of millions.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
parsing algorithm [#html5-parsing].
-ryan
[webstats]: http://code.google.com/webstats/
[html5-parsing]: http://whatwg.org/specs/web-apps/current-work/#parsing
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
On Jan 16, 2008, at 5:56 AM, André Luís wrote:
Hya,
I was interested in folowing this webinar, so I registered for the
event as soon as I heard about it. When I got there the only option to
hear what Ryan was saying was to phone to a certain numbers... given
that there wasn't none available
-webinar
-ryan
PS - Unfortunately its using some proprietary citrix software that
you have to download. I apologize for that and will make sure to
avoid such commitments in the future.
___
microformats-discuss mailing list
microformats-discuss
On Jan 14, 2008, at 1:53 PM, Andy Mabbett wrote:
In message [EMAIL PROTECTED],
ryan [EMAIL PROTECTED] writes
I know this is sorta last minute, but I'm doing a Webinar (web-
seminar) on hResume tomorrow at 10AM PST. It's hosted by the folks
at HR-XML.
I won't be able to join you
If it isn't already, could you please document this on http://
microformats.org/wiki/vcard-implementations ?
thanks,
ryan
On Jan 9, 2008, at 2:58 AM, Barry Cornelius wrote:
We have been successfully using Brian Suda's xhtml2vcal.xsl
(available from http://suda.co.uk/projects/X2V
and it seems to work correctly.
Could you (or someone else?) please add some tests to the test suite
for this?
thanks,
ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats
procedings?
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
/a
becomes parsed as a work-type 'phone number.
I don't think we want to do this, because it puts human-readable data
(work) in a spot that's no longer visible.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
/abbr
Q2. Would it be possible to do something like this, instead?
span class=type title=workPhone/span
@title is only used for abbr for many reasons. I think we have an FAQ
for it somewhere, but can't seem to find it right now.
-ryan
://microformats.org/wiki/hresume#Schema
[4]:
http://microformats.org/discuss/mail/microformats-discuss/2006-December/0075
59.html
--
Ryan Cannon
Application Developer
National Football League
http://ryancannon.com/
___
microformats-discuss mailing list
property as a secondary
classname to the locality resulting in locality org?
Adding an 'org' class name won't change anything in this case, the
locality will be the same.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
in to the
content they create. E.g., a photo and caption from a GPS enabled
cellphone.
Honestly I'd recommend that unless you can put the lat/long in a
human-visible spot, just leave it off.
-ryan
___
microformats-discuss mailing list
microformats-discuss
make it more clear how to use
it well.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
point me in the right
direction)
Operator applies some heuristics to de-dupe microformat instances on
a single page. It sounds like identical SUMMARYs is one of those.
Can we get a url to this page?
-ryan
___
microformats-discuss mailing list
anything (on the wiki, or
elsewhere), so I don't think it's a good idea.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
quite like to see if it's feasible for parsers to
handle this.
Thoughts?
The HTML5 draft covers this a bit: http://www.whatwg.org/specs/web-
apps/current-work/#the-dl
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
). The current methods work and align with user's views of
the world, because the information is already on the page, and the
relationship is well understood by the reader. In other (fewer)
words, the current include pattern is based on current publishing
behavior.
-ryan
tried.
Which parsers, in particular?
Is it my mark-up at fault, or is there some other problem?
It's likely that parsers don't support duration.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org
of markup, not
model, so my database models have been pretty stable.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
(I blame Tantek). Now we parse it all out
into a relatively normalized model. We're at 10^8 or so items now. If
we hit another order of magnitude we'll have to rethink things and
probably take some stuff (like BLOBs) out of the relational database
and put them somewhere else.
-ryan
I go to delicious
assuming they have some, alwasy forgetting because it seems like a
perfect site to host MF's.
Last time I talked to Joshua Schachter (founder of del.icio.us) about
this, we was opposed to microformats in general.
-ryan
anyone tell me if I am completely in the wild here?
My opinion, in short, would be use both.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
note so that you have useful fallback behavior.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
If someone could take a peek at the code I would be really
appreciate it.
Its the first table, the today's upcoming classes table
http://exhale.daisyinteractive.com/locations/santa-monica/
put class='vevent' and id='foo' on the tr and it should work fine.
-ryan
On Sep 13, 2007, at 12:59 PM, [EMAIL PROTECTED] wrote:
Since it belongs here:
http://meiert.com/en/blog/20070913/microformats-and-pseudo-namespaces/
I hope you don't think I'm being overly critical, I just think your
reasoning is flawed in a few ways and doesn't line up with the
it means. :)
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
with significant experience authoring XMDP documents.
Questions about GRDDL would probably best be directed towards the
GRDDL working group.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman
code. I know
Technorati uses kitchen.technorati.com and is spidering microformats,
at the moment they are not displaying XFN (if they index it),...
We do index XFN. I've done a bit of work on ways to display it, but
haven't gotten them release-ready.
-ryan
On Jun 28, 2007, at 1:37 AM, Andy Mabbett wrote:
hQuote anyone? ;-)
http://www.w3.org/TR/html401/struct/text.html#edef-Q
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
couldn't agree more. I think this discussion is rather unproductive
for this community. Just build the tools, design them well and get
people to use them. If you never use the word 'microformat' in your
application, that's fine. No harm, no foul, no need to build a new
brand.
-ryan
values, then I don't need to worry about the text in the
page because the attribute value would be used instead of the text.
You can put the type values in the title attribute of abbr elements
in this case.
-ryan
___
microformats-discuss mailing list
and interoperable (we're working on that,
though [1]).
Many tools use tidy or libxml2's html parsing interface, so most will
work pretty well already.
-ryan
1. http://www.whatwg.org/specs/web-apps/current-work/#parsing
___
microformats-discuss mailing
of the markup (in email) we'd be able to help more.
-ryan
1. http://microformats.org/wiki/vcard-implementations#Microsoft_Outlook
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
the contact info you find.
Currently this requires a bit of hand waving, but I think we can make
it work.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
in XFN.
It's hard to build a network where some nodes can only by sinks[1].
-ryan
1. http://en.wikipedia.org/wiki/Degree_(graph_theory)#Sink
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman
On Jun 13, 2007, at 4:25 PM, Chris Messina wrote:
On 6/13/07, Ryan King [EMAIL PROTECTED] wrote:
On Jun 12, 2007, at 8:15 PM, Chris Messina wrote:
Clearly the biggest issue I see with this scheme is the
inability to
link out *from* the email address. However, I'm not sure that this
case
, if you want to follow web architecture, all urls are opaque, so
it doesn't matter whether the URL has a query string or not.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
://www.all-about-lowering-
cholesterol.com/garlic-cholesterol.htmlGarlic Cholesterol/a
/p
/div
If you want to put the rationale in human readable text, they this
would be a way to do it.
-ryan
___
microformats-discuss mailing list
microformats
) for the vote.
Brian and Ryan have shown that these two items of information are
better expressed using hReview.
Thus, it appears that VoteLinks is redundant at best, and in violation
of the Microformat principles at worst, i.e., it hides rationale
information - human information - in the title
of people on it.
XFN doesn't define how to process a part of a page, only an entire page.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On Jun 1, 2007, at 11:41 AM, Ryan King wrote:
On Jun 1, 2007, at 10:59 AM, David Janes wrote:
I concur. Time to start ramping up for hAtom 0.2, if I can get some
blocks of free time.
I'm more than willing to help. I have time to spend on it right
now. I'll work on collecting issues to deal
On Jun 2, 2007, at 9:11 AM, David Janes wrote:
On 6/1/07, Ryan King [EMAIL PROTECTED] wrote:
On Jun 1, 2007, at 10:59 AM, David Janes wrote:
I concur. Time to start ramping up for hAtom 0.2, if I can get some
blocks of free time.
I'm more than willing to help. I have time to spend
On Jun 3, 2007, at 1:42 AM, Edward O'Connor wrote:
Ryan King wrote:
I think we should use rel-tag tagspaces for atom category schemes.
Sounds good to me. I wrote a bit about how to represent tags within
atom:category here:
http://edward.oconnor.cx/2007/02/representing-tags-in-atom
On May 31, 2007, at 11:29 AM, David Janes wrote:
On 5/31/07, Ryan King [EMAIL PROTECTED] wrote:
Another option is that entry content is:
p class=entry-contentContent/p
p class=entry-contentMore Content/p
Is there a reason why hAtom as currently spec'ed only does text, not
markup?
I
whatever it wants with it from there. If a lot of
people are converting to plain text, though, it would be useful to
specify an algorithm (as we have on http://microformats.org/wiki/
hcard-parsing).
-ryan
___
microformats-discuss mailing list
mapping to term and label (from the tag and
text). I think we should map rel-tag tagspaces to atom:category schemes.
I've put an entry on [2] at [3].
Any reason why we shouldn't do this?
-ryan
1. http://microformats.org/wiki/hatom-issues#rel-tag
2. http://microformats.org/wiki/hatom-issues
3. http
On Jun 1, 2007, at 10:59 AM, David Janes wrote:
I concur. Time to start ramping up for hAtom 0.2, if I can get some
blocks of free time.
I'm more than willing to help. I have time to spend on it right now.
I'll work on collecting issues to deal with.
-ryan
(concatenation with newline), or
4. something else entirely?
Another option is that entry content is:
p class=entry-contentContent/p
p class=entry-contentMore Content/p
Is there a reason why hAtom as currently spec'ed only does text, not
markup?
-ryan
data' title-is-ufhuman data/span
Consumers would all have to be updated. So while it's backwards
compatible with existing content, it isn't future compatible (if you
started publishing this before consumers were updated, your content
would not be handled correctly).
-ryan
else is jumping out from a quick glance - can anyone
spot anything more?
XFN. All of the side bars use [rel=contact].
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
an entire page.
This would make it impossible to have two events with the the same
dtstart, dtend or dtstamp on the same page. I think that makes it
unworkable.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
On May 10, 2007, at 4:45 PM, James Craig wrote:
Ryan King wrote:
James Craig wrote:
Haven't thought too much about this, but are there any obvious
gotchas to using an anchor element with name attribute as a
potential replacement for the abbr-design-pattern?
I believe a[name] and @id
, which is
not something I think we should be considering yet.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
)
AFAIK, there has been 0 interest in robots-exclusion since before we
even launched mf.org. However, if yahoo search is interested in
implementing this, I'd encourage anyone with influence there to point
them at our wiki and encourage them to go through the process.
-ryan
already some notes here:
http://microformats.org/wiki/
Main_Page#microformats_wiki_translations_in_other_languages
Anyone who'd like to create translations of wiki content is welcome
to do so on the mf.org wiki.
-ryan
___
microformats-discuss mailing
simple to
write and backwards-compatible.
[1]: http://tantek.com/log/2005/01.html#d26t0100
[2]: http://www.webreference.com/stats/browser.html
--
Ryan Cannon
Interactive Developer
http://RyanCannon.com
___
microformats-discuss mailing list
On Apr 24, 2007, at 2:25 PM, Drew McLellan wrote:
They're also subprops of fn when n isn't present. But n is present.
They are? If so, that's news to me. Maybe you're referring to the
implied-n rules?
-ryan
___
microformats-discuss mailing list
honorific-prefix and honorific-suffix are subproperties of n, so no,
I don't think it makes more sense.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
you do it in xslt:
http://www.w3.org/2000/07/uri43/uri.xsl
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
that they're of little use. Anyone processing HTML
documents on the web has to deal with relative URLs already (and
base).
Don't change.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman
the latest...
I don't think we have any good overall estimates. AFAIK, no one has
an index of all microformats in the wild. Most estimates I make are
based off of the implementations and examples-in-the-wild pages on
the wiki with some estimates of extrapolation.
-ryan
been low priority, because there
hasn't been much demand for it.
Which parsers are using it, and for which microformats?
It's in our test suite[1] for hCard. X2V uses it, our parser at
Technorati uses it.
-ryan
1. http://hg.microformats.org/tests?f=1672a460cd67;file=hcard/32-
header.html
On Apr 9, 2007, at 12:39 PM, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Ryan
King [EMAIL PROTECTED] writes
Thee are a couple of references, on the wiki, to the table headers
inclusion method and axis in tables, not least:
[...]
Thank you for your answers, but...
Is it part
/span,
span class=given-nameArthur/span
span class=additional-nameErnest/span)
/span
Please don't introduce hidden metadata. That's one of the things
we're trying to avoid with microformats.
-ryan
___
microformats-discuss mailing list
On Apr 4, 2007, at 7:58 AM, Henri Sivonen wrote:
On Mar 28, 2007, at 21:00, Ryan King wrote:
On Mar 28, 2007, at 9:47 AM, Henri Sivonen wrote:
I'd be interested in a design rationale pointer explaining why
having more than two tokens in an fn is not allowed when the
information about
On Apr 4, 2007, at 11:14 AM, Henri Sivonen wrote:
On Apr 4, 2007, at 20:10, Ryan King wrote:
FNs with more than 3 tokens are perfectly fine, it's just that
there's no implied-n rule that can deal with it, so the creator
needs to explicitly mark up N.
Well, that doesn't help. It doesn't
being a link somewhere?
No. xFolk uses rel-tag[1], which is designed to use links for tagging.
-ryan
1. http://microformats.org/wiki/rel-tag
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
microformats-discuss@microformats.org
/module3_7.html
[3]: http://www.liu.edu/CWIS/CWP/library/workshop/citapa.htm
[4]: http://www.libs.uga.edu/ref/chicago.html
--
Ryan Cannon
Interactive Developer
MSI Student, School of Information
University of Michigan
http://RyanCannon.com
___
microformats
. Is this something that has been inherited
wholesale from vCard?
Having more than 2 tokens in an fn is allowed, it's just not useful
for calculating an implied-n.
-ryan
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
microformats
lies.
Type is not required.
-ryan
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
these
problems.
I also think discussion of WYSIWYG-only users is fairly off-topic for
this list because their experience comes through a level of abstraction:
tool developers. We can continue that discussion off-list.
--
Ryan Cannon
Interactive Developer
MSI Student, School of Information
University
On Mar 1, 2007, at 6:25 PM, Joe Andrieu wrote:
Ryan King wrote:
On Feb 20, 2007, at 12:23 PM, Scott Reynen wrote:
And maybe that's because what you're describing is actually more
specific that related hCards implies. It seems here you're just
talking about a single relationship: identity
On Feb 23, 2007, at 1:44 AM, Joe Andrieu wrote:
Ryan King wrote:
I understand this. I agree that this is a desirable goal. I would
personally like to see it happen. However, the simpler
problem of two
hcards representing the same person (or organization) should be
solved first, because
On Mar 4, 2007, at 11:06 PM, Mike Schinkel wrote:
Ryan Cannon wrote:
Adding an @profile attribute to he headelement is far
less technically demanding than, say, creating a tag
space, which we also require. Especially as the addition
also has no performance or usability impact.
It may be less
that the meeting of
either
condition implies the ability to add an @profile as well for 80% of
cases?
--
Ryan Cannon
Interactive Developer
MSI Student, School of Information
University of Michigan
http://RyanCannon.com
___
microformats-discuss mailing
On Feb 20, 2007, at 12:23 PM, Scott Reynen wrote:
On Feb 20, 2007, at 1:05 PM, Ryan King wrote:
However, the simpler problem of two hcards representing the same
person (or organization) should be solved first, because it is a
simpler problem, with a simpler solution (which may not require
suggest that those who want to extend
hResume start by experimenting with their own resumes/CVs.
-ryan
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
=tag href=/
informal.../a/span
?
-ryan
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
:
http://microformats.org/wiki/group-brainstorming
http://microformats.org/wiki/group-examples
There's also prior art in
http://hellonline.com/cgi-bin/trac.cgi/wiki/XMF
Thanks,
ryan
--
Ryan King
[EMAIL PROTECTED]
___
microformats-discuss mailing list
/a
ISBN: abbr class=identifier title=urn:isbn:
15942000681594200068/abbr
span class=identifier
span class=typeLibrary of Congress/span:
span class=valueKF 2979 .L47 2004/span
/span
--
Ryan
http://RyanCannon.com
___
microformats
1 - 100 of 453 matches
Mail list logo
