#microformats 2013-09-27

2013-09-27 UTC
tantek, singpolyma and DanC joined the channel
singpolyma joined the channel
#
DanC
"how to markup citations in an article on the web that refers to other articles on the web" er... a/@href solves that problem, no?
#
DanC
I'd think the purpose of a citation is to provide redundancy when the normal sub-second dns/http links aren't doing so hot.
#
DanC
and to allow for citations in one style to be reformatted in another
#
DanC
and to indicate endorsement. "this paper was accepted at conference X" or "journal Y".
#
DanC
those would need to be refined
#
DanC
they're not problem statements as such.
#
DanC
the specific problem that brings me here today is: I have a mix of traditional academic literature and misc. web pages that I want to cite from a grant proposal
#
DanC
I'm not the primary author of the grant proposal.
#
DanC
Zotero does great with MS Word integration and such, once you get the citations in there...
#
DanC
but its browser plugins are kinda picky about what they'll grab and add to the Zotero DB
#
DanC
whereas diigo will let me capture anything, down to a free-text note that isn't even on the web yet...
#
DanC
... but in diigo, even when the web page I'm bookmarking is part of the traditional academic literature, the tool doesn't know how to pick out the author, title, conference/journal, etc. for formatting as MLA etc.
#
DanC
my previous problem in this area was: a consulting client asked for a bibliography of all my publications in the last 10 years
singpolyma joined the channel
#
DanC
Zotero was nearly perfect for that one.
#
DanC
Zotero has both a web UI and a windows/mac/linux desktop UI. I wonder how they develop the latter. Its UI is richer.
#
DanC
these days, with GWT and such, it's pretty straightforward to get parity.
#
DanC
e.g. RStudio and RStudio server
#
DanC
seems to be drafting a blog article
#
DanC
presumes nobody minds, since nobody else is saying anything
#
DanC
fwiw, result of said 10 yr bibliography exercise: https://www.zotero.org/connolly/cv
#
DanC
oh: another goal: structure-preserving copy-and-paste of citations (and lists of citations)
#
DanC
e.g. from Zotero to my linkedin profile
#
DanC
one dirt simple design: Zotero adds to its list of many formatting options a simple tab-separated-values format.
#
tantek
scrolls up to DanC chatting to the ether
#
DanC
then I copy-and-paste that to linked, which has some level of agreement with Zotero on column names
#
DanC
linkedin
#
tantek
DanC - you're looking for this: http://microformats.org/wiki/h-cite
#
DanC
well, I found that. that's where the "how to markup citations in an article on the web..." quote comes from
#
tantek
ah great - let me see if I can add an FAQ for your rhetorical question :)
#
DanC
updates to traditional citation guides (MLA, Chicago, ...) all seem to recommend citing web pages by when you accessed them. seems to me the normal rss/atom published/revised dates are much more relevant
#
DanC
we don't cite books by when we read them
#
DanC
interesting what has evolved in the wikipedia community. https://en.wikipedia.org/wiki/Wikipedia:Citation_templates . lots of how and very little why
#
tantek
edited /h-cite (+886) "add FAQ with question from DanC"
(view diff)
#
tantek
DanC the problem with rss/atom published/revised dates for citations is that they're simply self-asserted by the publisher
#
DanC
same with books and such
#
tantek
books are different because a. they don't change once printed and b. there are many copies
#
DanC
in both cases, you can, with various degrees of confidence, confirm from other sources the date of last revision
#
tantek
yes, in both cases (web articles and books) the published date is reported as self-asserted by the publisher
#
tantek
and it's not just wikipedia that has adopted "date accessed"
#
tantek
other citation guidelines recommend it as well
#
tantek
so we are simply paving the footpaths here
#
DanC
I know. much to my bewilderment
#
DanC
I don't really see how marking up name/date/etc. contributes to solving the problem as stated. hmm.
#
DanC
nor is it clear that "see also" links are disjoint with citations
#
tantek
rather it's not clear that "see also" links ever mean "citation"
#
tantek
the burden of proof is to assert that they are
#
DanC
maybe I just don't understand the problem statement. Can you give me a more concrete instantiation of it? Or a community who often comes across it?
#
tantek
in the simplest form, marking up name/date etc. allow for processing of web citations into whatever "style" or "format" the user wishes to publish them (MLA vs APA etc.)
#
DanC
ah. ok. I agree that capturing this semantic so it can be formatted different ways is a problem worth solving.
#
DanC
formatted, queried, sorted, organized, etc.
#
tantek
that's a worthy faq
#
DanC
seems to me it's a better problem statement. But I haven't finished swapping in all the recent work.
#
DanC
really should head out. hmm.
#
tantek
edited /h-cite (+294) "/* FAQ */ add Why"
(view diff)
#
DanC
I'm about this close >< to opening up emacs to start coding on a tool to go from Zotero to diigo or the other way, using h-cite in the middle.
#
tantek
indeed - I think tommorris has been discussing doing something similar
#
tantek
using h-cite as an intermediary format
#
tantek
whichever piece you end up building, it is likely useful
#
tantek
either producing h-cite form some other format
#
tantek
or consuming h-cite and producing whatever output you wish for your own purposes
#
DanC
wierd... how do i get from the revision Loqui cited a minute ago to the un-versioned page?
#
tantek
click History and then click Page :)
#
DanC
hopes you're not proud of that
#
DanC
er... now the page has 2 problem statements. One under #Why and one under Focus
#
DanC
I'd be happy if the one under Focus went away. Or if the page explictly said how they relate. As is, it looks like a merge conflict gone bad ;-)
#
tantek
Focus is more of a scoping than a problem statement
#
DanC
"solve the specific problem of" sure looks like a problem statement
#
DanC
heads out, hoping to return to the topic before too long
#
DanC
nice chatting with you, tantek
#
tantek
yes the FAQ should come before that
#
tantek
edited /h-cite (+1) "put FAQ before Design Principles / History"
(view diff)
#
tantek
DanC - when you're looking at parsing h-cite to generate something else, check out the microformats2 open source parsers: http://microformats.org/wiki/parsers#microformats2_parsers
#
tantek
in particular php-mf2 is quite good, well tested, good test suite etc. https://github.com/indieweb/php-mf2
singpolyma, tantek, eschnou, gjones, romainneutron, tobyink, danielfilho and barnabywalters joined the channel
#
Loqi
barnabywalters: tantek left you a message 12 hours, 55 minutes ago: not sure what you mean. right place for what? what research? context? (re: your link to accessibility-examples)
gjones, pfefferle, ChiefRA, romainneutron, tobyink, guesshimself, TallTed, singpolyma, jgay, gavinc, pfefferle_, jschweinsberg, tantek, eschnou, adactio, chiui, barnabywalters, singpoly1a and shaners joined the channel