Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:28:33Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:28, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~microformats issues closed~~</entry-title>~~		{{DISPLAYTITLE:microformats issues closed}}

	This page is for archiving closed issues about microformats in general. See:		This page is for archiving closed issues about microformats in general. See:

Tantek: drafted with existing closed issues and a few more.

2011-10-27T01:04:52Z

drafted with existing closed issues and a few more.

New page

<entry-title>microformats issues closed</entry-title>

This page is for archiving closed issues about microformats in general. See:
* [[issues-resolved]] for resolved issues that have pending actions.
* [[issues]] for currently open issues.

== closed issues ==
<span id="Closed_Issues">Closed issues that have no further actions to take.</span>

=== closed 2005 ===
Closed issues that were raised in 2005.

* {{ClosedIssue}} 2005-07-?? raised by Bud(?).
*# ''Documents with user-generated content are hard to parse, and microformats present particular parsing challenges.''
*#* REJECTED. Strawman. Lack of specific examples of such documents. Insufficient detail - "particular parsing challenges" need to be described.

* {{ClosedIssue}} 2005-07-13T19:44-07:00 raised by [[User:Bud|Bud]]
*# Follow-up to previous issue: ''Tantek needs to supply some justification for why this is a strawman as every developer I have talked to has raised it. It may be that the solutions described below are sufficient to solve the issue. More neutral statements to that effect might be more constructive.''
*#* REJECTED. See [http://en.wikipedia.org/wiki/Straw_man Wikipedia: Straw man argument]. Saying "with user-generated content" out of context is a strawman. Leaving out a specific example makes it a hypothetical. Saying "particular parsing challenges", without stating them is meaningless. Hence strawman. Parsing questions should be phrased as such and discussed in [[IRC]] or the microformats-dev mailing list.

=== closed 2006 ===
Closed issues raised in 2006.
<div class="vevent">
* {{ClosedIssue}} <span class="summary vcard"><span class="dtstart">2006-10-17</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span> on [[wiki-feedback]]; moved here 2007-03-10.
<div class="description">
*# What is currently described as a "specification" on [[hCard]] and [[hCalendar]] is no such thing.
*# Andy, what would it take to turn it into a "specification"?--[[User:JoeAndrieu|JoeAndrieu]] 15:13, 24 Mar 2007 (PDT)
*# [Belated response; only just seen the question!] - for a start, removal of user commentary; versioning. [[User:AndyMabbett|Andy Mabbett]] 02:37, 14 Jan 2008 (PST)
*#* ACCEPTED PARTIAL. How versioning should work is under consideration with various iterations of microformats (hCard 1.0.1, 1.1) and microformats itself with [[microformats-2]]. There is nothing remaining to do specific to this issue however.
*#* RESOLVED [[process]] updated with better definitions for how/when a draft becomes a specification, and how a specification can become a standard. - [[User:Tantek|Tantek]]
</div>
</div>

