rest/microformat-pub-protocol - Revision history

RyanKing: Reverted edits by LarelBocal (Talk) to last version by Tantek

2008-12-17T21:10:02Z

Reverted edits by LarelBocal (Talk) to last version by Tantek

← Older revision		Revision as of 21:10, 17 December 2008
Line 1:		Line 1:
	~~c4tvarlid~~
	=[ Background Problem ]=		=[ Background Problem ]=
	Microformat gives meaning to small chunks of text in one XHTML document.		Microformat gives meaning to small chunks of text in one XHTML document.

LarelBocal: zeleltt

2008-12-17T17:48:56Z

zeleltt

← Older revision		Revision as of 17:48, 17 December 2008
Line 1:		Line 1:
			c4tvarlid
	=[ Background Problem ]=		=[ Background Problem ]=
	Microformat gives meaning to small chunks of text in one XHTML document.		Microformat gives meaning to small chunks of text in one XHTML document.

Tantek: Reverted edit of MuwEo0, changed back to last version by DrErnie

2007-04-11T14:27:50Z

Reverted edit of MuwEo0, changed back to last version by DrErnie

← Older revision		Revision as of 14:27, 11 April 2007
Line 30:		Line 30:
	Of course, a "member" may exists in a document without its "collection".		Of course, a "member" may exists in a document without its "collection".

	Use		Use <a> hyperlinks tell human "what" to do:
			* click "edit" link to manipulate that particular "member"
			* click "new" link to create a new member in the "collection"
			* click "list" link to list the members in the "collection"
			----------
			<pre>
			<nn class="member">
			<a href="[uri]" rel="edit">Edit</a>
			</nn>

			<nn class="collection">
			<a href="[uri]" rel="new">New</a>
			<a href="[uri]" rel="list">List</a>
			</nn>
			</pre>
			---------

			Use <form> (X)HTML Form to tell human "how" to do:
			* after clicking "edit" link, user receive the member, plus a form to
			* update/delete it.
			* after clicking "new" link, user receive a form to create new member.
			* after clicking "list" link, user receive a collection of members, plus
			* a form to query them.
			---------
			Example after click "edit" link of hEvent, users may receive a XHTML:
			<pre>
			<div class="vevent member">
			<a href="[uri]" rel="edit">Edit</a>
			<abbr class="dtstart" title="20051212"> December 12, 2005 </abbr> -
			<span class="summary"> Birthday Party </span> - at
			<span class="location"> Home </span>
			</div>

			<form action="[uri]" method="post" id="vevent-form">
			<textarea id="code" name="code">
			<div class="vevent"><abbr class="dtstart" title.......... </div>
			</textarea>
			<button type="submit" id="update" name="update">Update</button>
			<button type="submit" id="delete" name="delete">Delete</button>
			</form>
			</pre>
			* simple and easy for human (just read, click, type ;-)
			* able to create, edit or list microcontents. (standard HTTP, XHTML)
			* late-binding (e.g human will discover "what" and "how" to do by following links)
			* hand authoring (use <form>. Question: human prefers plain <textarea> or h*-o-matic?)
			* and still machine parsable (all are still microformat, and standard XHTML)


			=[ Brainstorming.. ]=
			== Just <textarea> ?==
			The <textarea> is just a basic idea. More fields and h*-o-matic (with
			script) can be added as an alternate to help users to author a
			microcontent.

			== Where should be use? ==
			Many blogs/forums provide "edit", "new post" links near displayed
			entries after the owner is authenticated. A blog user should be able
			to update blogroll (at the side bar), categories and entries on the
			same page easily by just clicking links.

			== So easy? It's just the same old normal way we build web pages! ==
			That's the point, isn't it? ;-) However, I'm not sure about how
			machine/custom application will parse and understand XHTML <form>
			element.
			A [http://www.markbaker.ca/2003/05/RDF-Forms/ RDF Form] is out there as a machine-friendly similar version of HTML Form.

MuwEo0 at 13:57, 11 April 2007

2007-04-11T13:57:48Z

← Older revision		Revision as of 13:57, 11 April 2007
Line 30:		Line 30:
	Of course, a "member" may exists in a document without its "collection".		Of course, a "member" may exists in a document without its "collection".

	Use ~~<a> hyperlinks tell human "what" to do:~~		Use
	* click "edit" link to manipulate that particular "member"
	* click "new" link to create a new member in the "collection"
	* click "list" link to list the members in the "collection"
	~~----------~~
	~~<pre>~~
	~~<nn class="member">~~
	~~<a href="[uri]" rel="edit">Edit</a>~~
	~~</nn>~~

	~~<nn class="collection">~~
	~~<a href="[uri]" rel="new">New</a>~~
	~~<a href="[uri]" rel="list">List</a>~~
	~~</nn>~~
	~~</pre>~~
	~~---------~~

	~~Use <form> (X)HTML Form to tell human "how" to do:~~
	* after clicking "edit" link, user receive the member, plus a form to
	* update/delete it.
	* after clicking "new" link, user receive a form to create new member.
	* after clicking "list" link, user receive a collection of members, plus
	* a form to query them.
	~~---------~~
	~~Example after click "edit" link of hEvent, users may receive a XHTML:~~
	~~<pre>~~
	~~<div class="vevent member">~~
	~~<a href="[uri]" rel="edit">Edit</a>~~
	~~<abbr class="dtstart" title="20051212"> December 12, 2005 </abbr> -~~
	~~<span class="summary"> Birthday Party </span> - at~~
	~~<span class="location"> Home </span>~~
	~~</div>~~

	~~<form action="[uri]" method="post" id="vevent-form">~~
	~~<textarea id="code" name="code">~~
	~~<div class="vevent"><abbr class="dtstart" title.......... </div>~~
	~~</textarea>~~
	~~<button type="submit" id="update" name="update">Update</button>~~
	~~<button type="submit" id="delete" name="delete">Delete</button>~~
	~~</form>~~
	~~</pre>~~
	* simple and easy for human (just read, click, type ;-)
	* able to create, edit or list microcontents. (standard HTTP, XHTML)
	* late-binding (e.g human will discover "what" and "how" to do by following links)
	* hand authoring (use <form>. Question: human prefers plain <textarea> or h*-o-matic?)
	* and still machine parsable (all are still microformat, and standard XHTML)


	~~=[ Brainstorming.. ]=~~
	~~== Just <textarea> ?==~~
	~~The <textarea> is just a basic idea. More fields and h*-o-matic (with~~
	~~script) can be added as an alternate to help users to author a~~
	~~microcontent.~~

	~~== Where should be use? ==~~
	~~Many blogs/forums provide "edit", "new post" links near displayed~~
	~~entries after the owner is authenticated. A blog user should be able~~
	~~to update blogroll (at the side bar), categories and entries on the~~
	~~same page easily by just clicking links.~~

	~~== So easy? It's just the same old normal way we build web pages! ==~~
	~~That's the point, isn't it? ;-) However, I'm not sure about how~~
	~~machine/custom application will parse and understand XHTML <form>~~
	~~element.~~
	~~A [http://www.markbaker.ca/2003/05/RDF-Forms/ RDF Form] is out there as a machine-friendly similar version of HTML Form.~~

DrErnie at 23:11, 16 December 2005

2005-12-16T23:11:07Z

← Older revision		Revision as of 23:11, 16 December 2005
Line 35:		Line 35:
	* click "list" link to list the members in the "collection"		* click "list" link to list the members in the "collection"
	----------		----------
	<pre~~><code~~>		<pre>
	<nn class="member">		<nn class="member">
	<a href="[uri]" rel="edit">Edit</a>		<a href="[uri]" rel="edit">Edit</a>
Line 44:		Line 44:
	<a href="[uri]" rel="list">List</a>		<a href="[uri]" rel="list">List</a>
	</nn>		</nn>
	~~</code>~~</pre>		</pre>
	---------		---------

Line 55:		Line 55:
	---------		---------
	Example after click "edit" link of hEvent, users may receive a XHTML:		Example after click "edit" link of hEvent, users may receive a XHTML:
	<pre~~><code~~>		<pre>
	<div class="vevent member">		<div class="vevent member">
	<a href="[uri]" rel="edit">Edit</a>		<a href="[uri]" rel="edit">Edit</a>
Line 70:		Line 70:
	<button type="submit" id="delete" name="delete">Delete</button>		<button type="submit" id="delete" name="delete">Delete</button>
	</form>		</form>
	~~</code>~~</pre>		</pre>
	* simple and easy for human (just read, click, type ;-)		* simple and easy for human (just read, click, type ;-)
	* able to create, edit or list microcontents. (standard HTTP, XHTML)		* able to create, edit or list microcontents. (standard HTTP, XHTML)

DrErnie: code format

2005-12-16T23:10:16Z

code format

← Older revision		Revision as of 23:10, 16 December 2005
Line 10:		Line 10:
	pieces (e.g to update/delete the entry represented by that piece of		pieces (e.g to update/delete the entry represented by that piece of
	hAtom), and submit it back to the remote server?		hAtom), and submit it back to the remote server?


	=[ APP model draf-06 ]=		=[ APP model draf-06 ]=
Line 36:		Line 35:
	* click "list" link to list the members in the "collection"		* click "list" link to list the members in the "collection"
	----------		----------
			<pre><code>
	<nn class="member">		<nn class="member">
	<a href="[uri]" rel="edit">Edit</a>		<a href="[uri]" rel="edit">Edit</a>
Line 44:		Line 44:
	<a href="[uri]" rel="list">List</a>		<a href="[uri]" rel="list">List</a>
	</nn>		</nn>
			</code></pre>
	---------		---------

Line 54:		Line 55:
	---------		---------
	Example after click "edit" link of hEvent, users may receive a XHTML:		Example after click "edit" link of hEvent, users may receive a XHTML:
	~~...~~		<pre><code>
	<div class="vevent member">		<div class="vevent member">
	<a href="[uri]" rel="edit">Edit</a>		<a href="[uri]" rel="edit">Edit</a>
Line 64:		Line 65:
	<form action="[uri]" method="post" id="vevent-form">		<form action="[uri]" method="post" id="vevent-form">
	<textarea id="code" name="code">		<textarea id="code" name="code">
	<div class="vevent"><abbr class="dtstart" title.......... </div>		<div class="vevent"><abbr class="dtstart" title.......... </div>
	</textarea>		</textarea>
	<button type="submit" id="update" name="update">Update</button>		<button type="submit" id="update" name="update">Update</button>
	<button type="submit" id="delete" name="delete">Delete</button>		<button type="submit" id="delete" name="delete">Delete</button>
	</form>		</form>
	~~.....~~		</code></pre>
	~~-----------~~
	* simple and easy for human (just read, click, type ;-)		* simple and easy for human (just read, click, type ;-)
	* able to create, edit or list microcontents. (standard HTTP, XHTML)		* able to create, edit or list microcontents. (standard HTTP, XHTML)

DrErnie: extracted from email form toydi

2005-12-16T23:08:33Z

extracted from email form toydi

New page

=[ Background Problem ]=
Microformat gives meaning to small chunks of text in one XHTML document.

We can put several pieces of microformatted contents (e.g hCalendar,
hAtom, hCard etc) in a single XHTML document, and both human and
machine will be likely possible to understand and process each of the
pieces.

Is it possible, if we (human) wish to hand-author just one of the
pieces (e.g to update/delete the entry represented by that piece of
hAtom), and submit it back to the remote server?

=[ APP model draf-06 ]=
I will highlight two resources: "Collection" and "Member", quoted from
[http://tools.ietf.org/wg/atompub/draft-ietf-atompub-protocol/draft-ietf-atompub-protocol-06.txt APP section 3]:
;"Collection": A resource that contains a set of member IRIs.
;"Member": A resource whose IRI is listed in a collection.

In brief,
* "Collection" has a "href" IRI to accept POST to create a *new* member. See 8.1
* "Collection" has a "list-template" IRI to accept GET to *list* out members in the collection. See 9.0
* "Member" has a link *edit* IRI to accept GET, PUT, DELETE to manipulate the member. See 10.1

APP is designed for machine. Both "what" and "how" are written in draft and have to be early-bound into both client and server codes.

=[ a microformat way? ]=
Use "member" and "collection" classes based on the semantic in APP.
The "resource" is usually in microformat. Example: hEvent is a "member" and hCalendar is a "collection".
Of course, a "member" may exists in a document without its "collection".

Use <a> hyperlinks tell human "what" to do:
* click "edit" link to manipulate that particular "member"
* click "new" link to create a new member in the "collection"
* click "list" link to list the members in the "collection"
----------
<nn class="member">
<a href="[uri]" rel="edit">Edit</a>
</nn>

<nn class="collection">
<a href="[uri]" rel="new">New</a>
<a href="[uri]" rel="list">List</a>
</nn>
---------

Use <form> (X)HTML Form to tell human "how" to do:
* after clicking "edit" link, user receive the member, plus a form to
* update/delete it.
* after clicking "new" link, user receive a form to create new member.
* after clicking "list" link, user receive a collection of members, plus
* a form to query them.
---------
Example after click "edit" link of hEvent, users may receive a XHTML:
...
<div class="vevent member">
<a href="[uri]" rel="edit">Edit</a>
<abbr class="dtstart" title="20051212"> December 12, 2005 </abbr> -
<span class="summary"> Birthday Party </span> - at
<span class="location"> Home </span>
</div>

<form action="[uri]" method="post" id="vevent-form">
<textarea id="code" name="code">
<div class="vevent"><abbr class="dtstart" title.......... </div>
</textarea>
<button type="submit" id="update" name="update">Update</button>
<button type="submit" id="delete" name="delete">Delete</button>
</form>
.....
-----------
* simple and easy for human (just read, click, type ;-)
* able to create, edit or list microcontents. (standard HTTP, XHTML)
* late-binding (e.g human will discover "what" and "how" to do by following links)
* hand authoring (use <form>. Question: human prefers plain <textarea> or h*-o-matic?)
* and still machine parsable (all are still microformat, and standard XHTML)

=[ Brainstorming.. ]=
== Just <textarea> ?==
The <textarea> is just a basic idea. More fields and h*-o-matic (with
script) can be added as an alternate to help users to author a
microcontent.

== Where should be use? ==
Many blogs/forums provide "edit", "new post" links near displayed
entries after the owner is authenticated. A blog user should be able
to update blogroll (at the side bar), categories and entries on the
same page easily by just clicking links.

== So easy? It's just the same old normal way we build web pages! ==
That's the point, isn't it? ;-) However, I'm not sure about how
machine/custom application will parse and understand XHTML <form>
element.
A [http://www.markbaker.ca/2003/05/RDF-Forms/ RDF Form] is out there as a machine-friendly similar version of HTML Form.