Enrichment services

These are the services taking part in the KB Research enrichment infrastructure.
  1. Get enrichments for an information resource

    Syntax: base_URL?id=object_id
    This service returns a JSON list containing all enrichments for the object with object_id as identifier. There is no restriction to the syntax of this identifier, but it should be unique. Each enrichment is a list of name-value pairs, containing such information as a URL to related information, a named entity string, a confidence level etc.
    Example:
    http://tomcat.kbresearch.nl/links/ir?id=http://resolver.kb.nl/resolve?urn=ddd:010659765:mpeg21:a0226:ocr
  2. Get enrichments for a non-information resource

    Syntax: base_URL?id=resource_id
    This service returns a JSON list containing all enrichments for a non-information resource with a specific resource-id. Currently, these enrichments are links to resource descriptions and other related web pages. For supported resource description frameworks the resource identifier is a prefix for the framework combined with the framework resource identifier, for example DPB:Albert_Einstein or VIAF:75121530. If it is not from such a framework the resource-id is supposed to be a complete URL.
    Examples for the same resource with different resource-ids:
    http://tomcat.kbresearch.nl/links/nir?id=DBP:Albert_Einstein
    http://tomcat.kbresearch.nl/links/nir?id=VIAF:75121530
  3. Get the value of specific properties of a non-information resource

    Syntax: base_URL/resource_id?{property_name_list}
    This service returns the property values for a specific resource. It is supposed to provide low-barrier functionality for obtaining specific information about a resource.
    Examples:
    http://tomcat.kbresearch.nl/ods/VIAF:75121530?birthDate,deathDate
    http://tomcat.kbresearch.nl/ods/VIAF:75121530?thumbnail
  4. Add or delete an enrichment for an information resource

    Syntax: base_URL?action=add|delete&objectId=object_id&subjectId=subject_id&other_parameters
    With this service an enrichment for a specific object_id can be added or deleted. The parameter list contains a number of fields that are specific for the type of enrichment, like the subject_id, being the link to the related information. These fields are returned when an enrichment record is requested with one of the previous services. If the enrichment record did not exist, it is created.
    This service requires a login.
  5. Add or delete an enrichment for a non-information resource

    Syntax: base_URL?action=add|delete&objectId=object_id&subjectId=subject_id&other_parameters
    With this service a link to either a resource description or other information related to the resource can be added to or deleted from a non-information enrichment record. If the enrichment record did not exist, it is created.
    This service requires a login (see video example ).
  6. Expanded SRU service

    Syntax: base_URL?{SRU_parameters}, with CQL/query extension: [property=value]
    This service uses the same API as the SRU service of KB, but differs from the conventional SRU service in that it takes the condition between brackets, sends it to a SPARQL endpoint (currently DBpedia) and returns the names of the objects that meet the specified condition. These names are substituted in the CQL query being sent to the SRU service of KB. This extension is intended for formulating additional conditions to a query. It is still under construction: eventually we will use the identifiers of resources instead of their names. We also want to investigate how to optimize the processing of the SPARQL output as input for the conventional search, because limitations may be imposed on the query length.
    Example:
    http://tomcat.kbresearch.nl/stsb/sru?query=[dbpedia-owl:influencedBy=Pablo_Picasso]&x-collection=DDD_artikel
    Portal view
  7. Get potential links for named entities in a text

    Syntax: base_URL?[url=value][&ne=value][&context=true|false][debug=0|1]
    This service is used in the process of the creation of named entity enrichments. It extracts the named entities in the text parameter value or the text pointed to by the value of the url parameter, searches the named entities in DBpedia and returns a JSON list of potential DBpedia links. The debug parameter is used to provide information about the reason for not finding a match. In case the named entity (parameter ne) is provided, the named entity recognition is skipped and the most probable link for that specific NE is searched for. In case context=true (not yet supported) the context of the text from the text or url parameter and the contents of the DBpedia record are used by the matching algorithm. This matching algorithm is still under construction.
    Example:
    http://link.kbresearch.nl/?url=http://resolver.kb.nl/resolve?urn=ddd:010369397:mpeg21:a0040:ocr