Semantic Computing: the extension of the Semantic Web to the point where its methods and standards are pervasive in all computing. If you don’t believe this will happen, you might as well go the whole hog and say that the wheel will never catch on.
Subscribe to this category. RSS, Atom.
July 9th, 2003, by Rich, in RDFX.
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 . More…
July 5th, 2003, by Rich, in RDFX.
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 “#” or if it ends with a “/”.
Of course these are only tried if the default doesn’t work.
July 4th, 2003, by Rich, in RDFX.
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. More…
July 3rd, 2003, by Rich, in RDFX.
today i’ve
July 3rd, 2003, by Rich, in RDFX.
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 ensure memory isn’t gobbled up.
essentially, the core functions are “starting to happen” now, so I’m starting to have ideas about user will eventually want to navigate this data.
July 1st, 2003, by Rich, in RDFX.
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 want… to a point. another view that would be good - or an interesting twist at least, would be a simple search view. the problem here is that the boundaries between all the views are getting blurred. The list will probably have filters, the explorer too, the Digger will be search based…
Perhaps some concept of bookmarks would be good - Perhaps the digger could provide this since it’s nodes will be the most generic.
Anyhow, the image below is of the plugin as it ran this afternoon showing the default content in the List the initial content in the Explorer was /people/rich however, double-clicking on (activating) hong’s entry in the list defocused the explorer on the hong resource. The properties view shows the content of /rich which was selected in the Explorer view.
Note that “?>” in the properties is a flag to show that this name wasn’t looked up successfully - I need to look at decorators to understand how to best represent such things dynamically.
June 30th, 2003, by Rich, in RDFX.
i’ve been humming and harring about the core model. to be really capable there is a need to avoid
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 the current code out, or augmenting it.
since RDF has an XML serialisation mechanism, that is the obvious choice for the API - it relies not on objects but on a stream of data, whose structure and syntax are all pre-defined and controlled.
So, that may be a suitable API - by using XML to serialise and reconstitute objects, different models may be used - this would mean the concern I raised earlier about plug-ins for non-java languages can be laid to rest.
June 30th, 2003, by Rich, in RDFX.
Although not immediately apparent, the usefulness of the list view is large. In a nutshell, the concept of the list view is that it provides a flat list of all Resources thus:
To list is very basic, so perhaps the resource type could be included in a table rather than a list view. Filters could be added based on Type, Source, Content etc… the important thing is that it provides a neat way of displaying all the data model so that, upon a double click (possibly) the RDF Explorer root can be set - perhaps in an existing view, perhaps in a new view - this could be set in the prefs.
Such niceties are for further down the line anyway - for now, the mechanism is just that when a node is clicked, it is selected in an existing RDF explorer if it exists, and when double-clicked the explorer tree root is set to the chosen node.
June 25th, 2003, by Rich, in RDFX.
in building RDFSchemaLabelProvider i’ve had some interesting namespace problems. some namespaces are defined, ending with a “#”, which include the name of the definition file, some have no hash, no trailing slash, and define a URL where that file can be assumed to be, for example:
[xml]
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1">
[/xml]
This is a pain when trying to work out (a) which file to load and then (b) what the actual namespace should be for the content of that file - in the case of the rdf namespace the file is exactly as described - http://www.w3.org/1999/02/22-rdf-syntax-ns but in the case of foaf namespace the file is http://xmlns.com/foaf/0.1/index.rdf
:-?
June 25th, 2003, by Rich, in RDFX.
RDF contains some structures. Bag and Set, for example - then - extensions to the schema can also contain structures - DAM+OIL and OWL for example add concepts of cardinality - should the browser be able to handle these specially, or just treat them as resources (which they are).
Essentially - is there a need for a mechanism which interprets the resource type and substitutes a replacement, bespoke INode implementation, and if there is that need, can it be done? Answers: No, not for UISB and Yes, but it might prove interesting :)
