Changes between Version 5 and Version 6 of ApertureRDFMap


Ignore:
Timestamp:
Oct 25, 2005, 6:39:38 PM (21 years ago)
Author:
sauermann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ApertureRDFMap

    v5 v6  
    66Comment from an email:
    77I've taken a look at rdf2go. Looks nice! It's still alpha-stage though, I don't know how bad that is. It's also Java 5 (at least that's what it said, I didn't get this from the Javadoc). I thought you would rather have a 1.4-compatible API? We can also take a look at jrdf and related approaches, but I have no experience how good they are. Maybe defining our own simple interface is then not such a bad idea after all, it seems rather trivial to do and then we at least have full control over it. If one of the other RDF APIs becomes a standard, whether ad hoc or standardized, we can always define our interface as a specialization of this interface and map our own methods to the standard versions.
     8
     9= Api solution? =
     10as a hack, I would suggest to use the current Sesame2 inmemmodel as it is. Ought to be  way there to create triples somehow. I thought about using the old RIO package, but all those convenience mehtods have been deleted *sniff*., no more resource.addProperty(p, o)
     11
     12still have to see how this code here is possible in sesame2:
     13
     14{{{
     15#!java
     16Model m = new ModelImpl();
     17Resource r = m.createResource(uri).
     18r.addProperty(p, o);
     19r.addProperty(p1, o1);
     20return r;
     21}}}
    822
    923{{{