From: Lars H. <he...@se...> - 2008-10-21 13:37:52
|
Hi all, While working on Atomico <http://atomico.googlecode.com/> I wondered if it would make sense to implement a TopicMapSystem for tinyTiM which works upon TMShare. The first implementation would be read-only, I guess. Something like: tmSysFactory.setFeature( "http://tinytim.sf.net/feature/tmShare", "http://iri.which.points.to.a.tmshare.overview"); TopicMapSystem tmSys = tmSysFactory.newTopicMapSystem(); for (Locator loc: tmSys.getLocators()) { System.out.println(loc); // Prints out the available topic // maps at the specified server } TopicMap tm = tmSys.getTopicMap(loc); tmSys.createTopicMap(loc2); ---> Exception, the tmSys is read-only The topic map and the system could also be writable but there wouldn't be any synchronisation with the TMShare server (at least not in the initial version). Thoughts? Best regards, Lars -- Semagia <http://www.semagia.com> |
From: Stefan L. <li...@ap...> - 2008-10-21 13:41:55
|
Hi Lars, I saw a photo that you got the price at TMRA congrats. Can i find some report and slides from TMRA 2008 somewhere? stefan 2008/10/21 Lars Heuer <he...@se...>: > Hi all, > > While working on Atomico <http://atomico.googlecode.com/> I wondered > if it would make sense to implement a TopicMapSystem for tinyTiM which > works upon TMShare. The first implementation would be read-only, I > guess. > > Something like: > > tmSysFactory.setFeature( > "http://tinytim.sf.net/feature/tmShare", > "http://iri.which.points.to.a.tmshare.overview"); > > TopicMapSystem tmSys = tmSysFactory.newTopicMapSystem(); > > for (Locator loc: tmSys.getLocators()) { > System.out.println(loc); // Prints out the available topic > // maps at the specified server > } > > TopicMap tm = tmSys.getTopicMap(loc); > > tmSys.createTopicMap(loc2); ---> Exception, the tmSys is read-only > > > The topic map and the system could also be writable but there wouldn't > be any synchronisation with the TMShare server (at least not in the > initial version). > > Thoughts? > > Best regards, > Lars > -- > Semagia > <http://www.semagia.com> > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > tinyTiM-discuss mailing list > tin...@li... > https://lists.sourceforge.net/lists/listinfo/tinytim-discuss > |
From: Lars H. <he...@se...> - 2008-10-21 13:49:45
|
Hi Stefan, > I saw a photo that you got the price at TMRA congrats. Can i find some > report and slides from TMRA 2008 somewhere? Thanks, very difficult challenge... ;) I'll send you the TMShare slides as PDF. I sent them together with the other presentations and tutorials to Lutz and they should appear at the TMRA'08 site soon. I guess LMG will write something about TMRA'08. Maybe rho, too. Best regards, Lars -- Semagia <http://www.semagia.com> |
From: Lars H. <he...@se...> - 2008-10-21 16:34:45
|
[...] > The topic map and the system could also be writable but there wouldn't > be any synchronisation with the TMShare server (at least not in the > initial version). [...] Basically, tinyTiM would act as client which consumes the topic maps provided by the TMShare server. After the TopicMapSystem has been initialized, the system would contact the TMShare server and load the latest snapshots from the server (could be done lazily, i.e. the initial request would just download the information about the provided topic maps). After a topic map has been read, tinyTiM would act independent of the TMShare server (it does not report changes to the server, for example). The system could go into a another tinyTiM subproject, the core engine wouldn't be effected. The TopicMapSystemFactory would look if the feature "TMShare" is set and then load the specialised TopicMapSystem (i.e. Class.forName("org.tinytim.tmshare.TopicMapSystem");). The user would have to include additional libs only if she wants to have that functionality. The question is, if it would be valuable to implement such a system or if it would be a waste of time and effort. Best regards, Lars -- Semagia <http://www.semagia.com> |
From: Lars H. <he...@se...> - 2008-10-23 13:46:30
|
[...] > The question is, if it would be valuable to implement such a system or > if it would be a waste of time and effort. Created a feature request for it: <https://sourceforge.net/tracker/index.php?func=detail&aid=2189442&group_id=102341&atid=631667> Feel free to implement it, I am afraid that I won't be able to implement it in the near future. Best regards, Lars -- Semagia <http://www.semagia.com> |
From: Stefan L. <li...@ap...> - 2008-10-23 14:42:39
|
Hm, All i found about TMShare was an old paper from Kal [1]. Is it a product from networkedplanet or some standard? if its not a standard, we might leave it as a feature request. [1] http://www.idealliance.org/papers/dx_xmle03/papers/02-03-03/02-03-03.html 2008/10/23 Lars Heuer <he...@se...>: > [...] >> The question is, if it would be valuable to implement such a system or >> if it would be a waste of time and effort. > > Created a feature request for it: > <https://sourceforge.net/tracker/index.php?func=detail&aid=2189442&group_id=102341&atid=631667> > > Feel free to implement it, I am afraid that I won't be able to > implement it in the near future. > > Best regards, > Lars > -- > Semagia > <http://www.semagia.com> > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > tinyTiM-discuss mailing list > tin...@li... > https://lists.sourceforge.net/lists/listinfo/tinytim-discuss > |
From: Lars H. <he...@se...> - 2008-10-23 14:55:36
|
Hi Stefan, > All i found about TMShare was an old paper from Kal [1]. Is it a > product from networkedplanet or some standard? if its not a standard, > we might leave it as a feature request. Ah, sorry, my fault. I expected that everybody is familiar with the paper. TMShare homepage: <http://www.egovpt.org/fg/CWA_Part_1b> TMShare paper (outdated): <http://tmra.de/2008/talks/protocol-for-the-syndication-of-semantic-descriptions.html> I updated the feature request with the links. Best regards, Lars -- Semagia <http://www.semagia.com> |
From: Lars H. <he...@se...> - 2008-10-23 15:28:33
|
[...] >> All i found about TMShare was an old paper from Kal [1]. Is it a >> product from networkedplanet or some standard? if its not a standard, >> we might leave it as a feature request. It's not a standard, though. It's a protocol based on Atom. Anyway, the spec is freely available and it is better than nothing. :) The basic idea was that tinyTiM utilises the snapshots from the server. The provided fragments will be ignored at least in the initial version. tinyTiM would contact the server, look for the available topic maps and download the topic map on request transparently for the user. The next version could also consider the fragments. I.e. download all fragments which are published later that the latest snapshot. There is also TMRAP but it has slightly other goals. I.e. downloading a complete map is not possible with TMRAP. TMRAP can be used to ask a server if it has information about a particular topic, for example. Implementing a TopicMapSystem for TMShare shouldn't be too hard. The system would establish a connection to the server, parse the overview page and use the provided topic maps as initial set of locators returned by TopicMapSystem.getLocators(). Once the user uses TopciMapSystem.getTopicMap(Locator), the system downloads the latest snapshot, deserializes it and returns the topic map. Or the system download the topic maps in a background task after it has been initialized. The TMShareTopicMapSystem would be a bit heavier than the ordinary TopicMapSystem, so it should be implemented as a tinyTiM subproject. Further, the TMShareTopicMapSystem would introduce a dependency to a deserializer package (i.e. tinytim-mio) and may introduce more dependencies, i.e. to Restlet [1] or to the HTTPClient [2]. Maybe it can be implemented with the standard Java libs (URLConnection and friends). Anyway, that's the rough idea. [1] <http://www.restlet.org/> [2] <http://hc.apache.org/> Best regards, Lars -- Semagia <http://www.semagia.com> |