I’ve just returned from the First Italian Workshop on the Semantic Web (SWAP 2004), organised by long time chat-buddy and RDFIG lurker GiovanniT.

I notice that several folk are arriving at the rdf namespace oddness page which describes the slightly opaque problem of understanding RDF Schema URI’s and how to go about loading them.
I’ve long since found a solution, following a discussion on #rdfig a long time back. That solution is content negotiation, so for the record, [...]

The pages discussed here concern the representation of XML within RDF (a very different concept to that of the serialization of RDF in XML).

the question of who (or what) should proivide the iconic representation for nodes is playing on my mind. I’m thinking there needs to be a local cache – which can be initially populated with some defaults – but that it should be a dynamic thing basd on resource type, and using an RDF lookup .

One of the thgings I’ve added today is a little code to guess where the schema may be – in order to validate or interpret conent the schema needs to be accessible, so the code now checks for index.rdf and schema.rdf files if the supplied namespace is one that does not end in a “#” [...]

An addition to the core today is the ability to load RDF from a URI as well as a file – to demonstrate this I now have a news feed from theregister.co.uk being pulled in to the system when it’s started.

today i’ve

added sorting to the list of things the code can do. there’s not much intelligence there yet, but the mechanism is connected.
added a menu into the Resource List view so the sort can be selected, and
started to use Actions to abstract the users selections from the underlying code which implements them.

my comment yesterday about bookmarks triggered somehting this morning – what may be useful would be forward and back buttons in the explorer, so that current, and previous roots could be viewed and reviewed – this should be easy to implement by maintaining the INode tree. having a preference of how many histories would [...]

The List and Explorer views are now working insofar as they can be created and display some content. Double clicking on an entry in the Resource List makes that entry the head node in the Explorer – this mechanism, when combined with filters in the Resource List makes it easy to find the node you [...]

i’ve been humming and harring about the core model. to be really capable there is a need to avoid

over-dependence on Jena and
over-engineering the API.

i’d like the core to be abstracted from Jena so that as if an alternative model comes along, or if/when Jena release version 2, there shouldn’t be any major problem switching [...]