Microformats Wiki - User contributions [en]

haudio-brainstorming

2011-07-31T03:02:55Z

HughP: /* Contributor Roles */

<h1>hAudio Brainstorming</h1>

== Inheritance of Properties ==

Suggest that the following section in the spec:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

</blockquote>

Be replaced with:

<div style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

It is important to understand that ITEM is an opaque element. When processing the ITEM element, the properties of the child hAudio should not be pulled into the parent hAudio, nor vice versa, with the following exceptions.
* It is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo
* The parent hAudio {{may}} inherit the following properties from its children:
** sample (Note that sample is plural, so it is OK for the parent to inherit this property from multiple children)

</div>

* Suggested by [[User:TobyInk|TobyInk]]

== Download links ==

Suggested we change this:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">
The type of the file {{may}} be specified by using the type specifier for a URI.
</blockquote>

To:

<blockquote style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">
The type of the file {{should}} be specified by using the type specifier for a URI.
</blockquote>

All examples in the spec should be updated to include the type attribute, and an informative section in the spec should list commonly used types.

* Suggested by [[User:TobyInk|TobyInk]]

== Contributor Roles ==
Is there a list of Roles somewhere that we can use to "limit" the types of contributors? This list need not be germain to just audio genres, it could be inclusive of print media and video or photo media. I work with OLAC [http://www.language-archives.org] and we have a set of contributors which we pull from an RDF set somewhere. Could something simular be done here?

* Suggested by [[User:HughP|HughP]]

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

haudio-brainstorming

2011-07-31T03:01:52Z

HughP: /* Contributor Roles */ Fixed a link

<h1>hAudio Brainstorming</h1>

== Inheritance of Properties ==

Suggest that the following section in the spec:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

</blockquote>

Be replaced with:

<div style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

It is important to understand that ITEM is an opaque element. When processing the ITEM element, the properties of the child hAudio should not be pulled into the parent hAudio, nor vice versa, with the following exceptions.
* It is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo
* The parent hAudio {{may}} inherit the following properties from its children:
** sample (Note that sample is plural, so it is OK for the parent to inherit this property from multiple children)

</div>

* Suggested by [[User:TobyInk|TobyInk]]

== Download links ==

Suggested we change this:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">
The type of the file {{may}} be specified by using the type specifier for a URI.
</blockquote>

To:

<blockquote style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">
The type of the file {{should}} be specified by using the type specifier for a URI.
</blockquote>

All examples in the spec should be updated to include the type attribute, and an informative section in the spec should list commonly used types.

* Suggested by [[User:TobyInk|TobyInk]]

== Contributor Roles ==
Is there a list of Roles somewhere that we can use to "limit" the types of contributors? This list need not be germain to just audio genres, it could be inclusive of print media and video or photo media. I work with OLAC [http://www.language-archives.org|OLAC] and we have a set of contributors which we pull from an RDF set somewhere. Could something simular be done here?

* Suggested by [[User:HughP|HughP]]

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

haudio-brainstorming

2011-07-31T02:58:43Z

HughP: Added the section on Contributor Roles

<h1>hAudio Brainstorming</h1>

== Inheritance of Properties ==

Suggest that the following section in the spec:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

* It is important to understand that ITEM is an opaque element. When processing the ITEM element, none of the properties of the child hAudio should be pulled into the parent hAudio. However, it is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo

</blockquote>

Be replaced with:

<div style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">

'''Parser Processing Notes'''

It is important to understand that ITEM is an opaque element. When processing the ITEM element, the properties of the child hAudio should not be pulled into the parent hAudio, nor vice versa, with the following exceptions.
* It is recommended that child hAudio {{should}} inherit the following parent hAudio properties, if they are not specified on the child:
** album
** contributor
** category
** published
** photo
* The parent hAudio {{may}} inherit the following properties from its children:
** sample (Note that sample is plural, so it is OK for the parent to inherit this property from multiple children)

</div>

* Suggested by [[User:TobyInk|TobyInk]]

== Download links ==

Suggested we change this:

<blockquote style="border:2px solid #fcc;background:#fee;margin:1em;padding:0.33em">
The type of the file {{may}} be specified by using the type specifier for a URI.
</blockquote>

To:

<blockquote style="border:2px solid #cfc;background:#efe;margin:1em;padding:0.33em">
The type of the file {{should}} be specified by using the type specifier for a URI.
</blockquote>

All examples in the spec should be updated to include the type attribute, and an informative section in the spec should list commonly used types.

* Suggested by [[User:TobyInk|TobyInk]]

== Contributor Roles ==
Is there a list of Roles somewhere that we can use to "limit" the types of contributors? This list need not be germain to just audio genres, it could be inclusive of print media and video or photo media. I work with [OLAC|http://www.language-archives.org/] and we have a set of contributors which we pull from an RDF set somewhere. Could something simular be done here?

* Suggested by [[User:HughP|HughP]]

== Related Pages ==
{{haudio-related-pages}}
* [[audio]] (other pages about Audio on this wiki)

hresume

2011-07-30T19:12:11Z

HughP: The hresumecreator at http://hresume.weblogswork.com/hresumecreator/ has not resolved properly for 2 years. I have tried to contact the webmaster to no avail. There is how ever another hresumecreator

<entry-title>hResume</entry-title>
{{DraftSpecification}}
__TOC__
hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an hResume? Use the [http://recherche.telecom-bretagne.eu/labo_communicant/dev_labc/hResumeCreator.php hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog.

==Microformats Draft Specification==

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

{{rfc-2119-intro}}

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. {{must}} use [[hcard|hCard]]; {{should}} use <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hResume schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info in an [[hCard]]; {{should}} use <code class="element"><address></code> with [[hCard]] when possible.
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code class="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''publications''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== XMDP Profile ===
* [[hresume-profile]] (@TODO)

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<source lang=html4strict>

I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...

</source>

=== Contact ===
<source lang=html4strict>
<address class="vcard">
Pedro Sanchez

123 Fake St.
Preston, Idaho 83263

Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a>
Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a>
Phone: +01.208.555.4567
</address>
</source>

=== Education ===
<source lang=html4strict>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</source>

=== Experience ===
==== Basic ====
A basic experience event:

<source lang=html4strict>
<ol class="vcalendar">
<li class="experience vevent">
President,
Preston High School,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</source>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use one or more [[hcard|hCard]]s. hCard requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't customary to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

Currently, the recommended way to reference includes within microformats is to use a hyperlink with class="include". See [[include-pattern|include-pattern]] for details.

For example, this hCard refers to another hCard:

Using <code><a></code>:
<pre>

<a href="#pedro-name" class="include" title="Pedro Sanchez"></a>
Preston High School
Class President

</pre>

Using <code><object></code>:
<pre>

<object data="#pedro-name" class="include"></object>
Preston High School
Class President

</pre>

Where "<code class="attr-value">pedro-name</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):

<source lang=html4strict>
<address class="vcard">

Pedro
Sanchez

</address>
</source>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.

Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.

=== Skills ===
Some sample skills tags:
<source lang=html4strict>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</source>

=== Affiliations ===
<source lang=html4strict>
National Honor Society
</source>

=== Publications ===
<source lang=html4strict>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</source>

== Examples in the wild ==
See [[hresume-examples-in-wild]]

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse hResumes. If you have an hResume implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page like [[hresume-implementations]].

* [http://ben.balter.com/2010/09/12/wordpress-resume-plugin/ WP Resume] is an out-of-the-box solution to publish your resume on your WordPress site and outputs the resume in an hResume compatible template.

* [http://www.cvmatch4jobs.com/ cvmatch4jobs] has implemented hResume import for publicly published CV's. A Career site for 3 UK building and proprety magazines from publishers UBM. 19 Jan 2010.

* [http://careercv.mad.co.uk/ CareerCV] has implemented hResume import for publicly published CV's. A Career site for major UK design magazines from publishers Centaur Communications. 19 Jan 2010.

* [http://lab.madgex.com/hresume/ Madgex] has implemented hResume to Microsoft Word and PDF conversion API. 13 Dec 2009.

* [http://careers.stackoverflow.com/ Stack Overflow] generates hResume for its public CV hosting service for programmers. [http://careers.stackoverflow.com/klmr Stack Overflow CV example] Dec 2009.

* [http://jobs.guardian.co.uk/profile/ Guardian Jobs] has implemented hResume import for publicly published CV's. 4 Sep 2009.

* [http://www.yiid.com/ YIID - Your Internet Identity] supports importing of hResumes (e.g. here is the result of an import: http://pfefferle.yiid.com/cv [requires login] via @pfefferle)

* [[Resume.app]]

* [http://www.xing.com/ Xing] generates hResume for all Public Profiles. [http://www.xing.com/profile/Matthias_Pfefferle Xing Public Profile Example].

* [http://linkedin.com LinkedIn] generates hResume for all Public Profiles. [http://www.linkedin.com/in/steveganz LinkedIn Public Profile Example].

* [http://www.antix.co.uk Anthony Johnston] has implemented hResume (Creation and Import) in the [http://cv.antix.co.uk Antix CV Builder], an example resume using this site can be found [http://cv.antix.co.uk/ant here]
** The example resume is ''invalid''; job titles are marked with an hCard that is missing a "fn" (either directly or via object). --[[User:Gazza|Gazza]] 04:23, 1 May 2007 (PDT)
*** This is fixed now --[[User:Antix|Ant]] 00:38, 8 Dec 2007 (GMT)

* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin]. See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here]. Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...

* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator]. The creator will generate hResume markup ready to cut and paste into your webpage.

== Copyright ==
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
* [[RyanKing]]: I release all of my contributions to the public domain.

Per the above, and the public domain release on the author, [[User:RyanKing|RyanKing]]'s, user page this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[include-pattern|include pattern]]
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* [[rfc-2119]]
* @TODO

=== Informative References ===
* @TODO

== Acknowledgements ==
=== Concept ===
* [http://theryanking.com/ Ryan King] ([http://technorati.com Technorati])
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati])
* James Levine ([http://simplyhired.com Simply Hired])
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati])

== Related Pages ==
{{hresume-related-pages}}

== Further Reading ==
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/ Getting Semantic With Microformats, Part 6: hResume] by Emily Lewis

[[Category:Draft Specifications]]
[[Category:hResume]]

citation-strawman-00

2011-02-01T19:10:11Z

HughP: /* Working straw schema */

<h1>Brian's citation straw format</h1>

;Editor
:Brian Suda

= Reasoning =

== implied schema (examples) ==
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

== implied schema (formats) ==
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

= Working straw schema =

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
*** Note - There are two uses for the language attribute (And therefore two language attributes should two be considered for inclusion in the schema). One value is the language the resource is written in (which the resource might polyglot work and therefore require multiple values in the attribute). The other attribute is the language which the resource is about. i.e. a Book written about German, written in English. This might be considered as language-subject and language-written. [http://www.language-archives.org/ OLAC] has recommended using the [http://en.wikipedia.org/wiki/ISO_639-3 ISO 639-3] to Identify the languages used. Additionally, there is room here to describe the script used in a resource (script not encoding). Some languages print in more than one script, I know this is common in several South Asian Languages where there might be a romanized script and a Indic script. --[[User:HughP|HughP]] 12:44 1 Feb 2011 (CST)
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

== Notes about missing / changed fields in the schema ==

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

= Examples =

Markup examples using the above format:

== Book ==

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

== Citing Private Communication ==

Needs an example.

== Citing Legal Cases ==
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

== Citing a Book ==

needs an example

== Citing a journal article ==

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

== Citing a magazine article ==

needs an example

== Citing a Patent ==

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

== Citing a conference publication==

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

== Citing an external website ==

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

= Discussion of Straw Format elements =

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

== 'hcite' as Root Element name ==

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

== The URI Element ==

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

== Date Fields ==

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

== Container ==

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== title ==
The problem of the use of the term "title" for the name of a citation item (or media item) is twofold:

# It's already used to mean "job title" in the context of microformats ([[hCard]]).
# The concept that it is being proposed to represent is the *name* of a citation item. "fn" already means the name of an item. we should not introduce a new term to mean the same thing as an existing term.

[[User:Tantek|Tantek]]

== fn ==
We should use "fn" for the name of a citation item rather than "title". [[User:Tantek|Tantek]]

*"fn" means the "name of a person, organisation or venue". [[User:AndyMabbett|Andy Mabbett]] 01:04, 4 Feb 2008
** This is false. "fn" by itself simply means "formatted name". "fn" when used in an [[hCard]] means "name of a person, organization or venue". "fn" when used in an [[hReview]] item means name of the item. Thus "fn" when used in a citation, or perhaps a citation item, would mean name of the cited item. [[User:Tantek|Tantek]]
***Its use in hReview does not accord with the defining instance in vCard's {{RFC2426}} (which makes no mention of reviews). [[User:AndyMabbett|Andy Mabbett]] 11:28, 4 Feb 2008 (PST)
**** microformats attempt to re-use the vocabulary from existing standards. such re-use does not necessarily imply wholesale re-use of original context. [[to-do]] this should be clarified in the principles/process. [[User:Tantek|Tantek]] 12:10, 4 Feb 2008 (PST)

* Some problems with using fn for the names of other things are being discussed as at Jan-Feb 2008 (see [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html] et seq). Any specific such problems should be extracted, summarized and moved here.

= Related Pages =

{{citation-related-pages}}

User:HughP

2011-02-01T19:07:25Z

HughP:

My name is Hugh. I use Micro-Formats. I also use Wordpress. Find out more here: [http://thejourneyler.org http://thejourneyler.org]

User:HughP

2011-02-01T19:06:04Z

HughP:

My name is Hugh. I use Micro-Formats. I also use Wordpress. Find out more here: [http://thejourneyler.org|http://thejourneyler.org]

User:HughP

2011-02-01T19:05:40Z

HughP:

My name is Hugh. I use Micro-Formats. I also use Wordpress. Find out more here: [[http://thejourneyler.org|http://thejourneyler.org]]

User:HughP

2011-02-01T19:04:25Z

HughP: New page: My name is Hugh. I use Micro-Formats. I also use Wordpress. Find out more Here: http://thejourneyler.org

My name is Hugh. I use Micro-Formats. I also use Wordpress. Find out more Here: [[http://thejourneyler.org]]

citation-strawman-00

2011-02-01T19:02:12Z

HughP: /* Working straw schema */

<h1>Brian's citation straw format</h1>

;Editor
:Brian Suda

= Reasoning =

== implied schema (examples) ==
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

== implied schema (formats) ==
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

= Working straw schema =

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
*** Note - There are two uses for the language attribute (And therefore two language attributes should two be considered for inclusion in the schema). One value is the language the resource is written in (which the resource might polyglot work and therefore require multiple values in the attribute). The other attribute is the language which the resource is about. i.e. a Book written about German, written in English. This might be considered as language-subject and language-written. [[http://www.language-archives.org/|OLAC]] has recommended using the [[http://en.wikipedia.org/wiki/ISO_639-3|ISO 639-3]] to Identify the languages used. Additionally, there is room here to describe the script used in a resource (script not encoding). Some languages print in more than one script, I know this is common in several South Asian Languages where there might be a romanized script and a Indic script. --[[User:HughP|HughP]] 12:44 1 Feb 2011 (CST)
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

== Notes about missing / changed fields in the schema ==

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

= Examples =

Markup examples using the above format:

== Book ==

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

== Citing Private Communication ==

Needs an example.

== Citing Legal Cases ==
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

== Citing a Book ==

needs an example

== Citing a journal article ==

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

== Citing a magazine article ==

needs an example

== Citing a Patent ==

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

== Citing a conference publication==

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

== Citing an external website ==

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

= Discussion of Straw Format elements =

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

== 'hcite' as Root Element name ==

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

== The URI Element ==

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

== Date Fields ==

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

== Container ==

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== title ==
The problem of the use of the term "title" for the name of a citation item (or media item) is twofold:

# It's already used to mean "job title" in the context of microformats ([[hCard]]).
# The concept that it is being proposed to represent is the *name* of a citation item. "fn" already means the name of an item. we should not introduce a new term to mean the same thing as an existing term.

[[User:Tantek|Tantek]]

== fn ==
We should use "fn" for the name of a citation item rather than "title". [[User:Tantek|Tantek]]

*"fn" means the "name of a person, organisation or venue". [[User:AndyMabbett|Andy Mabbett]] 01:04, 4 Feb 2008
** This is false. "fn" by itself simply means "formatted name". "fn" when used in an [[hCard]] means "name of a person, organization or venue". "fn" when used in an [[hReview]] item means name of the item. Thus "fn" when used in a citation, or perhaps a citation item, would mean name of the cited item. [[User:Tantek|Tantek]]
***Its use in hReview does not accord with the defining instance in vCard's {{RFC2426}} (which makes no mention of reviews). [[User:AndyMabbett|Andy Mabbett]] 11:28, 4 Feb 2008 (PST)
**** microformats attempt to re-use the vocabulary from existing standards. such re-use does not necessarily imply wholesale re-use of original context. [[to-do]] this should be clarified in the principles/process. [[User:Tantek|Tantek]] 12:10, 4 Feb 2008 (PST)

* Some problems with using fn for the names of other things are being discussed as at Jan-Feb 2008 (see [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html] et seq). Any specific such problems should be extracted, summarized and moved here.

= Related Pages =

{{citation-related-pages}}