4.2.1 Publishers

Conforming publishers are implementations that create and publish conforming documents. Conforming publishers must make conforming documents available according to the serialization requirements of this document. Conforming publishers must consider privacy as described in the Privacy section of this document. Conforming publishers must consider security as described in the Security Considerations section of this document.

A non-exhaustive list of example publishers includes:

• A social network
• A personal web site
• A document publishing system
• A bridge from a non-conforming social network
• A document converter from similar document types such as RSS or Atom

4.2.2 Consumers

Conforming consumers are implementations that read and analyze conforming documents. Conforming consumers must not halt on any unrecognized properties or types.

Conforming consumers may re-publish conforming documents in other other data formats. Conforming consumers may present conforming documents to a user on screen, in print, in audio format, or using other presentation mechanisms. Conforming consumers must faithfully translate the information represented in conforming documents into these other formats or media. Conforming consumers that re-publish conforming documents must consider privacy and security as described in the Privacy section and Security Considerations section of this document.

A non-exhaustive list of example consumers includes:

• A social network
• A search engine
• A feed reader
• A document validator
• A feed aggregator

5.2.1 Post Objects

A post is composed of a "type" property, and one or more additional properties that describe the post.

The "type" property has a value that describes the vocabulary of this post. Common values include "entry", "card", etc. See Microformats 2 vocabularies for the full list when using a microformats based vocabulary.

Any additional properties in the post object are considered part of the post's vocabulary.

5.2.2 Post Properties

The list of valid post properties is defined by the vocabularies. This allows new vocabularies to be developed outside the development of the syntax.

Most values will be strings. If a property (such as `author` for example) references another object, it may be serialized in two ways: as an object serialized as the property value or as the unique identifier or URL where the object can be found. See Using References

Values may also be arrays if the vocabulary allows for multiple values of the property.

5.2.3 Example Post

{
  "type": "entry",
  "published": "2015-10-20T15:49:00-0700",
  "url": "http://example.com/post/fsjeuu8372",
  "author": {
    "type": "card",
    "name": "Alice",
    "url": "http://alice.example.com",
    "photo": "http://alice.example.com/photo.jpg"
  },
  "name": "Hello World",
  "content": "This is a blog post",
  "category": "Posts"
}

{
  "type": "entry",
  "published": "2015-10-20T15:49:00-0700",
  "url": "http://example.com/like/r23eugi02c",
  "author": {
    "type": "card",
    "name": "Alice",
    "url": "http://alice.example.com",
    "photo": "http://alice.example.com/photo.jpg"
  },
  "like-of": "http://bob.example.com/post/100",
  "category": ["Likes", "Posts"]
}

5.4.1 Multiple URLs for video/audio/picture

Since HTML video/audio/picture tags may have multiple URLs, we need a way to convey this information in the JSON representation.

<div class="h-entry">
  <video class="u-video" width="640" height="360" preload controls>
    <source src="sample_h264.mov" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />
    <source src="sample_ogg.ogv" type='video/ogg; codecs="theora, vorbis"' />
    <source src="sample_webm.webm" type='video/webm; codecs="vp8, vorbis"' />
  </video>
</div>

{
  "type": "entry",
  "video": [
    {
      "content-type": "video/mp4",
      "url": "sample_h264.mov"
    },
    {
      "content-type": "video/ogg",
      "url": "sample_ogg.ogg"
    },
    {
      "content-type": "video/webm",
      "url": "sample_webm.webm"
    }
  ]
}

9.2.2 Required Fields and Required Formats

The following fields have additional constraints to be a valid JF2 Feed that only apply to the top level feed object, its child entry object, and any properties of them.

• type MUST be defined with a value of "feed" on the top level entry. All other sub-object items MUST NOT have a type value of "feed". All direct children of the top level feed object MUST have a value of "entry".
• name MUST be defined on the top level "feed" object. This value MUST be a single string value. Any direct children of the top level item SHOULD have this property and if present MUST be a single string value.
• url SHOULD be defined on the top level "feed" object. This value MUST be a single string value and is expected to contain the URL of the data which this JF2 Feed describes. Additionally, if present in the author property object, or any direct child entry object, it MUST contain a single string value only and that value must be a [URL].
• photo MUST be a single string value if present on the top level feed object, its author property object, or any direct child entry object and MUST be a valid [URL].
• uid MUST be present on any entry object which is a direct child of the top level feed object. This property MUST be a single string value and MUST uniquely identify this entry object. This MAY be a duplicate of the entry's url property.
• published SHOULD be present on any entry object which is a direct child of the top level feed object. If present, this property MUST be a single string value and MUST be formatted as specified by [ISO8601].
• updated MAY be present on any entry object which is a direct child of the top level feed object. If present, this property MUST be a single string value and MUST be formatted as specified by [ISO8601].
• category MAY be present on any entry object which is a direct child of the top level feed object. If present, this property MUST be an array of string values.
• author MAY be present on the top level feed or second level entry objects. If present, it MUST be an object and it MUST contain at least a name, url, or photo property.
• content MAY be present on any entry object which is a direct child of the top level feed object. If present, this property MUST be an object as described in the html content regardless if only a text/plain version is available.
• summary MAY be present on any second level entry object. If present, it MUST be a single string.
• video or audio MAY be present on any second level entry object. If present, it MUST be an object as described in multiple urls section with at least a 'url' property which MUST be a single string and a valid [URL].

9.2.3 Discovery

The JF2 Feed for a page may be published as HTTP Link header [RFC5988], or as an HTML <link> or <a> tag element with the following attributes.

rel="alternate" type="application/jf2feed+json" href="http://www.example.com/jf2feed.json" 

9.2.4 JF2 Feed Example

{
    "type": "feed",
    "url": "https://example.org/myfeed.html",
    "name": "Brent Simmons’s Microblog",
    "author": {
        "type": "card",
        "name": "Brent Simmons",
        "url": "http://example.org/",
        "photo": "https://example.org/avatar.png"
    },
    "children": [
        {
            "type": "entry",
            "uid": "https://example.org/2347259",
            "url": "https://example.org/2347259",
            "content": {
              "text": "Cats are neat. \n\nhttps://example.org/cats"
            },
            "published": "2016-02-09T14:22:00-07:00"
        }
    ]
}