Aaron Parecki

Sunday, June 10, 2018

• 
• 

  7:31pm

  Asleep

  5:52am

  Awake

  10h 21m

  Slept

  41m

  Awake for

  

  Portland, Oregon, USA

  Sun, Jun 10, 2018 5:52am -07:00
• 

  157.0lbs

  Weight

  19.2%

  Body Fat

  Portland, Oregon

  Sun, Jun 10, 2018 5:53am -07:00
• gRegorLove https://github.com/gRegorLove   •   Jun 10

  #92 Using micropub summary property as fallback
  

  The summary property is intended to be used for fallback for when the server doesn't recognize the other properties of the request. Most Micropub servers understand content and photo, but this is a great example of an interesting content type that is likely not supported by most servers yet. In this case, summary is the correct place for this fallback content. The content property would be misleading since normally the content property contains user-entered text. For example, if the user enters a note about why they wanted to read this, that could be included in the content property.

  Portland, Oregon, USA • 49°F

  Sun, Jun 10, 2018 7:11am -07:00
• manton https://github.com/manton   •   Jun 10

  I don't think this really solves the problem, though. If a server implementation prefers content over summary (which it should), with this example the context of the book title will be lost unless the server is updated to understand read-of.
  

  Maybe the logic could be "if the request contains *any* unrecognized properties, the server uses the summary property instead"?

  Portland, Oregon, USA • 55°F

  Sun, Jun 10, 2018 2:55pm -07:00