hbib-discussion-2005-05-14: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Reverted edit of GjwSo2, changed back to last version by Tantek) |
||
Line 17: | Line 17: | ||
<h2>Authors</h2> | <h2>Authors</h2> | ||
<ul> | <ul> | ||
<li class="vcard"><a class="url fn" href="http://tantek.com/log/">Tantek</nowiki></pre> | <li class="vcard"><a class="url fn" href="http://tantek.com/log/">Tantek Çelik</a></li> | ||
<!-- numerical character entities work for XHTML and XML in general, | |||
whereas named character entities only work in HTML and *some* XHTML user agents --> | |||
<li class="vcard"><a class="url fn" href="#">Rohit Khare</a></li> | |||
<li class="vcard"><a class="url fn" href="http://meyerweb.com/">Eric A. Meyer</a></li> | |||
<li class="vcard"><a class="url fn" href="http://www.markbaker.ca">Mark Baker</a></li> | |||
<li class="vcard"><a class="url fn" href="http://www.wiredpen.com/">Kathy Gill</a></li> | |||
<li class="vcard fn">Bert Bos | |||
<li> ***** add your hcard here *****</li> | |||
<li>& other participants from the Microformats track on Dev Day at WWW 2005</li> | |||
</ul> | |||
<br> Solution? | |||
<br>Author -- should use hCard. OK | |||
<br>Mulitple authors? Multiple hCards. | |||
<br> use hidden SPANs? | |||
<br> use CSS classes for k-authors: 1st-author, 2nd-author? generic "author" class? | |||
<br> ol + span? | |||
<br> how to "loft" dc:author inot microformats use in CSS class= attrs? -- | |||
<em>create an XMDP for Dublin Core (creator, etc)</em> | |||
<pre> | |||
.author + .author + .author + .author {display: none} | |||
.author + .author + .author {content: " et al."} | |||
</pre> | |||
<h2> Existing Example</h2> | |||
<p>Let's start with a concrete example of a particular bibliography presentation | |||
</p> | |||
<pre> | |||
[1] Goland, Y. Y., Nottingham, M. and Orchard, D. WS-CallBack Protocol 0.91. | |||
BEA Systems, WS-CallBack Protocol 0.91, Feb 26 2003 2003. | |||
http://dev2dev.bea.com/technologies/webservices/WS-CallBack-0_9.jsp | |||
</pre> | |||
<p>How would we mark that up?</p> | |||
<pre class="example"> | |||
<span class="vcard"> | |||
<span class="fn n"> | |||
<span class="family-name "<Goland</span>, | |||
<abbr class="given-name" title="Yaron">Y.</abbr> | |||
</span> | |||
</span> | |||
</pre> | |||
<h2>Goals</h2> | |||
<ol> | |||
<li><strong>Stop having to re-key references!</strong></li> | |||
<li>Adapt to new Journal styles solely by changin the CSS?</li> | |||
</ol> | |||
<h2>Why a Microformat?</h2> | |||
<ol> | |||
<li><strong>Presentation matters!</strong></li> | |||
<li>A predecessor format exists: | |||
<ul> | |||
<li>BibTeX</li> | |||
<li>Endnote</li> | |||
<li>Dublin Core</li> | |||
</ul> | |||
</li> | |||
</ol> | |||
<hr> | |||
<strong>the microformats way</strong> | |||
<ul><li> | |||
solve a specific problem | |||
</li><li> | |||
make evolutionary improvements | |||
</li><li> | |||
be as simple as possible, perhaps solve a simpler problem first | |||
</li><li> | |||
adapt to current behaviors and usage patterns, e.g. (X)HTML, blogging | |||
</li><li> | |||
presentable <em>and</em> parsable | |||
</li><li> | |||
reuse existing microformats and well established schemas (e.g. IETF RFCs) as building blocks | |||
</li><li> | |||
design to be reused and embedded inside existing formats and microformats | |||
</li><li> | |||
enable and encourage decentralized development and services | |||
</li> </ul> | |||
<hr> | |||
<h2>The Microformats Checklist</h2> | |||
<dl> | |||
<dt>Specific Problem?</dt> | |||
<dd>Are we close? the library science rathole is pretty deep, folks....</dd> | |||
</dl> | |||
<h2>Notes</h2> | |||
<p>Typically have access to "rendered"/"flattened" papers without the structured data</p> | |||
</nowiki></pre> |
Revision as of 02:52, 6 July 2007
hBib Description 2005-05-14
This is a historical capture and therefore the below pre/nowiki contents MUST NOT be edited.
For current related efforts, see citation.
The following document was created, collaboratively edited live 2005-05-14 during the WWW2005 workshop and presentations on microformats.
<nowiki> <body style="font-size:130%"> <h1>hBib: une charette</h1> <p><em>an interactive design session</em></p> <h2>Authors</h2> <ul> <li class="vcard"><a class="url fn" href="http://tantek.com/log/">Tantek Çelik</a></li> <!-- numerical character entities work for XHTML and XML in general, whereas named character entities only work in HTML and *some* XHTML user agents --> <li class="vcard"><a class="url fn" href="#">Rohit Khare</a></li> <li class="vcard"><a class="url fn" href="http://meyerweb.com/">Eric A. Meyer</a></li> <li class="vcard"><a class="url fn" href="http://www.markbaker.ca">Mark Baker</a></li> <li class="vcard"><a class="url fn" href="http://www.wiredpen.com/">Kathy Gill</a></li> <li class="vcard fn">Bert Bos <li> ***** add your hcard here *****</li> <li>& other participants from the Microformats track on Dev Day at WWW 2005</li> </ul> <br> Solution? <br>Author -- should use hCard. OK <br>Mulitple authors? Multiple hCards. <br> use hidden SPANs? <br> use CSS classes for k-authors: 1st-author, 2nd-author? generic "author" class? <br> ol + span? <br> how to "loft" dc:author inot microformats use in CSS class= attrs? -- <em>create an XMDP for Dublin Core (creator, etc)</em> <pre> .author + .author + .author + .author {display: none} .author + .author + .author {content: " et al."}
Existing Example
Let's start with a concrete example of a particular bibliography presentation
[1] Goland, Y. Y., Nottingham, M. and Orchard, D. WS-CallBack Protocol 0.91. BEA Systems, WS-CallBack Protocol 0.91, Feb 26 2003 2003. http://dev2dev.bea.com/technologies/webservices/WS-CallBack-0_9.jsp
How would we mark that up?
<span class="vcard"> <span class="fn n"> <span class="family-name "<Goland</span>, <abbr class="given-name" title="Yaron">Y.</abbr> </span> </span>
Goals
- Stop having to re-key references!
- Adapt to new Journal styles solely by changin the CSS?
Why a Microformat?
- Presentation matters!
- A predecessor format exists:
- BibTeX
- Endnote
- Dublin Core
the microformats way
- solve a specific problem
- make evolutionary improvements
- be as simple as possible, perhaps solve a simpler problem first
- adapt to current behaviors and usage patterns, e.g. (X)HTML, blogging
- presentable and parsable
- reuse existing microformats and well established schemas (e.g. IETF RFCs) as building blocks
- design to be reused and embedded inside existing formats and microformats
- enable and encourage decentralized development and services
The Microformats Checklist
- Specific Problem?
- Are we close? the library science rathole is pretty deep, folks....
Notes
Typically have access to "rendered"/"flattened" papers without the structured data
</nowiki>