N3 Files

This directory contains a small percentage of the Notation3 files that I have worked on; just for interest.

A string test, composed just before I did the string built-in extensions
This was a wonderful little summary of the different kinds of equivalence you get from the different kinds of properties in Notation3, inspired by a question on #rdfig
This is the Notation3 that has appeared in my signature for quite a while now
This is an NTriples (a fixed subset of Notation3) test for an NTriples parser that I was writing in Python
This was a bit of EARL that I drafted up for nick, based on the SP output that his validator gives. One of the noticable things of this document is how it apparently differs from the texture of the normal Notation3 documents that I write, although it seems to comply fairly strictly to my Notation3 Style Guide
A little FOAF description of myself, requiring no more than the terms required in the FOAF namespace. Note that this uses a bNode for myself, which is something I don't often like to do - I'd much rather prefer people to use one of the numerous URI-views for me
An experiment for concating a URI, inspired by one of Aaron's joke ramblings
A test of the DOI (Digital Object Identifier) scheme, showing how such things could be structured
I used an XML RDF version of this in a publication... just a simple little bit of Notation3 as a demonstration
This was an interesting little test for the HuML project (which I later quit). It involves using the machinery of Notation3 to put some abstract project into practise., involving a heating mechanism and so forth
Here is the result of the OR experiment above. Let's just say that it didn't work, and never speak of it again
An early "OR" (logical or) experiment. TimBL said later that he's approach it using an OR class as a sub class of DAML List, and even provided a possible filter for it. This particular OR experiment was inspired by the Semantic Web Toolbox, which is now actually quite out-of-date
A test of the log:resolvesTo function, making sure that CWM is truly no longer a closed world machine. Theoretically, is there much that needs to be added to CWM? What exactly are we waiting to happen on the Semantic Web? I think that we're waiting for data, and stronger applications... but it does seem as if CWM should be a powerful enough engine to give us what we want
A set of inference terms that I developed. These were intended as terms to link terms to each other through schemata and other vocabulary control forms... but they weer quite weak terms; i.e. they had fairly descriptive semantics, and we really need strong terms on the Semantic Web. Of course, these terms are probably alright for things such as documentation
Calendar stuff. This one filters out dats of the week, and ranks them by period. It doesn't seem to have been the start of any serious project, and may have been inspired by something other than Libby's calendar stuff - checking through #rdfig logs of the time might yield further information
Boomarks in Notation3. This was the beginning of a great idea, and I think that I managed to get the bookmarks automatically generated by a CGI... but like so many projects, it just sits on the shelf. It probably would have been difficult to hook it up with the real world applications that I use for bookmarks anyway, so it probably belongs on the to-do shelf
A utility schema. It is very difficult to decide on hash vs. slash, so we kinda binned the idea, and I'm going with SWN instad
Trying to get log:startsWith to work. Of course, the problem was that the term is actually in the string namespace as string:startsWith
A funny little filter concerning the number of Simpsons episodes that I watch per day. Note that the distribution of episodes per day is not necessarily fixed, so the filter is not true for all time (which it should be, but due to contextualization, doesn't matter)
This is another example of a DOM TS result for Curt Arnold et al., this time using terms from Dublin Core. It raises an interesting question: should instance data mix and match terms from assorted namespaces? I have had many opinions on the matter, because it can be a useful utility to just copy terms into one namespace... but for the good of the Semantic Web, it's probably better to use other people's terms whenever you can - promoting interconnectivity, reducing the need to filter out duplicates, and generally establishing agreed upon standards. The evolutiary process is not smooth, even though we have the Semantic Web - we have to be selective about the data that we use!
A test of a DAML restriction
A filter to try to reify some RDF. Note that it, like many examples before it, use the old log.n3# namespace, which means that they are effectively broken when you try to put them through CWM. Of course, they also use the <> construct which incorrectly points to the document itself rather than the formula that it parses to, so it's doubly broken
The result of an experiment to go through the members of a DAML oneOf list, non-iteratively. DanC later showed me how to do it iteratively; it was quite obvious really
An example drafting of a schema language in N3. It would be an interesting experiment to convert James Clark's RELAXNG short grammar into Notation3, and find out if we could validate documents against RDF
A mock-up DOM Test Suite result for Curt Arnold et al., discussed more on the ERT WG list, and in the DOM TS group itself
A SEM related attempt at merging the core Semantic Web schemata. It was not all that successful because the core schemata are not maintained very well, and CWM doesn't appear to like "rdf:ID" on nodes, or got messed up somewhere along the line. The WebNS SWAG dictionary kinda replaces this experiment, but it would be nice to provide a feed of the basic SW schemata
Another Simpsons data experiemnt, this time involving a strange list model, using formulae as the list members. CWM basically threw up on it, and I filed a bug report with TimBL
An early copy of my URI schemes in Notation3 thing, which DanC asked for; earning me 1000 brownie points
A kind of early merge result for little sets of information about me - a bit like a Semantic Web homepage or business card. Eric Miller and Jim Hendler also (independently) produced things like this
This was basically the culmination (AFAIK) of the "address book" experiments, inspired by the early SWAG discussion, and later basically replaced to some extent by Dan Brickley's FOAF stuff. Nevertheless, the experiment still remains, and it would be interesting to find out how it would have scaled up
A simple test file using the ":-" anonode labelling construct. It was always quite difficult to work out what this token was supposed to do, especially as synchorizaion from the documentation to CWM could not be guaranteed. DanC did explain on #rdfig that ":-" labels an anonnode, but I'm not sure if it ever worked in CWM. CWM did at one point spew out ":-" in complex formula related results
An early attempt at Simpsons ratings, which eventually grew into the /2001/05/simpsons/ stuff
One of my earliest Notation3 files - describing the word yummers. Left for historical reasons only (the model is not all that solid - datatypes!)
Another early test, getting into the N3 language. This file incorporates a small statement, and a rule, such that an inverse property is declared; filtering a list of publications by author from a list of publications and their details
The result of running the other "coined by" files together through CWM - a simple filter exposing which people invented which terms within a schema. Kinda useful for administrative purposes, but more of a demonstration and experiment than anything else
This was a mock up of one of the experiments in the Semantic Web activity proposal; along with all the haystack stuff etc.
Sean B. Palmer