On Thu, Jun 4, 2015 at 7:52 AM, Brian Gerstle <bgerstle <at>
wikimedia.org> wrote:
Seems a bit inefficient to denormalize page content into the <meta> tags:
<meta name="description" content="Reflection in Swift is a limited
affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.">
and
<meta name="twitter:description" content="Reflection in Swift is a
limited affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.">
Twitter falls back to og:description if there is one (which is preferable as an open standard used by several companies), and Open Graph is RDFa so in theory this has the same meaning:
<span property="og:description">Reflection in Swift is a limited affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.<span>
without requiring you to duplicate the text of the lead paragraph. No idea whether all Open Graph consumers really understand it, though.