Plingback
From Plings Info
Contents |
PlingBack
PlingBack is about collecting feedback and additional information attached to Places to Go, and Things to Do.
As of 18th April 2010 PlingBack tools are under active development.
The following notes aim to document aspects of that development.
What is PlingBack
PlingBack could be:
- A comment or rating of a particular activitiy;
- Web metrics showing how often a particular activity has been viewed online;
- Numbers showing how many people attended or planned to attend at event;
- The identification of demand for a given activity or activity type;
- Additional information from a third-party about an activity, such as a web-link; a photo; or a video.
- An assertion about the general relationship of one activity to another (e.g. this activity is preferred over this one).
PlingBack can be collected and expressed in many different ways. However, we are primarily interested in collecting it as RDF statements stored on the Talis platform
PlingBack Structure
PlingBack consist of a number of statements about a PlingBack blank node. (The talis platform provides a unique URI for Blank Nodes when they are posted to it).
We propose that PlingBack uses elements of the following ontologies:
It also invents a new ontology.
- PB: http://plingback.plings.net/ontologies/plingback# (N.B. This is not yet confirmed. Use with caution!)
The following is a draft schema under development. Please suggest modifications via the discussion page
A subject
Usually a Plings activity, expressed through the <rdf:about> relationship.
__PlingBack <rdf:about> <http://plings.net/a/1234>
However, PlingBack could also be about:
- A place
- A local area
- Any other entity in the Plings data store;
An application
The PlingBack application which is providing the data.
__PlingBack <pb:plingBackType> <http://plingback.plings.net/applications/sms_tool>
The Plingback application can, optionally, specify its version.
__PlingBack <pb:plingBackVersion> "0.1"
A respondent/reviewer
Specified using the commenter predicate from Review ontology which can either identify an individual specified using FOAF, or can point to a unique ID of an anonymised user.
__PlingBack <REVIEW:commenter> <__Commenter>
A maximal set of information about an individual might include:
- Age
- Gender
- Location
- Ethnicity
- Disability
- Disadvantage
- Contact details
However, this demographic and personally identifying information should never be stored in a public data store.
An anonymised way of storing this information is required.
Rupert's Python Code
http://bluwiki.com/go/Plingback#Talis_Platform_Stores
Pling-u-like RDF
Rob Styles from Talis kindly formated this for us to optimise for consumption.
in RDF XML
<?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:pul="http://pling-u-like.com/schema/"> <pul:Visitor rdf:about="http://pling-u-like.com/visitors/2147483647"> <foaf:based_near rdf:resource="http://pling-u-like.com/locations/Birmingham"/> </pul:Visitor> <pul:Location rdf:about="http://pling-u-like.com/locations/Birmingham"> <geo:lat>1111.111</geo:lat> <geo:long>2222.222</geo:long> </pul:Location> <pul:Choice rdf:about="http://pling-u-like.com/visitors/2147483647/choices#1"> <pul:visitor rdf:resource="http://pling-u-like.com/visitors/2147483647"/> <pul:option rdf:resource="http://plings.net/a/16"/> <pul:option rdf:resource="http://plings.net/a/24"/> <pul:choice rdf:resource="http://plings.net/a/16"/> <pul:choice_position rdf:resource="http://pling-u-like.com/schema/left"/> </pul:Choice> <pul:Choice rdf:about="http://pling-u-like.com/visitors/2147483647/choices#2"> <pul:visitor rdf:resource="http://pling-u-like.com/visitors/2147483647"/> <pul:option rdf:resource="http://plings.net/a/18"/> <pul:option rdf:resource="http://plings.net/a/30"/> <pul:choice rdf:resource="http://plings.net/a/30"/> <pul:choice_position rdf:resource="http://pling-u-like.com/schema/left"/> </pul:Choice> <pul:Choice rdf:about="http://pling-u-like.com/visitors/2147483647/choices#3"> <pul:visitor rdf:resource="http://pling-u-like.com/visitors/2147483647"/> <pul:option rdf:resource="http://plings.net/a/17"/> <pul:option rdf:resource="http://plings.net/a/22"/> <pul:choice rdf:resource="http://plings.net/a/22"/> <pul:choice_position rdf:resource="http://pling-u-like.com/schema/left"/> </pul:Choice> </rdf:RDF>
In Turtle:-
@base <http://foo> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> . @prefix pul: <http://pling-u-like.com/schema/> . <http://pling-u-like.com/locations/Birmingham> a pul:Location ; geo:lat "1111.111" ; geo:long "2222.222" . <http://pling-u-like.com/visitors/2147483647> a pul:Visitor ; foaf:based_near <http://pling-u-like.com/locations/Birmingham> . <http://pling-u-like.com/visitors/2147483647/choices#1> pul:choice <http://plings.net/a/16> ; pul:choice_position pul:left ; pul:option <http://plings.net/a/16>, <http://plings.net/a/24> ; pul:visitor <http://pling-u-like.com/visitors/2147483647> ; a pul:Choice . <http://pling-u-like.com/visitors/2147483647/choices#2> pul:choice <http://plings.net/a/30> ; pul:choice_position pul:left ; pul:option <http://plings.net/a/18>, <http://plings.net/a/30> ; pul:visitor <http://pling-u-like.com/visitors/2147483647> ; a pul:Choice . <http://pling-u-like.com/visitors/2147483647/choices#3> pul:choice <http://plings.net/a/22> ; pul:choice_position pul:left ; pul:option <http://plings.net/a/17>, <http://plings.net/a/22> ; pul:visitor <http://pling-u-like.com/visitors/2147483647> ; a pul:Choice .

