Lab: RDFS - Revision history

Sinoa at 13:18, 2 April 2024

2024-04-02T13:18:18Z

← Older revision		Revision as of 13:18, 2 April 2024
Line 29:		Line 29:
	* When one thing that is charged with another thing,		* When one thing that is charged with another thing,
	** the first thing is a person under investigation and		** the first thing is a person under investigation and
	** the second thing is an ~~offense~~.		** the second thing is an offence.

	To add triples, you can use either:		To add triples, you can use either:
Line 73:		Line 73:
	* Paul Manafort was convicted for tax evasion.		* Paul Manafort was convicted for tax evasion.

	Use RDFS terms to add these rules as triples:		Use RDFS terms to add these rules as triples:
	* When one thing is ''convicted for'' another thing,		* When one thing is ''convicted for'' another thing,
	** the first thing is also ''charged with'' the second thing.		** the first thing is also ''charged with'' the second thing.
Line 85:		Line 85:
	'''Task:'''		'''Task:'''
	* Create a Turtle file with all the RDF and RDFS triples from the earlier tasks.		* Create a Turtle file with all the RDF and RDFS triples from the earlier tasks.
	* ~~Go to a local or online Blazegraph. Create~~ a new ~~Blazegraph namespace and~~ ''~~Use~~'' ~~it. (Remember that namespaces in Blazegraph~~ and ~~rdflib have nothing to do with one another~~.)		* Fire up GraphDB and create a new GraphDB Repository, ''this time with RDFS Ruleset'' for Inference and Validation.
	* ~~Go to~~ the ~~''Upload'' tab to add~~ the ~~triples into your new Blazegraph namespace.~~		* Load the graph from the Turtle file and go through each of the above queries to confirm that GraphDB has performed RDFS reasoning as you would expect.
	* Go through each of the above queries to confirm that ~~Blazegraph~~ has ~~not~~ performed ~~any~~ RDFS reasoning.

	You can ~~also~~ list all the triples in the ~~namespace~~ to ~~ensure that nothing~~ has been added:		You can list all the triples in the graph to see if anything has been added:
	SELECT * WHERE { ?s ?p ?o }		SELECT * WHERE { ?s ?p ?o }

	'''Task:'''		'''Task:'''
	* Create another ~~Blazegraph namespace~~, but ~~this time~~ ''~~with the~~ inference ~~box checked''. ''Use~~'' ~~the new namespace~~.		* Create another GraphDB Repository, but with ''No inference''.
	* ~~List all~~ the ~~triples in~~ the ~~new inferencing namespace. (What you see are the axioms in~~ RDFS~~.) How many are there?~~		* Re-run the above tests and compare with the RDFS inference results.
	* Upload the triples into your new inferencing Blazegraph namespace.
	* List all the triples again. How many have been added?
	* Go through each of the above queries to ensure that Blazegraph (with inference~~) has reasoned as you expect~~.

Rbo027 at 12:14, 15 March 2023

2023-03-15T12:14:22Z

