Table of Contents


  • Prior to Meeting: Contribute to Use Cases by adding a use case or refining one already added. 


  • Gather and define Use Cases

Meeting Materials



Going through Current Approaches to Providing Search APIs helps to understand intention to support different use cases.

  • Patterns include care for supplying different response types (jsonld, RDF/XML, json, etc.), RWO/Concept support, left anchored search, exact match searching.

Use Case discussion

  • Label exact match search supports unsupervised automated batch add URIs to existing data.
  • ATOM feed is an API that gives the delta, to update cached data based on changes.
  • Generally, there's a need to not build separate ETL processes for each dataset for caching locally data for indexing to support local workflows
  • Filtering is useful in a number of workflows, whether automated, supervised batch, or single entity search. What to filter on is a significant challenge, with a need to understand both the data model and consumer needs.
  • Of the use cases defined, there seems to be two schools of thought on where to start, first focus on a consistent return of data with agreed upon data models across different data sets (because without it deciding what to search for each in each dataset is really hard) or first focus on providing a general search that returns a URI, label with other context in a consistent format (which would punt the modeling questions, but provide consistent access technology-wise) 



  • No labels