hBookmark: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(New page: hBookmark is a microformat for bookmark management based on the hReview microformat. Current Version is Draft 0.01 As usual, <pre> The key words "MUST", "MUST NOT", "REQUI...)
 
Line 14: Line 14:


Elements:
Elements:
* hBookmark ('''<code>hBookmark</code>''')
* hBookmark ('''<code>hBookmark</code>''')
** '''<code>uri</code>''' Standard URI. REQUIRED, Read/write support REQUIRED.  
** '''<code>uri</code>''' Standard URI. REQUIRED, Read/write support REQUIRED.  

Revision as of 17:34, 9 January 2011

hBookmark is a microformat for bookmark management based on the hReview microformat.

Current Version is Draft 0.01

As usual,

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119.


Schema

The hBookmark schema consists is based on the hReview microform format, and contains the following elements. They are summarized here, and explained in detail below. For technical meaning of capital 'REQUIRED'

Elements:

  • hBookmark (hBookmark)
    • uri Standard URI. REQUIRED, Read/write support REQUIRED.
    • summary text, 140 chars max. OPTIONAL, Read/write support REQUIRED.
    • descriptiontext with optional valid HTML markup. ' OPTIONAL, Read/write support REQUIRED.
    • tag text. One or more. OPTIONAL, Read/write support REQUIRED.
    • triTransitory Resource Identifier for bit.ly, etc. Date and service as optional attributes. .OPTIONAL, Read/write support OPTIONAL.
    • encoding Type of content of uri. .OPTIONAL, Read/write support OPTIONAL.