← Older revision		Revision as of 12:14, 15 March 2023
Line 8:		Line 8:
	* RDF (RDF.type)		* RDF (RDF.type)
	* RDFS (RDFS.domain, RDFS.range, RDFS.subClassOf, RDFS.subPropertyOf)		* RDFS (RDFS.domain, RDFS.range, RDFS.subClassOf, RDFS.subPropertyOf)
			* [https://docs.google.com/presentation/d/13fkzg7eM2pnKGqYlKpPMFIJwnOLKBkbT0A62s7OcnOs Lab Presentation of RDFS]

	OWL-RL:		OWL-RL:

Sinoa: /* Tasks */

2023-03-08T12:25:17Z

Tasks

← Older revision		Revision as of 12:25, 8 March 2023
Line 59:		Line 59:

	You can compute the RDFS closure on a graph ''g'' like this:		You can compute the RDFS closure on a graph ''g'' like this:
	~~engine =~~ owlrl~~.RDFSClosure.RDFS_Semantics(g, False, False, False)~~		import owlrl
	~~engine~~.~~closure~~()
	~~engine~~.~~flush_stored_triples~~()		owlrl.DeductiveClosure(owlrl.RDFS_Semantics).expand(g)

	'''Task:'''		'''Task:'''

Sinoa: /* If you have more time... */

2023-02-18T17:27:15Z

If you have more time...

← Older revision		Revision as of 17:27, 18 February 2023
Line 83:		Line 83:
	==If you have more time...==		==If you have more time...==
	'''Task:'''		'''Task:'''
	Create a Turtle file with all the RDF and RDFS triples from the earlier tasks. Go to a local or online Blazegraph ~~and create~~ a new Blazegraph namespace ~~''with the inference box checked''.~~ ''Use'' ~~the new namespace~~. (Remember that namespaces in Blazegraph and rdflib have nothing to do with one another.) Upload the triples into Blazegraph.		* Create a Turtle file with all the RDF and RDFS triples from the earlier tasks.
			* Go to a local or online Blazegraph. Create a new Blazegraph namespace and ''Use'' it. (Remember that namespaces in Blazegraph and rdflib have nothing to do with one another.)
			* Go to the ''Upload'' tab to add the triples into your new Blazegraph namespace.
			* Go through each of the above queries to confirm that Blazegraph has not performed any RDFS reasoning.

	Go through each of the above queries to ensure that Blazegraph (with inference) has reasoned as you expect.		You can also list all the triples in the namespace to ensure that nothing has been added:
			SELECT * WHERE { ?s ?p ?o }

			'''Task:'''
			* Create another Blazegraph namespace, but this time ''with the inference box checked''. ''Use'' the new namespace.
			* List all the triples in the new inferencing namespace. (What you see are the axioms in RDFS.) How many are there?
			* Upload the triples into your new inferencing Blazegraph namespace.
			* List all the triples again. How many have been added?
			* Go through each of the above queries to ensure that Blazegraph (with inference) has reasoned as you expect.

Sinoa: /* If you have more time... */

2023-02-18T17:06:13Z

If you have more time...

← Older revision		Revision as of 17:06, 18 February 2023
Line 82:		Line 82:

	==If you have more time...==		==If you have more time...==
			'''Task:'''
			Create a Turtle file with all the RDF and RDFS triples from the earlier tasks. Go to a local or online Blazegraph and create a new Blazegraph namespace ''with the inference box checked''. ''Use'' the new namespace. (Remember that namespaces in Blazegraph and rdflib have nothing to do with one another.) Upload the triples into Blazegraph.

			Go through each of the above queries to ensure that Blazegraph (with inference) has reasoned as you expect.

Sinoa: /* Tasks */

2023-02-18T16:42:50Z

Tasks

← Older revision		Revision as of 16:42, 18 February 2023
Line 56:		Line 56:
	* Write a similar SPARQL query that checks the RDF type(s) of money laundering in your RDF graph.		* Write a similar SPARQL query that checks the RDF type(s) of money laundering in your RDF graph.
	* Write a small function that computes the ''RDFS closure'' on your graph.		* Write a small function that computes the ''RDFS closure'' on your graph.
	* Re-run the SPARQL queries to check the types of Rick Gates and of money laundering again.		* Re-run the SPARQL queries to check the types of Rick Gates and of money laundering again: have they changed?

	You can compute the RDFS closure on a graph ''g'' like this:		You can compute the RDFS closure on a graph ''g'' like this:
Line 66:		Line 66:
	Use RDFS terms to add this rule as a triple:		Use RDFS terms to add this rule as a triple:
	* A person under investigation is a FOAF person.		* A person under investigation is a FOAF person.
	* Like earlier, check the RDF types of Rick Gates before and after running RDFS reasoning.		* Like earlier, check the RDF types of Rick Gates before and after running RDFS reasoning. Do they change?

	'''Task:'''		'''Task:'''

Sinoa: /* Tasks */

2023-02-18T16:41:30Z

Tasks

← Older revision		Revision as of 16:41, 18 February 2023
Line 55:		Line 55:
	* Write a SPARQL query that checks the RDF type(s) of Rick Gates in your RDF graph.		* Write a SPARQL query that checks the RDF type(s) of Rick Gates in your RDF graph.
	* Write a similar SPARQL query that checks the RDF type(s) of money laundering in your RDF graph.		* Write a similar SPARQL query that checks the RDF type(s) of money laundering in your RDF graph.
	* Write a small function that ''~~computes the~~ RDFS closure'' on your graph.		* Write a small function that computes the ''RDFS closure'' on your graph.
	* Re-run the SPARQL queries to check the types of Rick Gates and of money laundering again.		* Re-run the SPARQL queries to check the types of Rick Gates and of money laundering again.

	You can compute the RDFS closure on a graph like this:		You can compute the RDFS closure on a graph ''g'' like this:
	engine = owlrl.RDFSClosure.RDFS_Semantics(g, False, False, False)		engine = owlrl.RDFSClosure.RDFS_Semantics(g, False, False, False)
	engine.closure()		engine.closure()
Line 64:		Line 64:

	'''Task:'''		'''Task:'''
	Use RDFS to add this rule as a triple:		Use RDFS terms to add this rule as a triple:
	* A person under investigation is a FOAF person.		* A person under investigation is a FOAF person.
	* Like earlier, check the RDF types of Rick Gates before and after running RDFS reasoning.		* Like earlier, check the RDF types of Rick Gates before and after running RDFS reasoning.
Line 72:		Line 72:
	* Paul Manafort was convicted for tax evasion.		* Paul Manafort was convicted for tax evasion.

	Use RDFS to add these rules as triples:		Use RDFS terms to add these rules as triples:
	* When one thing is ''convicted for'' another thing,		* When one thing is ''convicted for'' another thing,
	** the first thing is also ''charged with'' the second thing.		** the first thing is also ''charged with'' the second thing.

Sinoa: /* Tasks */

2023-02-18T16:40:24Z

Tasks

← Older revision		Revision as of 16:40, 18 February 2023
Line 19:		Line 19:
	'''Task:'''		'''Task:'''
	Install OWL-RL into your virtual environment:		Install OWL-RL into your virtual environment:
	pip install owlrl.		pip install owlrl

	'''Task:'''		'''Task:'''
Line 47:		Line 47:

	INSERT DATA {		INSERT DATA {
	# ~~your SPARQL update goes~~ here		# the triples you want to add go here,
			# you can use the prefixes defined in the NS-dict
	}		}
	""", initNs=NS)		""", initNs=NS)

