I haven't done a week in review since like May but REST ASSURED I'm keeping notes in a text file and I will flood you with all of them at some point. I'm behind on photo logging and like to link to stuff from the WiR, is why.
Post created with https://apps.rhiaro.co.uk/no-ceremonies-are-necessary
In reply to: http://kongaloosh.com/e/2015/11/10/i-should-probably-get-brid
Have you tried Quill Editor?
And you could generally ask around IWC about various interfaces other people are using and see if there's one you like. You can use different things for different types of post. I'm totally going to write a checkins client soon.
🔁 http://werd.io/2015/publish-on-your-own-site-reflect-inwardly
Amy shared http://werd.io/2015/publish-on-your-own-site-reflect-inwardly
My instinct is telling me to separate a 'raw' blog post from a rendered version which includes html markup, css styles, replies from other people, a header, footer, maybe links to other pages on my website on a menu somewhere, ...etc. Because an instance of a blog post is not the same as the post mashed into an HTML page along with replies and other stuff. The replies can stand alone on the social web, so the original post should be able to.
So 'raw' post URIs are in the form https://rhiaro.co.uk/llog/unique-post-slug and the rendered versions are found at https://rhiaro.co.uk/yyyy/mm/unique-post-slug. The rendered versions have a slashy-datey URL because it makes it obvious that you can filter back to temporal aggregates by removing parts of the URL. It's just plumbing and a bit of UX++, which is partly why I don't want to use this format as the URI for the blog itself (I might change my plumbing one day).
Dereferencing the rendered URI obviously returns the rendered page in all its glory.
Dereferencing the 'raw' URI should still return a document, not redirect, because a blog post can be retrieved over HTTP. But what exactly should it return? A bunch of plain text turtle maybe; all the triples with the URI as the subject. Or minimally marked up HTML (including microformats, I suppose, and maybe RDFa). I guess I just have an arbitrary decision to make here.
So what's the relationship between the 'raw' URI and the rendered one? Maybe <raw> foaf:primaryTopicOf <rendered> and <rendered> foaf:primaryTopic <raw>? (Or maybe I should coin a new renderedAt property to make the relationship clearer).
But when people want to start sending replies from their own sites, they're automatically going to want to use the rendered URI as the subject of their in-reply-to, however they do it, which would be technically incorrect; they should be replying to the blog post itself, not this rendering of it. Or maybe this is a context in which it doesn't matter, and the 'raw' and the rendered are essentially sameAs each other.
Maybe I call the 'raw' a permalink, and make it clear on the rendered page, and hope people point their replies at the right place.
But if people do muddle the blog post and the (essentially) page-about-the-blog-post in their interactions with it, it probably doesn't matter; I can disambiguate them appropriately on my end. Maybe do some contextual reinterpretation experiments in the process (watch this space).
How do other people handle this? Well the people who are replying to each others' blog posts from their own sites are indieweb and they're not necessarily big on the linked data or pedantic arguments about what a URI 'means'. Todo: Find out if anyone has implemented a blog or similar with LDP.
Last modified:
So Slog'd got stuck for a little while because the fast, nice-looking, somewhat magical SPARQL endpoint provided by ARC2 stopped working for no discernable reason.
I thought I'd try leaving it alone for a few weeks to see if it started working again by itself, but alas, it has not.
Everything is fine until I try to query for a specific predicate. (Specific objects or subjects are fine). The query runs, it just returns no results. I know the data is in there, because I can get it out with less specific queries. Also because I can see it all in the MySQL database on which it is based. When I left it, it was working fine.
I'm going to kill the database and set it up again.
I did this by - and oh, it was joyous - going into the database settings and appending '2' to the name of the database. I then reloaded the endpoint page, and it set everything up by itself :)
I inserted two triples, and successfully queried for a specific prefix. So, it works. I wonder what will happen if I dump all my old data back in there? (I validated the raw file with all the triples in RDF/XML, and they're fine).
I inserted the rest the rest: LOAD <path/to/rdf.rdf> INTO <>
Ran a test query, aaaand... it's fine.
So what the hell was wrong with my other database? Perhaps I'll never know...
Dimly aware that ARC2's triplestore uses named graphs, I decided to check where all my triples are at the moment. Turns out any inserted from php scripts are inside a graph whose URI is the file path to the script, eg. <http://localhost/testclasses.php>.
Maybe I should think about more proactively sorting my graphs.
Last modified:
Right-ho, it parses whatever arbitrary metadata I put in the comments of the markdown files providing they start with "label:" and end with a newline (" ").
And lumps it into displayable html along with the post it belongs to, mostly for easier testing.
The next step is to engage some ontologies and turn the metadata and posts into a graph. It's ARC2 time!
Update: Actually the metadata it accepts is not all that arbitrary. Will remedy.
Update 2: Fixed that.
Last modified:
It's easy to see why not many people do. I say not many, because I'm sure there are people using the various RDF Drupal or Wordpress plugin. But I don't really know if they count, because that's really just people annotating their content for SEO purposes, and maybe a bit of interlinking with DBPedia to let visitors find out a bit more about topics of interest.
But what I'm really talking about is the whole blog running from a triplestore, with a publicly accessible SPARQL endpoint.
All the publicly accessible SPARQL endpoints I can find are big 'useful' datasets that people might want to mash up with other things. Archives of data. Not live or frequently updated stuff. Certainly not the contents and metadata of a personal blog.
So what's the point?
There's not a lot else 'on' the Semantic Web to tap into. There's no hidden Semantic Blogosphere that would yield great worth if I could only tap into it. There are no smart agents traversing the Semantic Web and aggregating interesting blog content for intelligent readers (are there?).
And there never will be, if nobody publishes their content this way.
So I suppose I'd better get on with it.
My point is, it's easy to see why nobody does.
Last modified:
I'm using Michel Fortin's PHP Markdown to grab each md file in the posts directory and convert the contents to HTML.
I'll add some custom stuff to parse labels and categories that I plan to use to organise my content.
I also need to think about templating, and when the to-triples part is going to happen.
Updates (16:48)
Last modified:
Gotta start somewhere. So here's a first post.
With Slog'd you will be able to:
Then when someone loads your blog:
I don't know how I'm going to do this yet, but I'll save my progress as I go...
Last modified: