On 20.2.2014 20:32, Stefan Lemme wrote: > > Hello, > > after our workshop last week a few questions about the POI Data > Provider raised and hopefully you can provide some insights. > > * Is there a GE implementation available beside the one packaged at > https://forge.fi-ware.eu/frs/?group_id=7#title_miwi-poidataprovider and > the probably same in the github repository at > https://github.com/Chiru/WeX/tree/master/poi ? > We will deploy one soon to some public server. > > * Is there further specification of the data components available > beside the draft of the open API specification at > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/POI_Data_Provider_Open_API_Specification_(DRAFT)#Data_Component_Structures**? > Not yet. > > * There is a mismatch between the JSON schema and data provided by > the POI-DP implementation regarding the "name" of a POI, for instance. > We had some phase difference between specification and implementation. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php?title=POI_Data_Provider_Open_API_Specification_(DRAFT)&oldid=28502 (13.2.2014 14:12) is the version corresponding the release 3.2. > > * How to realize relative POIs? > Not yet specified. Will be in the next release. > > * Where is the incoming data validated to comply with the > specification, e.g. JSON schema? > Validation in server is currently under development. > > * Wouldn't it be better to reference a remote xml3d element directly > by URI instead of string-encode dom elements? > Currently we need to do it that way. Remote URI to group does not work in XML3D. There is a related issue under development in https://github.com/xml3d/xml3d.js/issues/54 . > > * Which ontology is used for the category of a POI? How to handle > POIs referring to multiple categories? And what about tags? (All > with regard to multi-lingual content) > We took directly the value of amenity key in OpenStreetMap for fast start. This will be reconsidered to next release. > > * What entities are referred by UUIDs through source.id and > last_update.responsible? > They are references to source and person-profile descriptions not yet specified. > > * > > I would really appreciate to get some more informations about the open > questions. > > Best regards, > Stefan > > > -- > ******************************************************** > Stefan Lemme > > DFKI GmbH > Agenten und Simulierte Realität > Campus, Geb. D 3 4, Raum 0.75 > 66123 Saarbrücken > > Tel.: +49 (0) 681 / 85775 -- 5391 > Fax: +49 (0) 681 / 85775 -- 2235 > http://www.dfki.de/web > ******************************************************** > Deutsches Forschungszentrum für Künstliche Intelligenz GmbH > Trippstadter Straße 122 > D-67663 Kaiserslautern, Germany > > Geschaeftsführung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973 > Steuernummer: 19/673/0060/ > ******************************************************** > > > > > > ******************************************************** > Stefan Lemme > > DFKI GmbH > Agents and Simulated Reality > Campus, Build. D 3 4, room 0.75 > D-66123 Saarbruecken > Germany > > Phone: +49 (0) 681 / 85775 -- 5391 > Fax: +49 (0) 681 / 85775 -- 2235 > http://www.dfki.de/web > ******************************************************** > German Research Center for Artificial Intelligence > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany > > Management Board: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Chairman) > Dr. Walter Olthoff > > Chairman of the Supervisory Board: > Prof. Dr. h.c. Hans A. Aukes > > Amtsgericht Kaiserslautern, HRB 2313 > ******************************************************** -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140221/91f12f0a/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy