<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=LarelBocal</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=LarelBocal"/>
	<link rel="alternate" type="text/html" href="http://microformats.org/wiki/Special:Contributions/LarelBocal"/>
	<updated>2026-05-25T17:39:10Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=rest/microformat-pub-protocol&amp;diff=35376</id>
		<title>rest/microformat-pub-protocol</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=rest/microformat-pub-protocol&amp;diff=35376"/>
		<updated>2008-12-17T17:48:56Z</updated>

		<summary type="html">&lt;p&gt;LarelBocal: zeleltt&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;c4tvarlid&lt;br /&gt;
=[ Background Problem ]=&lt;br /&gt;
Microformat gives meaning to small chunks of text in one XHTML document.&lt;br /&gt;
&lt;br /&gt;
We can put several pieces of microformatted contents (e.g hCalendar,&lt;br /&gt;
hAtom, hCard etc) in a single XHTML document, and both human and&lt;br /&gt;
machine will be likely possible to understand and process each of the&lt;br /&gt;
pieces.&lt;br /&gt;
&lt;br /&gt;
Is it possible, if we (human) wish to hand-author just one of the&lt;br /&gt;
pieces (e.g to update/delete the entry represented by that piece of&lt;br /&gt;
hAtom), and submit it back to the remote server?&lt;br /&gt;
&lt;br /&gt;
=[ APP model draf-06 ]=&lt;br /&gt;
I will highlight two resources: &amp;quot;Collection&amp;quot; and &amp;quot;Member&amp;quot;, quoted from&lt;br /&gt;
[http://tools.ietf.org/wg/atompub/draft-ietf-atompub-protocol/draft-ietf-atompub-protocol-06.txt APP section 3]:&lt;br /&gt;
;&amp;quot;Collection&amp;quot;: A resource that contains a set of member IRIs.&lt;br /&gt;
;&amp;quot;Member&amp;quot;: A resource whose IRI is listed in a collection.&lt;br /&gt;
&lt;br /&gt;
In brief,&lt;br /&gt;
* &amp;quot;Collection&amp;quot; has a &amp;quot;href&amp;quot; IRI to accept POST to create a *new* member. See 8.1&lt;br /&gt;
* &amp;quot;Collection&amp;quot; has a &amp;quot;list-template&amp;quot; IRI to accept GET to *list* out members in the collection. See 9.0&lt;br /&gt;
* &amp;quot;Member&amp;quot; has a link *edit* IRI to accept GET, PUT, DELETE to manipulate the member. See 10.1&lt;br /&gt;
&lt;br /&gt;
APP is designed for machine. Both &amp;quot;what&amp;quot; and &amp;quot;how&amp;quot; are written in draft and have to be early-bound into both client and server codes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=[ a microformat way? ]=&lt;br /&gt;
Use &amp;quot;member&amp;quot; and &amp;quot;collection&amp;quot; classes based on the semantic in APP.&lt;br /&gt;
The &amp;quot;resource&amp;quot; is usually in microformat. Example: hEvent is a &amp;quot;member&amp;quot; and hCalendar is a &amp;quot;collection&amp;quot;. &lt;br /&gt;
Of course, a &amp;quot;member&amp;quot; may exists in a document without its &amp;quot;collection&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Use &amp;amp;lt;a&amp;gt; hyperlinks tell human &amp;quot;what&amp;quot; to do:&lt;br /&gt;
* click &amp;quot;edit&amp;quot; link to manipulate that particular &amp;quot;member&amp;quot;&lt;br /&gt;
* click &amp;quot;new&amp;quot; link to create a new member in the &amp;quot;collection&amp;quot;&lt;br /&gt;
* click &amp;quot;list&amp;quot; link to list the members in the &amp;quot;collection&amp;quot;&lt;br /&gt;
----------&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;nn class=&amp;quot;member&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;amp;lt;a href=&amp;quot;[uri]&amp;quot;  rel=&amp;quot;edit&amp;quot;&amp;gt;Edit&amp;amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;amp;lt;/nn&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;nn class=&amp;quot;collection&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;amp;lt;a href=&amp;quot;[uri]&amp;quot; rel=&amp;quot;new&amp;quot;&amp;gt;New&amp;amp;lt;/a&amp;gt;&lt;br /&gt;
        &amp;amp;lt;a href=&amp;quot;[uri]&amp;quot; rel=&amp;quot;list&amp;quot;&amp;gt;List&amp;amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;amp;lt;/nn&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
---------&lt;br /&gt;
&lt;br /&gt;
Use &amp;amp;lt;form&amp;gt; (X)HTML Form to tell human &amp;quot;how&amp;quot; to do:&lt;br /&gt;
* after clicking &amp;quot;edit&amp;quot; link, user receive the member, plus a form to&lt;br /&gt;
* update/delete it.&lt;br /&gt;
* after clicking &amp;quot;new&amp;quot; link, user receive a form to create new member.&lt;br /&gt;
* after clicking &amp;quot;list&amp;quot; link, user receive a collection of members, plus&lt;br /&gt;
* a form to query them.&lt;br /&gt;
---------&lt;br /&gt;
Example after click &amp;quot;edit&amp;quot; link of hEvent, users may receive a XHTML:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;div class=&amp;quot;vevent member&amp;quot;&amp;gt;&lt;br /&gt;
&amp;amp;lt;a href=&amp;quot;[uri]&amp;quot;  rel=&amp;quot;edit&amp;quot;&amp;gt;Edit&amp;amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;20051212&amp;quot;&amp;gt; December 12, 2005 &amp;amp;lt;/abbr&amp;gt; -&lt;br /&gt;
&amp;amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt; Birthday Party &amp;amp;lt;/span&amp;gt; - at&lt;br /&gt;
&amp;amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt; Home &amp;amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;form action=&amp;quot;[uri]&amp;quot; method=&amp;quot;post&amp;quot; id=&amp;quot;vevent-form&amp;quot;&amp;gt;&lt;br /&gt;
&amp;amp;lt;textarea id=&amp;quot;code&amp;quot; name=&amp;quot;code&amp;quot;&amp;gt;&lt;br /&gt;
&amp;amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&amp;amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title.......... &amp;amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;amp;lt;/textarea&amp;gt;&lt;br /&gt;
&amp;amp;lt;button type=&amp;quot;submit&amp;quot; id=&amp;quot;update&amp;quot; name=&amp;quot;update&amp;quot;&amp;gt;Update&amp;amp;lt;/button&amp;gt;&lt;br /&gt;
&amp;amp;lt;button type=&amp;quot;submit&amp;quot; id=&amp;quot;delete&amp;quot; name=&amp;quot;delete&amp;quot;&amp;gt;Delete&amp;amp;lt;/button&amp;gt;&lt;br /&gt;
&amp;amp;lt;/form&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
* simple and easy for human (just read, click, type ;-)&lt;br /&gt;
* able to create, edit or list microcontents. (standard HTTP, XHTML)&lt;br /&gt;
* late-binding (e.g human will discover &amp;quot;what&amp;quot; and &amp;quot;how&amp;quot; to do by following links)&lt;br /&gt;
* hand authoring (use &amp;amp;lt;form&amp;gt;. Question: human prefers plain &amp;amp;lt;textarea&amp;gt; or h*-o-matic?)&lt;br /&gt;
* and still machine parsable (all are still microformat, and standard XHTML)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=[ Brainstorming.. ]=&lt;br /&gt;
== Just &amp;amp;lt;textarea&amp;gt; ?==&lt;br /&gt;
The &amp;amp;lt;textarea&amp;gt; is just a basic idea. More fields and h*-o-matic (with&lt;br /&gt;
script) can be added as an alternate to help users to author a&lt;br /&gt;
microcontent.&lt;br /&gt;
&lt;br /&gt;
== Where should be use? ==&lt;br /&gt;
Many blogs/forums provide &amp;quot;edit&amp;quot;, &amp;quot;new post&amp;quot; links near displayed&lt;br /&gt;
entries after the owner is authenticated. A blog user should be able&lt;br /&gt;
to update blogroll (at the side bar),  categories and entries on the&lt;br /&gt;
same page easily by just clicking links.&lt;br /&gt;
&lt;br /&gt;
== So easy? It's just the same old normal way we build web pages! ==&lt;br /&gt;
That's the point, isn't it? ;-) However, I'm not sure about how&lt;br /&gt;
machine/custom application will parse and understand XHTML &amp;amp;lt;form&amp;gt;&lt;br /&gt;
element.&lt;br /&gt;
A [http://www.markbaker.ca/2003/05/RDF-Forms/ RDF Form] is out there as a machine-friendly similar version of  HTML Form.&lt;/div&gt;</summary>
		<author><name>LarelBocal</name></author>
	</entry>
</feed>