Zach, The R2RML issue is here: https://github.com/d2rq/d2rq/issues/84
Best, Richard On 17 Aug 2011, at 16:00, Richard Cyganiak wrote: > On 17 Aug 2011, at 14:02, Whitley, Zachary C. wrote: >> I was wondering what you had in mind as the roadmap for D2R development. I >> guess the big question is how do you see R2RML support fitting in with D2R? >> I haven't had a chance to dig into the D2R code yet so I don't have any idea >> what would be involved with that effort. Would this require a new code base >> or would D2R be a good starting point? > > I definitely want to see R2RML support happen in D2RQ. > > I think that the D2R codebase is a good starting point. The internals of the > D2RQ engine (all the TripleRelation/NodeMaker stuff and the ARQ integration) > can be used for implementing R2RML. And the user-facing stuff – the scripts, > APIs and D2R Server – would work very well for an R2RML implementation too. > > I think that the best way forward would be to (i) add a number of missing > features to the D2RQ mapping language and D2RQ engine, so that it supports > all the features of R2RML (named graphs, non-bijective translation tables, > xsd:hexBinary, etc); and (ii) add a new mapping parser and compiler that > understands R2RML but uses the existing internals. I expect the second part > to be easy once the first is done. > > I'm planning to create an issue on GitHub that lists the things that would > need to be added to the D2RQ engine so that R2RML can be implemented over it. > Will post a link here once the issue is created. > > Richard > > >> >> >>> -----Original Message----- >>> From: Richard Cyganiak [mailto:[email protected]] >>> Sent: Wednesday, August 17, 2011 8:34 AM >>> To: d2rq-map-devel (E-mail) >>> Subject: [d2rq-dev] D2RQ on GitHub >>> >>> All, >>> >>> I'm in the process of slowly moving D2RQ hosting from SourceForge to >>> GitHub. >>> >>> This will from now on be considered the "official" D2RQ source >>> repository: >>> https://github.com/d2rq/d2rq >>> >>> Note that it contains both the D2RQ engine and D2R Server. They will no >>> longer have their separate repositories. >>> >>> I've also gone through a lot of old emails and notes, trying to capture >>> a reasonably up-to-date issues list: >>> https://github.com/d2rq/d2rq/issues >>> >>> I'll move the remaining open issues from SourceForge to that list in >>> the near future. >>> >>> This mailing list will remain on SourceForge for the foreseeable >>> future. >>> >>> All the best, >>> Richard >>> ----------------------------------------------------------------------- >>> ------- >>> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, >>> user administration capabilities and model configuration. Take >>> the hassle out of deploying and managing Subversion and the >>> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 >>> _______________________________________________ >>> d2rq-map-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > d2rq-map-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ d2rq-map-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel
