On Tue, Jul 20, 2010 at 1:07 PM, Philip Jägenstedt wrote:
> Well, it's not in W3C's version of HTML5, they published it as a separate
> spec (which is strange, IMO). Regardless of what spec it is in, it still
> works just the same, so that's OK.
Oh, really? Sorry, I'm out of date in that case.
I
On Tue, Jul 20, 2010 at 5:05 AM, Angelo Gladding wrote:
> Can an enlightened soul describe in which ways microdata is actually
> superior to profiled poshformats?
To me it's not a question of Microdata vs POSH, it's more like
Microdata vs class attributes where both are methods that can be used
i
he value-class-pattern [1]
One of the examples is given as follows:
mobile
+44 7773 000 000
This would seem to have obvious uses for i18n.
-Ciaran McNulty
[1]
http://microformats.org/wiki/value-class-pattern#Parsing_value_from_a_t
Is it in a public setting, or is it all behind-doors talks?
-Ciaran McNulty
[1] http://tinyurl.com/daj7j8
On Sun, Feb 15, 2009 at 4:27 PM, Toby A Inkster wrote:
> Brian Suda wrote:
>
>> Google has started to use rel-canonical to specific the best URL for
>> page information.
George
Looks good!
You might want to handle URLs with the http:// omitted.
-Ciaran McNulty
On Mon, Feb 16, 2009 at 11:47 AM, George Ornbo wrote:
> Hi all
>
> I'd like to share an example I knocked up showing how YQL can be used
> to populate forms using just a URL.
>
>
e going to have
hidden data (and frankly from what I can tell from discussions so far
about this, we're heading that way) it's better that its 'near' the
visible version in the HTML rather than being hidden in the HEAD.
-Ciaran McNulty
__
El Greco = nickname
However I don't think there's any hard-and-fast rule about it.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
any feedback about:
A. Whether this is a problem that needs solving, or if there's an
obvious way of representing these events in hCalendar that we've all
missed.
B. Whether it needs to be solved by adding a concept of 'now' to
hCalendar or whether it needs to be solved in
in en_us and not worry too much about it.
The idea of internationalising uF fields is too horrific to
contemplate, after all!
See also text-align: center;
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
pect alphabetically
b) All together under N
c) Nulty separately with McNulty and MacNulty listed together in a
separate Mc section after the M section.
That said I think sorting is a bit out of scope for hCard and would
consider O'-, Fitz-, Mc- and Mac- prefixes to be parts
Another example of non-Gregorian calendaring is Saudi Arabia, where
the arabic calendar is in common usage:
http://www.sama.gov.sa/
(actually clicking the 'english' tab on that page shows the gregorian dates)
-Ciaran McNulty
On Tue, Jul 15, 2008 at 3:40 AM, Karl Dubost <[EM
s seems to be that hidden data is ok for machine data,
as long as it's right next to the human-readable date in the HTML (so
that it's less likely to be overlooked when editing).
However, -1 from me for using @class in that way - I think it breaks
On Sun, Jun 29, 2008 at 3:07 PM, Duncan Cragg <[EMAIL PROTECTED]> wrote:
> Those of us who favour opaque URLs (actually for practical reasons such as
> clean separation of concerns, maintainability, etc.) are unhappy with being
> forced into a semantic URL schema when using rel-tag.
Can you go int
sign pattern
> seems relatively the best way to do the job, but it's not perfect.
As another aside, HTML5 has the proposed TIME element for exactly this.
Friday 5pm
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@micro
On Wed, May 14, 2008 at 2:38 PM, Toby Inkster <[EMAIL PROTECTED]> wrote:
> I'm sorry, but this sounds like a really bad idea. Parsers would need to
> maintain translation tables for day and month names, plus abbreviations
> for them,
I agree that it sounds a bit over the top for hCalendar but it's
On Thu, Apr 10, 2008 at 1:40 PM, Mark Ng <[EMAIL PROTECTED]> wrote:
> XFN itself is fairly easy to deal with by just throwing pages through
> tidy and using DOM/SAX/xPath, surely ? I made a rudimentary parser to
> do this some time ago. The code is a little ugly to publish, but I
> don't mind
On Thu, Apr 10, 2008 at 10:48 AM, Ciaran McNulty <[EMAIL PROTECTED]> wrote:
> The only problem I can see is that it doesn't handle invalid HTML that
> well (an example would be http://ciaranmcnulty.livejournal.com/).
In fact it does just look like you need to turn down erro
would be http://ciaranmcnulty.livejournal.com/).
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
t
immeasurable IMO.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
s 'live', but because it's Google they can return all the results
in one response to your query, and it saves you spidering the site
yourself and worrying about all the complexity that would involve.
Alternatively, if you want to parse uFs in PHP, I believe hKit by Drew
McLell
value should be visible.
Quite, but entry-title should only be on an image when that image
contains the text of the title (bad practice admittedly).
So in this case the @alt should contain the text in the image.
-Ciaran McNulty
___
microformats-discu
in other languages is really a side issue (but there
are already existant hCard->PHP services, for instance).
Basically iff we're going to be talking about JSON representations
maybe it's good if other languages can benefit from it.
-Ciaran McNulty
__
ead JSON parsing packages - I would
have thought PEAR would have one but they don't seem to.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
e a strong opinion about this? I
realise that at the moment it's a side issue.
Is there an obvious representation in any other programming languages?
-Ciaran McNulty
[1] http://uk2.php.net/json
___
microformats-discuss mailing list
micro
hors.
Conversely, I would propose that 'n' values are mandatory in jCard to
make things easier for parsers, and that converters be responsible for
applying the defaulting rules.
-Ciaran McNulty
___
microformats-discuss mailing list
y
anyhow, for most real-world applications. Keeping vCard names is more
useful than changing them for very little gain.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On Thu, Mar 27, 2008 at 9:59 AM, Dan Brickley <[EMAIL PROTECTED]> wrote:
>
> On 27 Mar 2008, at 07:34, Ciaran McNulty wrote:
> > The simplest way to stop it is to add @rel="nofollow" to any comment
> > links - this has the effect of negating any XFN va
ve said, this is a publishing issue rather than a parsing
issue. A page that is linked to with @rel="me", and then allows
outbound XFN values authored by people who are not the representative,
is broken.
-Ciaran McNulty
___
microform
On Thu, Mar 20, 2008 at 3:05 PM, Andrew Jaswa <[EMAIL PROTECTED]> wrote:
> The hCard below doesn't get picked up by Operator:
>
>
>http://microformats.org/mailman/listinfo/microformats-discuss
On Mon, Mar 17, 2008 at 11:18 PM, Charles Iliya Krempeaux
<[EMAIL PROTECTED]> wrote:
> How many people do you think actually have wiki accounts?
As far as I know they're free to create, aren't they?
-Ciaran McNulty
___
microformats-d
have a 'lead' tag that's a synonym for
'leash'.
This is the reason that URL prefixes are included in the semantics of
tagging - different tagspaces will associate different meanings with
different tags, compound or otherwise. Aggregation where URLs are
discar
has been under a lot of scrutiny,
because of its inability to contain block elements.
hReview has more lenient defaulting rules, and I think there was some
mention in another thread of hAtom 0.2 fixing this.
-Ciaran McNulty
___
microformats-discuss mailing l
e with a missing AUTHOR
element in an Atom feed.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
aculous for the dialogues
> and the mofo parser on the serverside to fetch remote hCards.
Very impressive, Gordon!
One small comment: It doesn't appear to pick up my 'website' in the
case where there are multiple URL in one hCard. I believe your best
strategy would be to pick the
ith Opera Mini - though I have more
> confidence in the ability being added to the latter.
Lack of cut+paste is indeed an annoyance with the N95. The good news
is that it can handle most vCards or iCals correctly, if delieverd
over HTTP.
-Ciaran McNulty
___
On Dec 15, 2007 1:40 AM, Scott Reynen <[EMAIL PROTECTED]> wrote:
> It seems to me "3:23" is already
> machine-readable
Does 3:23 mean 3 mins 23 seconds, or 3 hours 23 mins, or 23 minutes
past three o'clock? ;-)
-Ciaran McNulty
_
o agree that ISO dates are often completely unreadable and we
should continue to explore alternatives, I've not seen on that makes
more sense than [EMAIL PROTECTED] yet as I am somewhat against the idea of
hiding it in title attributes on arbitrary elements.
-Ciaran McNulty
ot;
>
> There's no mention of using ; as a seperator in the XFN specs. I just
> wanted to check I wasn't missing anything.
XFN just mentions using multiple rel values for complex relationships,
and rel values are space-separate
n the context of your original page
*will* refer to 16:03 on a specific day (I'm finding it hard to think
of a non-contrived example where it wouldn't) - it's just abbreviated
to 16:03. A human would gather that information from context but it's
more exp
It sounds like a solid idea to me, but I'd really worry that it would
be unclear that we mean 'HTML and XHTML'. Is (X)HTML too unwieldy to
be the global replacement?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discus
does not appear in the exported event, in any of the
> several parsers I've tried.
>
> Is it my mark-up at fault, or is there some other problem?
Opening the Operator-exported .ICS in a text editor shows that the
DURATION field is missing, which suggests it's an Operator issue.
-Cia
On 9/20/07, Philip Tellis <[EMAIL PROTECTED]> wrote:
> well, what you do is, you blast all possible 8 bit sequences through
> usenet, and the ones that come out alive... that's your list.
Is this mailing list available on Usenet?
On 9/20/07, Andy Mabbett <[EMAIL PROTECTED]> wrote:
> Whatever character you have before that "f" isn't 7-bit Usenet
> compliant.
Is this list available on Usenet?
-Ciaran McNulty
___
microformats-discuss mailin
My public key id is http://pgpkeys.mit.edu:11371/pks/lookup?op=vindex&search=0x1F140E17";>1F14
0E17
Maybe with an appropriate @rel?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microf
ard child properties have to be on child HTML nodes.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
suspect it's the fact the lon/lat need a @class="geo" wrapper. that
would have to go on the TR meaning the vcard gets pushed up a level.
The lack of anything to wrap table columns in is quite a frustration.
-Ciaran McNulty
___
ossed with my reply to Ted - this isn't on
the faq page because it's an existing issue on the hresume-issues
page.
I've no objection to leaving off dtend as a solution but I think it
would need to be added to the hResume spec as a departure from iCal.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 8/29/07, Ciaran McNulty <[EMAIL PROTECTED]> wrote:
> Unfortunately vCard has a mechanism for generating default dtends when
> they are missing [1] - this is one of the issues on the hresume-issues
> page [2] that I'd really like to see resolved.
Apologies:
[1]
http://micr
Adding a *-intro page and a small island at the top of the existing
spec pages that says 'This is a specification, for a quick
introduction to * see *-intro' or something a bit more user-friendly.
-Ciaran McNulty
___
microformats-di
ec that an absent dtend in an hresume
event doesn't use this mechanism
2. Having some 'special' value that can be used for 'present'
Both would have negative impacts on hCal parsers that were trying to
consume the page and weren't 'hResume-aware'.
-Ciaran McNulty
__
he present' as a finish date for an
experience vevent.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
) level accuracy.
5Post code (zip code) level accuracy.
6Street level accuracy.
7Intersection level accuracy.
8Address level accuracy.
ref:
http://www.google.com/apis/maps/documentation/reference.html#GGeoAddressAccuracy
-Ciaran McNulty
__
problem with
other hCard subproperties being used inside a @class="adr".
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
CTED]" class="email">contact
But a close reading of the HTML spec would be required, and I doubt
any parsers would pick it up..
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
e USA)
I agree that i18n issues make this a bit too strict (I have similar
reservations about the implied-n optimisations but that's
tangential).
IMO it may be that the best option is to say that ADR can exist
without subproperties for hCard / solo-ADR
On 7/31/07, Andy Mabbett <[EMAIL PROTECTED]> wrote:
> Are there any examples of publishers or parsers using "agent" in hCard?
I don't think so, there was some discussion of it a while back on the
mailing list but you'd have to search t
xported to .vcf as
> "X-ASSISTANT".
That's interesting, as vCard allows an AGENT field that can contain a
complete other vCard. I don't know if any applications use it much.
-Ciaran McNulty
___
microformats-discuss mailing list
On 7/18/07, Brian Suda <[EMAIL PROTECTED]> wrote:
--- this is a known issue with Outlook.
http://microformats.org/wiki/vcard-implementations#TEL
I know, that's where I found out about it! :-)
-Ciaran McNulty
___
microformats-discuss m
and the consuming application default it to 'home',
but Outlook doesn't like vCard TEL without a TYPE, so most converting
apps will insert the default type explicitly.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
e
format too (date-of-death of course also fits into this usage).
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
I can't see this, but maybe I'm being stupid. Where on the page do
you see this?
I can see the geo tags, but only if I expand the 'machine tags'
section, which seems like a nice comprimise for machine-targetted /
human-targetted data.
-Ciaran McNulty
__
print stylesheet.
Well, to use it in any application that doesn't yet consume GEO (i.e.
sadly a lot of them) you'd want to be able to cut and paste it at the
minimum...
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@micro
ant to write it down, print it out, etc.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
rkup can be parsed unambiguously into a
DOM tree?
Most proxy-type services seem to run everything through Tidy anyhow.
I can't think of any uFs I'm aware of that wouldn't 'work' in HTML,
although some of the nesting features wouldn't work if people did (for
instance):
On 6/15/07, Pelle W <[EMAIL PROTECTED]> wrote:
Could such a microformat be designed like perhaps?
HTML already has
:-)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/m
such links.
In this case, I believe @rel="me" requires a symmetric link to be valid.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
ommendation for how to parse
HTML into text, it's a good place to start.
-Ciaran McNulty
* I'm thinking the exceptions are that that dates are ISO8601 and that
category names will be rel-tag and therefore RFC3986 encoded
[1] http://microformats.org/wiki/hcard
endar event
that essentially has old information in it?
One wouldn't, as far as I can see.
Certainly in my hResume, the hCards for each hEvent in the employment
history is the name and url of the company involved.
Regards,
-Ciaran McNulty
___
microformats
hereas anything 'hard coded' into the HTML spec
will not be optional.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
ractice in a lot of places, for similar
reasons.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
ever made up the term (Tantek?)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
to wrap arbitrary user-entered names in fn
and assume that parsers will work it all out.
One possible solution, which I've experimented with, is to use:
$user_entered_name
Then whatever the user has entered as their login becomes their full
name and nickname, and the other vCard fields
better idea than my one of a separate page per
uF, in that there's lower overhead in adding it to the existing pages,
and the fact it's visible on the page could prompt people to add
links, rather than it being tucked away.
-Ciaran McNulty
_
s. It would help to explain a lot of the thinking behind
'controversial' decisions like the datetime design pattern, rel-tags
url scheme and a few other things that seem to cause puzzlement.
-Ciaran McNulty
[1] http://microformats.org/wiki/datetime-design-pattern#How_to_use
GEO and ADR as stand-alone microformats outside of hCard came later,
which is why they're at a less advanced stage than hCard.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
How is this better than just:
Singapore
?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
tter insight than I.
I wasn't sure if I included an FN, isn't there a requirement for an N as well?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
ty. Commercial
properties are generally referred to by either the building name (i.e.
Microformats House) or the number/street (10 Microformats St.).
These are both usually also the first line of the address, do I just
have 1 Madeup
St. ?
Any guidance would be appreciated.
y:none"), I
don't see any value for the parentheses (or for the comma).
It's somewhat dangerous to assume elements set to be display:none will
never be seen...
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-dis
post-office-box" perhaps?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 2/2/07, Derrick Lyndon Pallas <[EMAIL PROTECTED]> wrote:
Except it does need it. Say you put your del.icio.us (or otherwise) feed
on your page and want to include it and the associated tags as xFolk
entries. How can a generic rel-tag parser know that the xFolk entires
don't apply to the curren
-tag parser doesn't need to know "don't look
inside hAtom and hCard", as you seem to be suggesting. Any rel-tags
it finds may be applied to the page itself quite fairly, and so a
rel-tag parser would say 'this page contains something relevant to FOO
and something relevant to B
l take from it is probably
correct.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
e as the 'me' of the current page?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
ntics for a number of languages, actually!
"The language tag always defines a language as spoken (or written) by
human beings for communication of information to other human beings.
Computer languages are explicitly excluded."
Ah, well spotted. Sh
On 1/30/07, Colin Barrett <[EMAIL PROTECTED]> wrote:
I have been posting some code listings on my blog recently. It would
be really nice to have these sections identified (so then a source
coloring tool could identify them and color them)
code
is the awful HTML I have been using. It would be ni
-name and Michael as the
family-name.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
2], i.e. an identifier for the place the data should
come from.
-Ciaran McNulty
[1] http://www.w3.org/TR/REC-html40/struct/objects.html#adef-data
[2] http://www.w3.org/TR/REC-html40/types.html#type-uri
___
microformats-discuss mailing list
microform
...
The spec explicitly mentions encoding in Unicode chars[2] so I don't
think there's any inherent limitation on which characters can be in a
tag.
In fact, I'd say that this should be something the tagging index
should be looking after (i.e. the uF is agnostic but
westmidlan
site stems from rel-tag being applied
to more generic 'categorisation' tasks in other uFs, where the user
might not have a tagging index set up. It's worth considering whether
the wording of the spec should be changed IMO.
-Ciaran McNulty
_
On 1/8/07, Andy Mabbett <[EMAIL PROTECTED]> wrote:
The @data should contain a URL, not data, the way you have here. A
parser would end up looking for an element with ID 'summaryA+ with...'
etc.,
Not sure about an elegant solution, I'm afraid, you may be better off
just repea
On 1/5/07, Andy Mabbett <[EMAIL PROTECTED]> wrote:
So the "workaround" at:
<http://microformats.org/wiki/advocacy#Google_as_rel-tag_namespace>
will not work?
Not in a fully conformant parser, no.
-Ciaran McNulty
__
re are also issues with multilingual sites that might want a
unified tagging scheme.
e.g. http://example.com/tags/fish"; rel="tag">poisson
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
Anyone care to shed some light on this for me?
The main reason that I can see is to allow normalisation of tags
across different pages. One might have http://en.wikipedia.org/wiki/Football_%28soccer%29";>Soccer
and the other http://en.wikipedia.org/wiki/Fo
On 1/1/07, Eran <[EMAIL PROTECTED]> wrote:
That last sentence pretty much leaves all interpretation of scope to the
application. In a blog the scope is usually a single post (even if several
posts appear on the same page), in hReview it is the product (or the rating
for the product) and in xFolk
On 1/1/07, Colin Barrett <[EMAIL PROTECTED]> wrote:
On Jan 1, 2007, at 7:29 AM, Ciaran McNulty wrote:
> Another @rel value that is more similar to the @rel="nsfw" would be
> @rel="no-follow", which is trying to express an opinion about the
> linked p
g is more like an hReview, but the
semantics don't correspond too well.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
to put all their efforts
into trying to obfuscate it to avoid getting more spam!
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
insane as that sounds in
this day and age)? :-)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 12/19/06, Ciaran McNulty <[EMAIL PROTECTED]> wrote:
Where you say "Why isn't it hCard? Apparently there are some
historical reasons for it, but I do not know the reasons." in slide 3,
the simple answer is that in vCard, the root property is VCARD, as in:
I should h
1 - 100 of 168 matches
Mail list logo