Sinoa: /* Tasks */

2023-02-18T16:39:04Z

Tasks

← Older revision		Revision as of 16:39, 18 February 2023
Line 45:		Line 45:
	# when you provide an initNs-argument, you do not have		# when you provide an initNs-argument, you do not have
	# to define PREFIX-es as part of the update (or query)		# to define PREFIX-es as part of the update (or query)

	INSERT DATA {		INSERT DATA {
	# your SPARQL update goes here		# your SPARQL update goes here

Sinoa: /* Tasks */

2023-02-18T16:38:26Z

Tasks

← Older revision		Revision as of 16:38, 18 February 2023
Line 22:		Line 22:

	'''Task:'''		'''Task:'''
	We will use simple RDF statements from the Mueller investigation RDF graph you create in Exercise 1.		We will use simple RDF statements from the Mueller investigation RDF graph you create in Exercise 1. Create a new rdflib graph and add triples to represent that:

	Create a new rdflib graph and add ~~in "plain RDF" like you did in Exercise 1~~:
	* Rick Gates was charged with money laundering and tax evasion.		* Rick Gates was charged with money laundering and tax evasion.

	Use RDFS to add these rules as triples:		Use RDFS terms to add these rules as triples:
	* When one thing that is charged with another thing,		* When one thing that is charged with another thing,
	** the first thing is a person under investigation and		** the first thing is a person under investigation and
	** the second thing is an offense.		** the second thing is an offense.

	~~You can~~ add triples ~~using~~ simple ''~~rdflib~~.add((s, p, o))'' or ~~using~~ ''INSERT DATA {...}'' SPARQL updates. If you use SPARQL updates, you can define a namespace dictionary like this:		To add triples, you can use either:
			* simple ''graph.add((s, p, o))'' statements or
			* ''INSERT DATA {...}'' SPARQL updates.
			If you use SPARQL updates, you can define a namespace dictionary like this:
	EX = Namespace('http://example.org#')		EX = Namespace('http://example.org#')
	NS = {		NS = {
Line 44:		Line 45:
	# when you provide an initNs-argument, you do not have		# when you provide an initNs-argument, you do not have
	# to define PREFIX-es as part of the update (or query)		# to define PREFIX-es as part of the update (or query)

	INSERT DATA {		INSERT DATA {
	# your SPARQL update goes here		# your SPARQL update goes here