On Thu, 30 Mar 2006 16:43:49 +0200, Scott Reynen [EMAIL PROTECTED]
wrote:
citePhoto span class=titleSiesta Lake/span by span class=fn
photographyAnsel Adams/span./cite
The Photo there isn't machine-readable. I think it should be made it
machine-readable with span class=mediaphoto/span or
On 3/30/06, Tim White [EMAIL PROTECTED] wrote:
2) Adapted to current behaviors and usage patterns.
Microformats are suppose to be modeled on what people are currently
doing (80/20) on the web. I think of it in terms of the Everyman/woman.
Capturing metadata isn't what is happening by the 80.
--- Scott Reynen [EMAIL PROTECTED] wrote:
On Mar 30, 2006, at 7:48 AM, Tim White wrote:
The Photo there isn't machine-readable. I think it should be made
it machine-readable with span class=mediaphoto/span or span
class=citation photo -- I'm ambivalent about which is best between
On 3/30/06, Tim White [EMAIL PROTECTED] wrote:
[... snip ...]
In short, I'd like to be able to talk about a book on my blog:
I am reading cite class=hcitation titleOperating Manual for
Spaceship Earth/cite ...
AND, be able to cite it at the end of a longer piece:
cite class=hcitation
On 3/30/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
On 3/30/06, Tim White [EMAIL PROTECTED] wrote:
Although, to clarify, your distinction above is really between an
in-text citation, and a full bibliographic reference.
Um... I just see it as a note pointing to a citation and the citation
On 3/28/06, Ross Singer [EMAIL PROTECTED] wrote:
On 3/28/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
I have to disagree on the usefulness of the OpenURL stuff in this context.
Can you explain this? w/r/t HTML, I find OpenURL the /most/ useful in this
context, with this context being web
On Mar 29, 2006, at 9:36 AM, Alf Eaton wrote:
span class=editors
span class=editorJohn Green/span and
span class=editorSimon Brown/span (Eds);
/span
I guess there are some things in
On Mar 29, 2006, at 12:29 PM, Michael McCracken wrote:
In my opinion, converting losslessly is not the aim. Given a
microformatted citation, I should be able to take one more step and
find enough information to populate a full format, but I don't think
embedding a full bibliograhpic record at a
True, but a mechanism for this sort of thing already exists for
microformats in XMDP, and in a somewhat more flexiible form, in that
one does not need a monolithic profile for all the modules involved,
one can have a seperate profile for each module and link to each
seperately.
The basic
OK, so a minimal microformat for a citation could look like this:
x class=citation [type]
x class=titleItem title/x
x class=creatorshcards/x
x class=container citation [type]hcitation for the container/x
x class=pagesn-n/x [and anything else specific to this
particular
Yeah, this is getting very similar, and I certainly don't have any
huge problems with the differences between our versions. A couple
questions:
- I'm still not convinced about [type] as a class, although it'd be
useful to have that data in there somewhere, it seems like it has the
potential to
On 3/29/06, Alf Eaton [EMAIL PROTECTED] wrote:
On 29 Mar 2006, at 14:34, Michael McCracken wrote: span class=author vcard a class=fnLorin Hochstein/a /spanThat's an interesting problem, because what happens if the authors
names are in the format Surname, Initials. Do you have to use
I just looked over the hcard spec again. 'fn' is formatted name, and
it implies another element 'n', which is required by the vCard spec.
In the XMDP profile for hCard, they refer us to this section of the
vCard RFC:
3.1.2 N Type Definition
To: [EMAIL PROTECTED]
Subject: Registration of
Alf Eaton wrote:
On 29 Mar 2006, at 14:34, Michael McCracken wrote:
span class=author vcard
a class=fnLorin Hochstein/a
/span
That's an interesting problem, because what happens if the authors
names are in the format Surname, Initials. Do you have to use an
abbreviation?
span
On Mar 29, 2006, at 1:44 PM, brian suda wrote:
Another thing that really helped some hCalendar discussion was to plan
an IRC meet-up, We all selected a time when we could meet online and
knocked-out several of issues at once. Would folks be up for that?
if so
i can get a sort of agenda
Well, this is a lot to process at the end of the day. Here's just a few
of my initial thoughts.
First, and I've asked this before, what are we trying to do? For me, I
just want a *simple* way to mark up books, be it a title, title
author, or slightly more.
We are NOT replacing OpenURL, etc.
We
On 3/28/06, Michael McCracken [EMAIL PROTECTED] wrote:
Hi, so since we've got a large number of examples on the examples
page, I think it's time to float an initial version of a citation
microformat.
I think this is a good start. I'd vote for volume and issue number
being separately
On 3/28/06, C. Hudley [EMAIL PROTECTED] wrote:
But, the helpful part of the distinction is that when you're examining
a reference external to the content at hand, you don't need the full
bibliographic details. This immediately lets you eliminate stuff like
subjects/keywords, pricing,
On 3/28/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
I have to disagree on the usefulness of the OpenURL stuff in this context.Can you explain this? w/r/t HTML, I find OpenURL the /most/ useful in this context, with this context being web content and OpenURL being a means to link a citation to an
19 matches
Mail list logo
