Web Metadata for publishing


#1

I’ve been looking at how to provide metadata for social sharing for Plume blog and want to share some of the worms falling out of this can, and invite any advice, comment etc from those who know a bit about this stuff!

Refs

Useful refs I’ve collected:

Live Example

I took a look at what @RubenVerborgh uses on his blog for inspiration (below).

Ruben specifies the semantic vocabularies he’s using in the HTML/prefix attribute (in accordance with RDFa). I’m not sure this is necessary as it doesn’t seem to be referred to in articles I’ve seen, but looks like the ‘proper’ way to do this!


<html 
	lang=en 
	prefix="schema: http://schema.org/
	  og: http://ogp.me/ns#
	  fb: http://ogp.me/ns/fb#
	  article: http://ogp.me/ns/article#
	  bibo: http://purl.org/ontology/bibo/
	  sioc: http://rdfs.org/sioc/ns# 
	  bio: http://purl.org/vocab/bio/0.1/ 
	  time: http://www.w3.org/2006/time#" 
	
	resource="/blog/2018/12/28/designing-a-linked-data-developer-experience/" 
	typeof="schema:WebPage"> 
<head>
<meta charset=utf-8>
<title>Designing a Linked Data developer experience | Ruben Verborgh</title> 

<link rel=stylesheet href="/styles/main.css">
<link rel=alternate type="application/atom+xml" href="/blog/latest.xml" title="Ruben Verborgh’s blog">
<link rel=alternate type="application/rss+xml" href="//rubenverborgh.disqus.com/designing_a_linked_data_developer_experience/latest.rss" title="Comments on &ldquo;Designing a Linked Data developer experience&rdquo;">

<meta name=viewport content="width=device-width,initial-scale=1,minimum-scale=.5">

<meta property="dc:title" content="Designing a Linked Data developer experience"/>
<meta property="og:type" content=article>
<meta property="og:title" content="Designing a Linked Data developer experience">
<meta property="og:description" content="Making decentralized Web app development fun ◆ While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to focus on the Web; whereas our technologies are delivering results in specialized back-end systems, the promised intelligent end-user apps are not being created…">
<meta property="og:image" content="https://ruben.verborgh.org/images/blog/front-end-devs.jpg">
<meta property="og:url" content="https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/">
<meta property="article:author" content="https://ruben.verborgh.org/profile/#me">
<meta property="article:published_time" content="2018-12-28T16:30:00+01:00">
<meta property="twitter:card" content=summary>
<meta property="twitter:site" content="@RubenVerborgh">
<meta property="twitter:creator" content="@RubenVerborgh">

Metadata for Social Sharing

Random articles on the topic suggest something like the following is appropriate, so this is what I’m thinking of doing for Plume, maybe with extras from Ruben’s example.

Let me know if you agree or have any suggestions.

Minimum to cover twitter and fb:

<meta property="og:title" content="European Travel Destinations">
<meta property="og:description" content="Offering tour packages for individuals or groups.">
<meta property="og:image" content="http://euro-travel-example.com/thumbnail.jpg">
<meta property="og:url" content="http://euro-travel-example.com/index.htm">
<meta name="twitter:card" content="summary_large_image">
<meta property="og:site_name" content="European Travel, Inc.">
<meta name="twitter:image:alt" content="Alt text for image">

More:

<meta property="og:type" content="article" />
<meta name="twitter:creator" content="@author_handle">

WebID:

I haven’t seen any use of WebID yet. Would it make sense to use the WebID profile document URI like this, or in some other way:

<link rel=”author” href=”https://thewebalyst.solid.community/profile/card”/>

I haven’t decided what would be best for Plume yet, so if you have any thoughts or advice please share them.


Solid CMS - options for document creation and management
Solid Plume - simple blog app
Solid Plume - simple blog app
#2

Default prefix mappings do not need to be specified, but others must be: https://www.w3.org/2011/rdfa-context/rdfa-1.1

You missed mine then :slightly_smiling_face: I’m marked as the author of all my webpages.
Bonus: query all the data that comes out of my website: http://query.verborgh.org/


#3

Thanks Ruben, appreciated. I had thought I saw something for ‘author’ but not a WebID - I’m not sure how - because there it is… Doh!

Default prefix mappings do not need to be specified, but others must be: https://www.w3.org/2011/rdfa-context/rdfa-1.1

What are the consequences of messing this up? I see you use twitter:card without defining it, although it is not one of the predefined contexts.


#4

Then the properties will not be parsed.

Ah, but the Twitter markup is not RDFa. They use their own name= thingy.

I wrote about this craziness back in 2013: https://ruben.verborgh.org/publications/verborgh_web_2013/
With Semantic Web tech, we should be able to just write one thing, and the rest can be derived through reasoning (as I do on my website, which can be queried with multiple ontologies).


#5

Thanks very much for that paper Ruben, it is very informative and helps me fit different parts of the Semantic Web & Solid jigsaw together. I’d like to share it but is there a way to link to the text as HTML (I only found links to read it that downloaded a PDF)?

The paper raises questions for me too! I can dig myself and don’t want to absorb too much of you time, but if you have links to more on this area, and the issues with world modifying semantic description (eg for POST) I’d be interested to read more.

I note that this was published in 2013 so am interested to know if much has changed. My little knowledge of this area suggests not, but are there areas that have significantly improved or got significantly worse do you think?

If I understood, RDFa & Owl tried to pull the different Web ontologies/ontology makers together, but largely in vein, because we still have to include semantic markup redundantly (as in schema.org, open graph, twitter cards etc). This is a significant burden and disincentive I think.

People are still I expect abusing REST, largely because ‘they know not what they do’ :wink:, and I’m not sure if RESTdesc or anything else has made an impact on ‘world modification’ for agents. And as for:

‘However, it will take a strong cooperation between Web resource providers and agent developers to make the rise of the Web for agents happen in the not-too-distant future’

… I feel so depressed (to quote Marvin, the paranoid web agent!) :rofl:

Thanks again. I really appreciate the way you take time to help out and answer questions.


#6

I wish, those were my early days when I was more obedient :slightly_smiling_face:

Not technologically, but I think the momentum is different now.

Shapes are an important newcomer though.

You’re very welcome. Feel free to tag me if you see things that are relevant!