* {{ClosedIssue}} 2006-12-08 raised by [[User:AndyMabbett|Andy Mabbett]].
*# As evidenced in [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007531.html discussion of an emailed response from eBay], the current position on the IP rights relating to microformats is unclear, or at least not clearly expressed. It seems to me that there should be an unambiguous statement of the current position, either for each individual format, or collectively, on a page to which people with concerns may be directed.
*#* ACCEPTED. A clearer statement of both copyright and patents both in specific specs and in general would be a good thing. In general, the end result that our current copyright/patent statements seek is Creative Commons, W3C, and IETF compatibility in terms of both copyrights, and royalty free patent policies. I [[to-do#Tantek|will work]] on this [[User:Tantek|Tantek]] 11:58, 9 Dec 2006 (PST)
*#* This appears to be unresolved; and in the light of, for example, [[hCard#Copyright the hCard 'spec']], the statement in the FAQ that "[http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Microformats are open standards licensed under Creative Commons Attribution]" to be, at best, erroneous and misleading. [[User:AndyMabbett|Andy Mabbett]] 11:04, 10 Mar 2007 (PST)
*#* Also [http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Attribution&curid=7391090&diff=117538680&oldid=117536621 causing concern here]. '''Prompt resolution would be advisable''' [[User:AndyMabbett|Andy Mabbett]] 09:04, 24 Mar 2007 (PDT)
*#** First, [[citation]] is not ready for use in Wikipedia anyway. Second, what is unclear about the Creative Commons/W3C/IETF license and patent statements? This appears to be a theoretical issue / nitpick. Yes, things can be made clearer, but "erroneous" and "misleading" are inaccurate labels.
*#** This is not a citation issue. For example, [[hcard#Copyright|hCard's current copyright statement]] is not compatible with the Creative Commons license:<br><blockquote>{{MicroFormatCopyrightStatement2004}}</blockquote><br>If you look at the wikicode, this is actually the "MicroFormatCopyrightStatement2004" default microformat copyright.--[[User:JoeAndrieu|JoeAndrieu]] 15:09, 24 Mar 2007 (PDT)
*#* ALL RESOLVED per:
*#** http://microformats.org/2007/12/29/making-open-standards-as-open-as-possible - all microformats wiki contributions since 2007-12-27 are placed into the public domain per CC-PD. - [[User:Tantek|Tantek]]
*#** [[hCard]] all editors/authors have put placed their work into the public domain per Creative Commons PD declaration and it's been [[hcard#Copyright|updated accordingly]] a while ago (~2007?). - [[User:Tantek|Tantek]]

=== closed 2007 ===
Closed issues raised in 2007.

* {{ClosedIssue}} 2007-03-24 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Further to the above (but out-dented for clarity), [[hresume|hResume]] cedes copyright to "the authors": "This specification is (C) 2006 by the authors"; and names just one author; Ryan King. What legal standing does the "the authors (sic) intend to submit..." clause have? What exists, to reassure someone (or some mega corporation's lawyers) contemplating or already using hResume that they won't be invoiced by Mr King? Why aren't the other people who contributed to that spec jointly credited with its copyright? [[User:AndyMabbett|Andy Mabbett]] 17:34, 24 Mar 2007 (PDT)
*#* ACCEPTED RESOLVED per: [[hResume]] all editors/authors have put placed their work into the public domain per Creative Commons PD declaration and it's also [[hresume#Copyright|been updated accordingly]] a while ago (~2007?). - [[User:Tantek|Tantek]]

* {{ClosedIssue}} 2007-03-25 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Also, there appears to be nothing on [[buttons]] to say that they're freely licensed, or public-domain. [[User:AndyMabbett|Andy Mabbett]] 03:01, 25 Mar 2007 (PDT)
*#* ACCEPTED RESOLVED. [[buttons]] has a [[buttons#Licensing|licensing section]] that now either makes it explicit or encourages contributors to do so on their own sites. That's all we can do. - [[User:Tantek|Tantek]]

* {{ClosedIssue}} 2007-04-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Shouldn't microformats be recognised on <code>ID</code> as well as <code>class</code>? In other words, if I know I'm gong to have only one review or only one location, or whatever, on a page, then <code>"id=hReview"</code>, <code>id="geo"</code> etc. are semantically valid and appropriate. [[User:AndyMabbett|Andy Mabbett]] 11:32, 1 Apr 2007 (PDT)
*#* REJECTED. This was considered a while ago and rejected for a number of reasons:
*#** Adds complexity for very little benefit. Using just one attribute (class) for a microformat makes them simpler and reduces chances of error. RDFa has been struggling with 'property' vs. 'rel' issues with just two attributes! - [[User:Tantek|Tantek]]
*#** Forcing an ID to be used for a microformat semantic is an unreasonable requirement to place on an attribute which can only have one value. The 'class' attribute works for microformats because authors can simply ''add'' microformats class names to their existing class values and have everything keep working. ID is single-valued and doesn't work that way. If there was a way to make ID multivalued that could help fix this, but then the first problem noted above, increased complexity, would still remain. - [[User:Tantek|Tantek]]

== see also ==
* [[issues]]
* [[issues-resolved]]

issues-closed - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

Tantek: drafted with existing closed issues and a few more.