What follows is a list of supported text based object types.
- Article (
article)
- For medium to large, episodic and / or timestamped texts
- Compatible with µf2 h-entry
- Body file part is mapped to the
e-contentproperty - See IWC articles
- Notes (
note)
- For short, typically unstructured and possibly timestamped (plain)texts
- Compatible with µf2 h-entry
- Body file part is mapped to the
e-contentproperty - See IWC notes
- Comments / replies (
reply)
- Similar to notes, but in reply to another resource which is necessary to know in order to fully understand the reply
- Compatible with µf2 h-entry
- Body file part is mapped to the
e-contentproperty - See IWC notes
- Code (
code)
- For source code snippets
- Compatible with µf2 h-entry
- Body file part is mapped to the
e-contentproperty - Custom
p-language-nameandp-language-versionproperties to denote the programming language and version as hint for syntax highlighters etc. - See IWC code
- Event (
event)
- For events
- Compatible with µf2 h-event
- Body file part is mapped to?
- See IWC event
- RSVP (
rsvp)
- Similar to replies, but in response to an event post
- Compatible with µf2 h-entry
- Body file part is mapped to the draft
p-rsvpproperty - See IWC RSVP
- Favourite (
favourite)
- For favourites as on Twitter
- Compatible with µf2 h-entry
- Body file part is mapped to the
u-like-ofproperty - See IWC favourite
- Like (
like)
- For likes like on Facebook, Instagram etc.
- Compatible with µf2 h-entry
- Body file part is mapped to the
u-like-ofproperty - See IWC like
- Repost (
repost)
- For pure 100% re-publications of another post (e.g. Retweet, Reblogging etc.)
- Compatible with µf2 h-entry
- Body file part is mapped to the
u-repost-ofproperty - See IWC like
- Bookmark (
bookmark)
- For bookmarks consisting of a URL, sometimes with a description or cite
- Compatible with µf2 h-entry
- Body file part is mapped to the
e-contentproperty - Special property
u-bookmark-ofto denote the bookmarked URL - See IWC bookmark
- Checkin (
checkin)
- For venue checkins
- Compatible with µf2 h-entry
- Body file part is mapped to?
- Has a
p-location h-cardproperty for setting the venue - What about referencing a venue post?
- See IWC checkin
- Review / recommendation / rating (
review)
- For reviews, recommendations or ratings
- Compatible with µf2 h-review
- Body file part is mapped to the
e-descriptionproperty
- Venue / address (
venue)
- Named locations or address / geo, typically used for checkins
- Compatible with a basic µf2 h-card
- Body file part is mapped to?
- See IWC venue and µf2 opening hours
- Geographical coordinates (
geo)
- WGS84 geographic coordinates, typically used by checkins and events
- Compatible with µf2 h-geo
- Body file part is mapped to?
- See IWC location
- Contact card (
contact)
- Person or organization details
- Compatible with µf2 h-card
- Body file part is mapped to?
- See IWC contact
- Address (
address)
- Postal address
- Compatible with µf2 h-adr
- Body file part is mapped to?
- Citation (
cite)
- Citation or reference to online publication
- Compatible with µf2 h-cite
- Body file part is mapped to the
p-contentproperty - See IWC citation
- Project (
project)
- Citation or reference to online publication
- Compatible with µf2 h-project
- Body file part is mapped to the
e-descriptionproperty - What about a
productobject type?
- Item (
item)
- As base for a review, project / product or event (in rare cases)
- Compatible with µf2 h-item
- Body file part is mapped to?
Media objects consist of two files: The media file and a like-named YAML file containing the meta data. In addition, the meta data might be embedded into the media file in case the file format supports this.
- Images (
image)
- For photos or images with an optional caption / description
- Compatible with µf2 h-entry
- Has a reference to the image file that is mapped to the
u-photoproperty - Body file part is mapped to the
e-contentproperty (image description) - All image formats are allowed
- See IWC photos
- Audio (
audio)
- For audio files / sound recordings with an optional caption / description
- Compatible with µf2 h-entry
- Has a reference to the audio file that is mapped to the
u-audioproperty - Body file part is mapped to the
e-contentproperty (audio file description) - All audio formats are allowed
- See IWC audio
- Video (
video)
- For video files with an optional caption / description
- Compatible with µf2 h-entry
- Has a reference to the video file that is mapped to the
u-videoproperty - Body file part is mapped to the
e-contentproperty (audio file description) - All video formats are allowed
- See IWC video