W3C home > Mailing lists > Public > www-webont-wg@w3.org > November 2001

homework: using WebOnt for organizational stuff

From: Dan Connolly <connolly@w3.org>
Date: Mon, 26 Nov 2001 16:01:14 -0600
Message-ID: <3C02BBAA.33FA9F1D@w3.org>
To: www-webont-wg@w3.org
I intend to use this ontology language for organizational stuff.

For example, in an attempt to figure out goegraphic
concentrations of WG members for ftf meeting planning
purposes, I'm joining data you guys gave me about
nearby airports with latitude/longitude data found elsewhere.

(in progress; see
  http://www.w3.org/2001/sw/WebOnt/Makefile
  http://www.w3.org/2001/sw/WebOnt/webont-airports.rdf )

I can do some of that with plain old RDF, but only
if everybody uses full URIs to talk about common concepts;
a critical feature of an ontology language is
the UniqueProperty/UnambiguousProperty/cardinality
stuff that allows me to say "*the* airport
whose IATA code is 'MCI'" which makes the joins possible.

I'm also using this stuff to check the consistency
between the three different sources of info
about WG membership:
	-- the nominations by email
		(I have a perl script that converts these to RDF)
	-- the WG home page
		(I scrape this from XHTML to RDF using XSLT)
	-- a mailing list subscription database
		(I plan to have the database export RDF; haven't
		done it just yet)

I have rules ala "if somebody's been nominated, but they're
not on the WG home page, they're in the class MissingFromHomePage".

This sort of scenario relies on level-breaking stuff
(specifically, log:resolvesTo and log:uri
in http://www.w3.org/2000/10/swap/log
  http://www.w3.org/2000/10/swap/log.rdf
  http://www.w3.org/2000/10/swap/log.n3 )
that I don't expect will be standardized at the ontology
level, but it also makes use of uniquely identifying
properties ala "*the* person/party whose mailbox
is mailto:connolly@w3.org".

More generally, see:

  Schedule Coordination and Dependency Tracking
  in
  Semantic Web Activity: Advanced Development
  http://www.w3.org/2000/01/sw/#L2888



I think I have use cases that motivate oneOf,
onProperty/hasValue, and a few others from DAML+OIL.
More on those separately, I hope...

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 26 November 2001 17:01:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:46 GMT