As a first step, using DMOZ categories for dc:subject is very simple. In Movable Type, just place the dmoz URI (eg, http://dmoz.org/Computers/Internet/On_the_Web/Weblogs/ for blogging) as a category in your blog configuration.
dc:subject wants a Literal as a value, so the URI from dmoz will show up as a Literal. I believe the Semantic Blog Demonstrator has a more full schema for blogging. Once it starts to work again, I'll see how best to indicate a blog entry's subject in a more RDF friendly way (ie, make the DMOZ URI a Resource and not a Literal).
Just adding more semantic web friendly triples.
Tuesday, April 20, 2004
Saturday, April 17, 2004
A Trust Web Might Help
phil ringnalda dot com: TypeKey from a different angle
Phil Ringnalda writes:
Now, I'm not so sure that's the right angle to take. If instead of seeing TypeKey as a slightly more tolerable (because you only have to lie about your email address once instead of many times) way to implement registration, you look at it as way to implement comment moderation, it begins to look a tad bit better.
He's right about this. TypeKey alone won't stop any problems. We need authorization controls, which are above authentication. TypeKey is only a first step.
I am investigating using Semantic Web technologies to help with the authorization problem. There's a concept of building a trust web that can likely help here.
What's nice about putting all that raw information into the RSS is the aggregators can make their own assumptions. Isn't this what the semantic web is all about? Don't like how one aggregator's algorithm for trust is working? Upload your own OWL file, or use a different aggregator. The important part is that "who to trust" is decided at runtime.
As Phil points out in a blog post to me, the above is not the hard part. The hard part is getting everyone to put these types of tripes into their RSS feeds. It's a chicken and egg problem. No one will put the tripes in until they see a killer app. But it's hard to write a good killer app without all the triples to prove it's killer.
Phil Ringnalda writes:
Now, I'm not so sure that's the right angle to take. If instead of seeing TypeKey as a slightly more tolerable (because you only have to lie about your email address once instead of many times) way to implement registration, you look at it as way to implement comment moderation, it begins to look a tad bit better.
He's right about this. TypeKey alone won't stop any problems. We need authorization controls, which are above authentication. TypeKey is only a first step.
I am investigating using Semantic Web technologies to help with the authorization problem. There's a concept of building a trust web that can likely help here.
- Use a authenitcation service (TypeKey or PGP signatures) to prove Seth is Seth.
- Give Seth a URI. A foaf:mbox_sha1 might be good here.
- Put blog comment triples into RSS feeds. The aggregators can pick these up and start to collect where Seth has posted, when, etc.
- Some concepts of trust begin to form. For instance, if Seth has posted to many blogs, and those posts are old (haven't been deleted), then they might not be content spam. Also, RSS feeds can include any moderation points given to posts. The white lists and black lists created by blog authors can also easily be captured inside the RSS.
What's nice about putting all that raw information into the RSS is the aggregators can make their own assumptions. Isn't this what the semantic web is all about? Don't like how one aggregator's algorithm for trust is working? Upload your own OWL file, or use a different aggregator. The important part is that "who to trust" is decided at runtime.
As Phil points out in a blog post to me, the above is not the hard part. The hard part is getting everyone to put these types of tripes into their RSS feeds. It's a chicken and egg problem. No one will put the tripes in until they see a killer app. But it's hard to write a good killer app without all the triples to prove it's killer.
Friday, April 16, 2004
Slight Change to RSS Blog Comments Module
RSS 1.0 and 2.0 Blog Comments Module
The current blog comments module does not render as RDF. The current usage:
<blogcomments:comments>
need to become
<blogcomments:comments rdf:parseType="Collection">
I have made this change, and along with the MTEntryIfComments plugin, I now have validated RSS 1.0 as RDF!
Just doing my part to add more triples to the world.
Of course, now question remains, how best to promote these (and other) triples to other blog authors?
The current blog comments module does not render as RDF. The current usage:
<blogcomments:comments>
need to become
<blogcomments:comments rdf:parseType="Collection">
I have made this change, and along with the MTEntryIfComments plugin, I now have validated RSS 1.0 as RDF!
Just doing my part to add more triples to the world.
Of course, now question remains, how best to promote these (and other) triples to other blog authors?
Add Comment Triples To RSS
MT Extensions: MTEntryIfComments 2.0
MovableType has conditional tags that are true when entries and pings are enabled. The following tags allow you to test whether comments or pings exist.
MTEntryIfComments:
A conditional tag that is true if the current entry has one or more (or a specific number of) comments. Useful if you want to add content before/after a list of comments only if the list is not empty, or if you want to display different text based on the number of comments.
This is useful for rendering comment triples if they exist for a particular blog entry.
MovableType has conditional tags that are true when entries and pings are enabled. The following tags allow you to test whether comments or pings exist.
MTEntryIfComments:
A conditional tag that is true if the current entry has one or more (or a specific number of) comments. Useful if you want to add content before/after a list of comments only if the list is not empty, or if you want to display different text based on the number of comments.
This is useful for rendering comment triples if they exist for a particular blog entry.
Thursday, April 15, 2004
An External OWL Ontology Creates Order, Promotes Freedom
SemErgence: Comment on Subject metadata to Blog Posts
CaptSolo writes:
Regarding the hard part to make the UI for selecting categories - I think that most blog engines already have UI for entering the blog post categories.
Therefore, instead of adding semantic category to each post and having to create a new UI for that, we may add the semantic meta-information to the existing categories.
This is the route I initially travelled. I have a post that shows how to use OWL to map a blog post that has a particular dc:subject Literal to a OWL Class. For instance, declaring that posts that have a dc:subject of "blogging" are members of the :PostAboutBlogging class.
This leaves each blog owner the freedom to declare any dc:subject they want (literal or Resource) and to use an external OWL ontology to bring some order.
CaptSolo writes:
Regarding the hard part to make the UI for selecting categories - I think that most blog engines already have UI for entering the blog post categories.
Therefore, instead of adding semantic category to each post and having to create a new UI for that, we may add the semantic meta-information to the existing categories.
This is the route I initially travelled. I have a post that shows how to use OWL to map a blog post that has a particular dc:subject Literal to a OWL Class. For instance, declaring that posts that have a dc:subject of "blogging" are members of the :PostAboutBlogging class.
This leaves each blog owner the freedom to declare any dc:subject they want (literal or Resource) and to use an external OWL ontology to bring some order.
Add dc:references to RSS, Help The World
SemErgence: How To Make Blogging More SemWeb Friendly
Kasei writes:
While the dcterms:references might be easily obtainable from the HTML, I don't see any reason to make people parse the HTML over and over again, when it could easily be done once, and be immediately available as RDF. So here's a Movable Type plugin which does just that; just drop the tag into the RSS 1.0 template.
Thanks kansei! This is great. I'll add this in tonight.
If people do this, it'll make semweb applications that compile and operate on Resources that people are blogging about much easier. How does the semantic web community evangelize movements such as this? My guess would be to get the tool manufacturers to agree to modify their templates. Most blog owners wouldn't know how to manipulate their blog backend.
There is a Semantic Web Best Practices and Deployment Working Group from the W3. Maybe I'll talk to them about ideas for help.
Kasei writes:
While the dcterms:references might be easily obtainable from the HTML, I don't see any reason to make people parse the HTML over and over again, when it could easily be done once, and be immediately available as RDF. So here's a Movable Type plugin which does just that; just drop the tag into the RSS 1.0 template.
Thanks kansei! This is great. I'll add this in tonight.
If people do this, it'll make semweb applications that compile and operate on Resources that people are blogging about much easier. How does the semantic web community evangelize movements such as this? My guess would be to get the tool manufacturers to agree to modify their templates. Most blog owners wouldn't know how to manipulate their blog backend.
There is a Semantic Web Best Practices and Deployment Working Group from the W3. Maybe I'll talk to them about ideas for help.
Wednesday, April 14, 2004
Hacking MovableType, Here I Come
movabletype.org : FAQ
Q: May I modify the Movable Type source code?
A: Yes, as long as you do not redistribute the modified code without permission. In addition, if you modify any of the code and feel that your changes would be useful to all Movable Type users, we encourage you to make your work available to the community of users by sharing it on the independent plug-ins site, http://www.mt-plugins.org.
Looks like Six Apart doesn't mind too much if we hack Movable Type. Sounds good to me. I think we have enough ideas to keep us busy.
I think first up will be to include dmoz and/or yahoo category forests as selectable Categories. The modification of the RSS template to include the dmoz URI as a rdf:resource of dc:subject will be next. If I can do all that as a plugin, then all the better!
Oh, and I'm focusing on Movable Type because that seems to be pretty popular.
Q: May I modify the Movable Type source code?
A: Yes, as long as you do not redistribute the modified code without permission. In addition, if you modify any of the code and feel that your changes would be useful to all Movable Type users, we encourage you to make your work available to the community of users by sharing it on the independent plug-ins site, http://www.mt-plugins.org.
Looks like Six Apart doesn't mind too much if we hack Movable Type. Sounds good to me. I think we have enough ideas to keep us busy.
I think first up will be to include dmoz and/or yahoo category forests as selectable Categories. The modification of the RSS template to include the dmoz URI as a rdf:resource of dc:subject will be next. If I can do all that as a plugin, then all the better!
Oh, and I'm focusing on Movable Type because that seems to be pretty popular.
Subject metadata to Blog Posts
SemErgence: How To Make Blogging More SemWeb Friendly
Morten Frederiksen writes:
While it would certainly be nice, I think you'll find that the hardest part of (3) is agreeing on a taxonomy of subjects (or mapping between differing taxonomies). For this reason, something like dmoz:category or yahoo:index might be interesting.
I agree that it would be hard to map all that data. His suggestion of using dmoz and yahoo is great. The easiest thing would be to take any URIs found in the blog post (perhaps via dcterms:references?) and query for them in dmoz or yahoo. Of course, that would only be correct about 5% of the time.
It would be nice, then, to have Movable Type and other blog posting software, to give a quick tree view of dmoz and yahoo. A good blog posting software would save the favorite categories for quick retrieval (a sort of hot subjects collection).
I just upgraded to Movable Type 2.661. I don't believe it's Open Source, but wonder how much I can hack in?
Morten Frederiksen writes:
While it would certainly be nice, I think you'll find that the hardest part of (3) is agreeing on a taxonomy of subjects (or mapping between differing taxonomies). For this reason, something like dmoz:category or yahoo:index might be interesting.
I agree that it would be hard to map all that data. His suggestion of using dmoz and yahoo is great. The easiest thing would be to take any URIs found in the blog post (perhaps via dcterms:references?) and query for them in dmoz or yahoo. Of course, that would only be correct about 5% of the time.
It would be nice, then, to have Movable Type and other blog posting software, to give a quick tree view of dmoz and yahoo. A good blog posting software would save the favorite categories for quick retrieval (a sort of hot subjects collection).
I just upgraded to Movable Type 2.661. I don't believe it's Open Source, but wonder how much I can hack in?
OWL Shows Off
Re: Does Euler support owl:hasValue ? from Jos De_Roo on 2004-04-14 (www-rdf-logic@w3.org from April 2004)
I was very lucky to get help from Bejamin Nowack and Mr. Euler Jos De Roo. I asked the www-rdf-logic list about how to declare an object is a member of a owl:Class based on a Literal value of a Property. I was close, only backwards. The correct OWL would be something like:
Then, with a fact like the following (easily taken from some RSS):
I could tell:
I hope this at least illustrates my goal: to map different dc:subjects from different blogs into a locally understood set of owl:Classes. Then, provide a way to create Planet*.com sites with ad hoc aggregation based on queries given by users. And the first query: " Collect all blog entries that are of type XXX "
OWL is nice, and Euler is nice. Now, to plug them into the planetrdf.com code.
Thoughts or comments?
I was very lucky to get help from Bejamin Nowack and Mr. Euler Jos De Roo. I asked the www-rdf-logic list about how to declare an object is a member of a owl:Class based on a Literal value of a Property. I was close, only backwards. The correct OWL would be something like:
[ a owl:Restriction ; owl:onProperty dc:subject ; owl:hasValue "blogging"^^xsd:string ] rdfs:subClassOf :PostAboutBlogging .
:PostAboutBlogging a owl:Class .
dc:subject a owl:DatatypeProperty ; rdfs:range xsd:string .
Then, with a fact like the following (easily taken from some RSS):
:blogitem a owl:Thing ; dc:subject "blogging"^^xsd:string .
I could tell:
:blogitem a :PostAboutBlogging .
I hope this at least illustrates my goal: to map different dc:subjects from different blogs into a locally understood set of owl:Classes. Then, provide a way to create Planet*.com sites with ad hoc aggregation based on queries given by users. And the first query: " Collect all blog entries that are of type XXX "
OWL is nice, and Euler is nice. Now, to plug them into the planetrdf.com code.
Thoughts or comments?
How To Make Blogging More SemWeb Friendly
After thinking about this for a little while, and with the discussions on this blog, I offer some suggestions to make blogs more friendly and useful to the semantic web.
Thoughts or comments?
- Put triples describing comments and comment authors inside RSS - This would help with the comment spam problem and start to build a web of trust wrt posting to blogs. Movable Type's TypeKey system solves the authentication problem. By finding triples of the blog comments, I feel we can help with the second level to the problem: authorization.
- RSS feeds should populate dc:references with URIs used in blog entry body - Typically, blog entries include one or more URIs in the body of the entry. By making those URIs explicitly available via triples inside the RSS, more accurate and interesting information becomes available. Specifically, the question of "What are people blogging about?" becomes easier to answer.
- Encourage Blog authors to include dc:subject, and help define what might go in there - By starting to label blog entries with information on their subject (what the entry might be about), ad hoc planet* sites can be built. These planet* sites scan all the RSS looking for entries about particular subject matters and aggregate the entries. For this to work, there would be a way for an aggregator to declare a mapping between the values of dc:subject found in the wild, and the recognized values of the aggregator (OWL helps here a lot).
Thoughts or comments?
Tuesday, April 13, 2004
RDF Should Make This Easy
Peter Van Dijck's Guide to Ease:
Peter, along with Danny, likes PlanetRDF the way it is. I completely respect that, and just try to point out that if implemented correctly, then the filtering using semweb technologies that I'm proposing would allow everyone to have their blogrolls just the way they like.
Each person would be able to create a personal PlanetRDF by declaring which dc:subject's they are interested in reading about. This allows for smarter Planet* because, as PlantRDF has shown, blogs cover many different topics.
If XFML is a way to accomplish this, then certainly RDF and OWL would, too! And thanks to help on #rdfig, I think I have the OWL statements to accomplish this. More soon.
Peter, along with Danny, likes PlanetRDF the way it is. I completely respect that, and just try to point out that if implemented correctly, then the filtering using semweb technologies that I'm proposing would allow everyone to have their blogrolls just the way they like.
Each person would be able to create a personal PlanetRDF by declaring which dc:subject's they are interested in reading about. This allows for smarter Planet* because, as PlantRDF has shown, blogs cover many different topics.
If XFML is a way to accomplish this, then certainly RDF and OWL would, too! And thanks to help on #rdfig, I think I have the OWL statements to accomplish this. More soon.
It’s more ’sucks’ as in ‘wanted to grab attention’ and ‘could be better’
Raw: I don't think it 'sucks' as in 'blows goats'...
Thanks to Danny Ayers for chiming in. I agree that some of the appeal of Planet RDF is the semi-randomness of the entries. I was trying to bring awareness up for the fact that we have these nice semweb technologies, and a planetrdf.com, let's see if we can make them work to our advantage. Danny's filtering would be loose, while my filter would be strict.
Danny also mentioned an RDF Thesaurus, which definitely be better than string matching.
Though, if dc:subject can have an rdfs:range of rdf:Resource, I think we get more sem webbiness out of it.
Maybe I'll check out the planetrdf.com code? (sorry, couldn't find a URI for the code)
Thanks to Danny Ayers for chiming in. I agree that some of the appeal of Planet RDF is the semi-randomness of the entries. I was trying to bring awareness up for the fact that we have these nice semweb technologies, and a planetrdf.com, let's see if we can make them work to our advantage. Danny's filtering would be loose, while my filter would be strict.
Danny also mentioned an RDF Thesaurus, which definitely be better than string matching.
Though, if dc:subject can have an rdfs:range of rdf:Resource, I think we get more sem webbiness out of it.
Maybe I'll check out the planetrdf.com code? (sorry, couldn't find a URI for the code)
What Sucks About PlanetRDF.org
First off, let me mention that I think the idea of PlanetRDF.com is great, and I find it a very valuable resource.
My problem with planetrdf.com is that it syndicates all posts from blogs it has chosen, instead of those posts that deal only with RDF and the semweb. For instance, planetrdf.com might show posts on RDF and someone's new car. While I might be interested in that new car (especially if it's a Mini), I would like planetrdf.com to filter out items that do not have anything to do with the semweb or RDF. For a site that is all about RDF, I think we have all the tools necessary.
It should be straightforward for planetrdf.com to say, "This item (blog post) has something to do with one of the categories I syndicate. Let's show it.". Also, it should be just as easy to say "This item is from a category that I do not syndicate, so I'll silently drop it".
In RSS 1.0 (RDF) there should be a triple to indicate an item's category. From the implementations I've seen, the Object in this triple is a Literal (string). For instance, here is a triple you might get from a RSS 1.0 feed:
The most simple thing to do here is to create a list of approved Literal values of categories. The planetrdf.com aggregator would simply check the string values of the dc:subject.
Now, of course, we are using Semantic Web technologies, so we can do a bit better. The property dc:subject doesn't specify a rdfs:range. I'm not sure exactly what this means, but I'm hoping it means we could place a Resource as the Object of that triple.
For instance, the above triple could change to:
Then, using OWL, we can provide mappings between Resources that planetrdf.com is interested in (such as http://www.w3.org/RDF for RDF) and dc:subject Resources defined by blog owners. This allows for the dc:subject ontology to be defined by blog owners. Using OWL's owl:sameAs
planetrdf.com (or even the blog owner) could compile mappings between the two ontologies.
Anyway, I hope this generates some discussion or action. It seems like we have the pieces needed to use semweb technologies to make planetrdf.com much smarter. Do others think this is possible?
Also, is it possible to create mappings with OWL based on Literals (for instance, saying that "Blogging" owl:sameAs "blogging")?
My problem with planetrdf.com is that it syndicates all posts from blogs it has chosen, instead of those posts that deal only with RDF and the semweb. For instance, planetrdf.com might show posts on RDF and someone's new car. While I might be interested in that new car (especially if it's a Mini), I would like planetrdf.com to filter out items that do not have anything to do with the semweb or RDF. For a site that is all about RDF, I think we have all the tools necessary.
It should be straightforward for planetrdf.com to say, "This item (blog post) has something to do with one of the categories I syndicate. Let's show it.". Also, it should be just as easy to say "This item is from a category that I do not syndicate, so I'll silently drop it".
In RSS 1.0 (RDF) there should be a triple to indicate an item's category. From the implementations I've seen, the Object in this triple is a Literal (string). For instance, here is a triple you might get from a RSS 1.0 feed:
urn:example:blogitem:xxx dc:subject "Blogging" .
The most simple thing to do here is to create a list of approved Literal values of categories. The planetrdf.com aggregator would simply check the string values of the dc:subject.
Now, of course, we are using Semantic Web technologies, so we can do a bit better. The property dc:subject doesn't specify a rdfs:range. I'm not sure exactly what this means, but I'm hoping it means we could place a Resource as the Object of that triple.
For instance, the above triple could change to:
urn:example:blogitem:xxx dc:subject category:blogging .
Then, using OWL, we can provide mappings between Resources that planetrdf.com is interested in (such as http://www.w3.org/RDF for RDF) and dc:subject Resources defined by blog owners. This allows for the dc:subject ontology to be defined by blog owners. Using OWL's owl:sameAs
planetrdf.com (or even the blog owner) could compile mappings between the two ontologies.
Anyway, I hope this generates some discussion or action. It seems like we have the pieces needed to use semweb technologies to make planetrdf.com much smarter. Do others think this is possible?
Also, is it possible to create mappings with OWL based on Literals (for instance, saying that "Blogging" owl:sameAs "blogging")?
Monday, April 12, 2004
Testing Comments in RSS
I found a Blog Comments Module for RSS, so I've hacked it into my Movable Type's index.rdf generation. My index.rdf is still RSS 1.0 (RDF).
First, I put this block in my template:
Next up, I will add a smidge of OWL to say that a
Then, the next simple step is to get everyone in the world doing this! Remember, if you add this into your index.rdf for your blog, then trust web authorization services can be built. If you assume that those that comment spam is deleted, the mere fact that posts exist out on the web by an authenticated user must be a good sign.
While the world is updating their blogs to include these new triples, and gearing up for TypeKey, the semweb community can start building the authorization service.
First, I put this block in my template:
<blogcomments:comments>
<MTComments>
<blogcomments:comment>
<blogcomments:name><$MTCommentAuthor></blogcomments:name>
<blogcomments:email
rdf:resource="mailto:<$MTCommentEmail spam_protect="0"$>"/>
<blogcomments:ip><$MTCommentIP></blogcomments:ip>
<blogcomments:date><$MTCommentDate></blogcomments:date>
<blogcomments:body>
<![CDATA[<$MTCommentBody convert_breaks="0"$>]]>
</blogcomments:body>
</blogcomments:comment>
</MTComments>
</blogcomments:comments>
Next up, I will add a smidge of OWL to say that a
blogcomments:email is the sameAs foaf:mbox.Then, the next simple step is to get everyone in the world doing this! Remember, if you add this into your index.rdf for your blog, then trust web authorization services can be built. If you assume that those that comment spam is deleted, the mere fact that posts exist out on the web by an authenticated user must be a good sign.
While the world is updating their blogs to include these new triples, and gearing up for TypeKey, the semweb community can start building the authorization service.
So Much For The P in PURL
IIR, the P in PURL.ORG stands for permanent. Well, tonight I couldn't resolve it (for whatever reason). DOH!
Fighting Comment Spam
My Movable Type install is now fighting comment spam with mt-blacklist.
This would be great if it reported spam hits in real time via XML-RPC to a central server. And, of course, if this plugin could then pull that list or check it in real time, all the better! This is a great use for P2P, or at least, automated collection and retrieval of information.
This would be great if it reported spam hits in real time via XML-RPC to a central server. And, of course, if this plugin could then pull that list or check it in real time, all the better! This is a great use for P2P, or at least, automated collection and retrieval of information.
TypeKey and the Trust Web
After browsing Movable Type, I read that they have created TypeKey. TypeKey is, from the looks of it, a single sign on for blogs.
TypeKey primarily has been created to fight comment spam appearing in blogs.
I ponder how the semweb could help with this problem. There has been an effort to generate a trust web using semantic web technologies. Can this web be used to help fight comment spam?
My guess, though untested, would be yes. If blog owners require sign in before posting a comment, then an identity is collected. My blog system can then query the semantic web and get a trust metric for the ID.
TypeKey only provides authentication services. It leaves authorization up to the blog backend. This is a wise choice, and it leaves open an implementation for authorization based on the semweb's trust web.
I can see a authorization system based on the trust web, where users have certain trust metrics for posting to blogs. Note that a blog posting trust metric would be different than a "take care of my grandma" trust metric, so there must be a distinction there.
As users, once authenticated, post to blogs without generating (subjectively measured) negative feedback, their intrinsic trust metric increases. For instance, if a user that has posted 10000 posts across the web with no spam, then that user can relatively be trusted to post to your blog without harm.
How would an authorization agent know the blog posting trust metric of an authenticated user? Possibly by querying a trustkey authorization service. It could assign a blog posting trust metric and send it back to the blog backend.
It would be interesting to investigate if the information of "User X has posted a non-harmful blog comment" from the web. RSS feeds, to my knowledge, do not include the comments (though nothing technical would stop this from happening). So getting this information as triples would be more difficult than merely harvesting statements from the semweb.
It sounds good, and an interesting application of the trust web. Can this be built? More importantly, would people use it?
TypeKey primarily has been created to fight comment spam appearing in blogs.
I ponder how the semweb could help with this problem. There has been an effort to generate a trust web using semantic web technologies. Can this web be used to help fight comment spam?
My guess, though untested, would be yes. If blog owners require sign in before posting a comment, then an identity is collected. My blog system can then query the semantic web and get a trust metric for the ID.
TypeKey only provides authentication services. It leaves authorization up to the blog backend. This is a wise choice, and it leaves open an implementation for authorization based on the semweb's trust web.
I can see a authorization system based on the trust web, where users have certain trust metrics for posting to blogs. Note that a blog posting trust metric would be different than a "take care of my grandma" trust metric, so there must be a distinction there.
As users, once authenticated, post to blogs without generating (subjectively measured) negative feedback, their intrinsic trust metric increases. For instance, if a user that has posted 10000 posts across the web with no spam, then that user can relatively be trusted to post to your blog without harm.
How would an authorization agent know the blog posting trust metric of an authenticated user? Possibly by querying a trustkey authorization service. It could assign a blog posting trust metric and send it back to the blog backend.
It would be interesting to investigate if the information of "User X has posted a non-harmful blog comment" from the web. RSS feeds, to my knowledge, do not include the comments (though nothing technical would stop this from happening). So getting this information as triples would be more difficult than merely harvesting statements from the semweb.
It sounds good, and an interesting application of the trust web. Can this be built? More importantly, would people use it?
Subscribe to:
Posts (Atom)
Disclaimer
