• https://www.linkedin.com/pulse/iot-directory-come-back-uddi-ldap-all-forgiven-david-traynor

FIWARE project home: https://www.fiware.org/

FIWARE Catalogue (of the so-called “generic enablers”): http://catalogue.fiware.org/

From there, you may select “IoT Services Enablement” (the green circle). That brings up a related list of GEs. The “IoT Discovery” enabler could be particularly relevant for our current discussion on the directory service: http://catalogue.fiware.org/enablers/iot-discovery http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.IoT.Backend.IoTDiscovery

• Limitation: http://fiware-orion.readthedocs.io/en/latest/user/known_limitations/index.html
• Context query: http://fiwaretourguide.readthedocs.io/en/latest/development-context-aware-applications/v2/how-to-update-and-query-context-information/
• IoT: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture
  • Backend:
    • http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTDiscovery

Working dir

  /home/dang/data/mydirectory/mywork/dailabor/00--current/00_dai_pjs_actual/50_ISCO/isco_ws/05_AP5/05_icn_based_directory/references/IoT_ICN

• Jabref
• papers: http://link.springer.com/book/10.1007/b100845/page/2
• https://tools.ietf.org/html/draft-zhang-icn-iot-architecture-00
  • NDN's Interest/Data mechanisms allows only one response for each Interest send while discovery requires to learn multiple entities, hence efficient discovery is realized using exclusion via Selectors in the protocol or as an overlay protocol [29].