On 7/11/06, Lee Amosslee [EMAIL PROTECTED] wrote:
So, if I apply rel-tag, am I saying that this is an important link?
Am I missing something?
A little, I saw a couple of earlier replies but thought there were
some bits I could clarify.
With markup like:
pTags: a rel=tag
On 7/13/06, Sho Kuwamoto [EMAIL PROTECTED] wrote:
Exactly my point. There are two competing schema living in the same
document: the world of HTML (semantically poor and unextensible), and
the world of microformats. While this works out OK usually, I believe
there are cases where the two worlds
On 7/18/06, Charles Iliya Krempeaux [EMAIL PROTECTED] wrote:
Maybe something like...
Pay me abbr class=currency title=CAD$/abbr5.00 now!
Something along these lines would be pretty sensible IMO
Some other things to consider... there might be an implicit currency
that comes with what's
On 7/18/06, Mike Stickel [EMAIL PROTECTED] wrote:
Since there can be a difference between different languages within
countries I thought it might be a good idea to include that in the
currency definition of the formating, eg., CAD eng or CAD fr.
If you need to specify the language, for
On 7/18/06, Ciaran McNulty [EMAIL PROTECTED] wrote:
Or, a more complex example with multiple languages:
[...]
Sorry, screwed this up a bit. I meant to demonstrate different number
formatting.
p lang=en
Price:
span class=money
abbr class=currency title=GBPpound;/abbr
span class
On 7/18/06, Scott Reynen [EMAIL PROTECTED] wrote:
It already is pretty neat:
http://viewmycurrency.wordpress.com/about/
http://nybblelabs.org.uk/projects/exchequer
http://6v8.gamboni.org/Greasemonkey-Yahoo-Finance.html
Which prompts the question: what exactly is the problem we're trying
to
microformats the tag may refer to a
smaller portion on the page but the prescence of this smaller portion
but by implcation can also apply to the page as a whole.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
Someone said that the citation uformat should use hcards for authors; this is
probably an ideal situation, but not necessarily practical in all cases - for
instance, I'm slurping author data from Amazon and don't have control of how
it segments into first, middle, last names, etc.
You don't
On 8/3/06, Andrew Sidwell [EMAIL PROTECTED] wrote:
Could one use cite class=vcard fnBen Barren/cite instead? That
would fit HTML semantics more closely.
The fn has to be inside the vcard, but
cite class=vcardspan class=fnBen Barren/span/cite would be ok.
-Ciaran McNulty
I did think about using the agent field --- unfortunately, in this
instance John Smith is (in real life) an agent and John Doe is the
agent's assistant. I have a feeling that using the agent's agent
field for the agent's assistant's hcard or the associate agent's
hcard is just going to cause
On 8/29/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
I am assuming 'A' is an abberiviation for a first name? 'B' is a
middle name, and 'Smith' is the last name you can do the following:
On 8/28/06, Brian Suda [EMAIL PROTECTED] wrote:
Yeah, but I don't think you can asssume that. Better to
On 8/31/06, Jeremy Keith [EMAIL PROTECTED] wrote:
I was working an intranet site for a posh estate agent recently, and
they had all sorts of ludicrous edge cases in their database of upper-
class landed gentry.
I work for a site that deals in the Construction industry, and for
whatever reason,
the literal content for parsing, hAtom
only specifies this for dates?
What is the reasoning behind this?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats
Lets say you have a personal registration form in your web app, for
entering contact data which will later be output as an hCard in
various places.
What if I was to mark up the form (and fields) with hCard classes?
I've long thought that a form should be marked up as if the data was
On 10/1/06, Scott Reynen [EMAIL PROTECTED] wrote:
I think $ is a unit of measuring currency, and barrel is a unit
of measuring oil, which in this case is the product the currency
references.
I disagree. There are plenty of other things that can be sold by the
barrel, and I doubt there are
pointers to the existing research?
Thanks
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
a
'smart pasting' implementation to figure out where to place data
(although some guidance e.g. recommending that the field-identifying
classes are applied directly to the INPUT might turn out to be
necessary).
Regards,
-Ciaran McNulty
___
microformats
than new one.
Semantics of an input form and the eventual display format are the same.
Drawbacks:
Existing parsers would/could parse forms as invalid hCards,
would need re-writing.
Regards,
Ciaran McNulty
___
microformats-discuss mailing list
, surely.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
think it'd be a good idea to update / add to
the examples to cover this case - I'd be happy to do so myself once I
know what the correct answer is.
Cheers,
-Ciaran McNulty
[1] http://microformats.org/wiki/include-pattern
[2] http://microformats.org/wiki/include-pattern#class_name_.22include.22
think ISO8061 has a way of representing 'now' -
the only thing I could suggest would be that you set it equal to the
document's publication date, maybe using PHP as you suggest.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss
be appropriate,
http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
to be
everything inside the 'money' that isn't the 'currency'.
i.e. span class=moneyabbr class=currency
title=USD$/abbr5.99/span would be equivalent to your example
above.
That would simplify the markup in a large number of the cases, and I
don't think would complicate the parsing *too* much.
-Ciaran
in. This would then hopefully also cover more complex cases like
figures written in Japanese etc.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
readers and so on.
-Ciaran McNulty
[1] http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt
[2] http://ftp.ics.uci.edu/pub/ietf/http/related/iso3166.txt
[3] http://www.w3.org/International/O-HTML-tags.html
___
microformats-discuss mailing list
a
per-page language setting.
The @lang doesn't have to be on the HTML element really. As long as
it's on *an* element that contains your content, a user-agent should
know what's going on.
-Ciaran McNulty
___
microformats-discuss mailing list
a page locally, or is
viewing it through a cache such as Google's, it'd be a mistake to
infer the URL as C:\Temp\whatever, for instance.
These are edge cases, but worth thinking about.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats
that meant we had to turn off output
compression on a largeish site.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
For the specific example you mention, the '2 hours' declaration could
probably be used as the DURATION (probably with an ABBR) and then
transcluded into each VEVENT using the include-pattern.
-Ciaran McNulty
___
microformats-discuss mailing list
explanatory, or at least appear to be to him.
Authoring practices are the current practices and conventions used
by people authoring content.
The structure of the markup is the syntactic structure of pages
marked up with (X)HTML.
-Ciaran McNulty
___
microformats
not really another option, sure.
-Ciaran McNulty
* It's very easy to volunteer other people's time like this, I appreciate ;-)
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats
be.
The microformats list and/or IRC channel are, I've found, a great
place to discuss semantic XHTML in general. I'd encourage you to
publish your data using whatever sensible scheme you deem appropriate,
maybe after some discussion here and elsewhere.
-Ciaran McNulty
[1] http://microformats.org/wiki
=bookmark is scoped to the current page, I think. It can be
applied to an A or a LINK.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
], so you can add any other identifiers onto it.
However, hCard does already distinguish between organisations and
individuals [2] (who can then be members of an organisation), so the
extra markup may not be worth it.
-Ciaran McNulty
[1] http://microformats.org/wiki/hcard-parsing
/projects/netlib/Link_Prefetching_FAQ.html
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
be normalised to a single
space when rendered.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
that makes rel=vote-for mean This url is a vote for the
current page. It could be used, for instance, to link to people who
are adding their names to a petition?
I don't think it can be taken to mean 'This is a place where you can
vote for the current page', which seems to be your intent.
-Ciaran
Rather than hiding data using CSS, would it be valid to do something
like the following?
abbr title=cell class=typeOffice/abbr
I think that would parse correctly, but the usage of the ABBR is very
semantically dodgy.
-Ciaran McNulty
___
microformats
On 11/14/06, Ciaran McNulty [EMAIL PROTECTED] wrote:
abbr title=cell class=typeOffice/abbr
Sorry, abbr title=cell class=typeMobile/abbr makes more sense.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
for the current
page, which I doubt is correct.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
, then the entry author will default
to the nearest in-parent [EMAIL PROTECTED]author
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
of this, so I'd be delighted to find I'd read it wrong!
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 12/13/06, Siegfried Gipp [EMAIL PROTECTED] wrote:
address is an element designed to contain contact information. So if you
want to include contact information use address. That is indepenent of
using hCard or not. address is a html element, specified by the w3c, hCard
is an attribute
On 12/13/06, Tim White [EMAIL PROTECTED] wrote:
I believe that the (%inline) refers to what address can contain -- inline
elements. See same structure for headings:
http://www.w3.org/TR/html4/struct/global.html#h-7.5.5
Aha, that sounds probable (apologies to Siegfried).
The fact it can't
On 12/13/06, Steve Marshall [EMAIL PROTECTED] wrote:
This, to my mind, is sub-optimal: the version of the format in use
isn't something most (if any) users care about and, ideally, shouldn't
be required to be part of the content.
For Microformats that have an XMDP profile this is at least in
On 12/13/06, Chris Messina [EMAIL PROTECTED] wrote:
If it's not been done already, could this be added to the wiki under
versioning practices?
There's a bit about it here:
http://microformats.org/wiki/profile-uris
But it doesn't seem to be a resolved issue yet.
-Ciaran McNulty
On 12/14/06, Mike Schinkel [EMAIL PROTECTED] wrote:
Just curious, what did you mean by double entendre markup?
It means 'double meaning'.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
Scott was just making a bit of wordplay.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
:
http://microformats.org/wiki/rel-tag#Tags_Are_Visible_Metadata
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 12/16/06, Alex Faaborg [EMAIL PROTECTED] wrote:
Today Mozilla Labs released a microformat extension for Firefox 2
named Operator. The extension was developed by Michael Kaply at IBM,
and detects hCard, hCalendar, geo, hReview and rel-tag.
Alex,
This is absolutely excellent,
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 have added 'so because hCard
in
this day and age)? :-)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
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
.
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 page rather than describing the link relationship.
My own opinion is that a rating is more like an hReview, but the
semantics don't correspond too well.
-Ciaran
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 page rather than describing the link relationship
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
?
The main reason that I can see is to allow normalisation of tags
across different pages. One might have a
href=http://en.wikipedia.org/wiki/Football_%28soccer%29;Soccer/a
and the other a
href=http://en.wikipedia.org/wiki/Football_%28soccer%29;Football/a,
for instance.
-Ciaran McNulty
is on an image...
There are also issues with multilingual sites that might want a
unified tagging scheme.
e.g. a href=http://example.com/tags/fish; rel=tagpoisson/a
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
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
___
microformats-discuss mailing
On 1/8/07, Andy Mabbett [EMAIL PROTECTED] wrote:
object data=#summaryA+ with +#summaryC class=include
/object
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
-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
___
microformats-discuss mailing list
. 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
microformats-discuss
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)
precode
code
/code/pre
is the awful HTML I have been using.
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. Shame!
-Ciaran McNulty
.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
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 BAR.
Does that make sense?
-Ciaran McNulty
___
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 current
/spanbr /
span class=country-nameNew Zealand/span
/p
I would think that the name of the recipients is the FN, not part of
the address.
Are Rural Delivery numbers similar enough to post-office-box perhaps?
-Ciaran McNulty
___
microformats-discuss mailing
)
/span
Since this information is not being displayed (style=display: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
be appreciated.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
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
=display:none
(span class=country-nameSingapore/span)
/span
How is this better than just:
span class=adrspan class=country-nameSingapore/span/span
?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
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
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
___
microformats-discuss mailing list
are effectively blank.
Actually span class=fn$foo/span where $foo is one word already
has this optimisation [2]
-Ciaran McNulty
[1] http://microformats.org/wiki/hcard#Implied_.22n.22_Optimization
[2] http://microformats.org/wiki/hcard#Implied_.22nickname.22_Optimization
the term (Tantek?)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
I concur, an HTML parser should be allowed to ignore comments, and many will.
The similar decision to 'hide' Javascript and other scripting
languages inside HTML comments has been widely criticised and is no
longer considered best practice in a lot of places, for similar
reasons.
-Ciaran
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
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-discuss mailing list
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-parsing
#Plain_Text_Formatting_of_Structural.2FSemantic_HTML
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
On 6/15/07, Pelle W [EMAIL PROTECTED] wrote:
Could such a microformat be designed like a href=foobar.com/foo/bar/
rev=application/pdf perhaps?
HTML already has a href=foo type=application/pdf /
:-)
-Ciaran McNulty
___
microformats-discuss mailing
/em/p
(which I think is valid HTML)
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
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@microformats.org
http
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
___
microformats-discuss
of course also fits into this usage).
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
apps will insert the default type explicitly.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
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 mailing list
any parsers would pick it up..
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
being used inside a @class=adr.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
for an
experience vevent.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
. 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
___
microformats-discuss mailing list
microformats-discuss
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-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org
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://microformats.org/discuss/mail
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
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
___
microformats-discuss mailing
to be on child HTML nodes.
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
is object class=key type=whatever_PGP_keys are
data=http://pgpkeys.mit.edu:11371/pks/lookup?op=vindexamp;search=0x1F140E17;1F14
0E17/object
Maybe with an appropriate @rel?
-Ciaran McNulty
___
microformats-discuss mailing list
microformats-discuss
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 mailing list
microformats-discuss@microformats.org
1 - 100 of 141 matches
Mail list logo
