Changes between Version 36 and Version 37 of FCS-specification
- Timestamp:
- 04/26/13 13:41:35 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FCS-specification
v36 v37 398 398 }}} 399 399 400 The aggregator is asked to search the resources identified by "hdl:1839/00-0000-0000-0003-467E-9", "hdl:1839/00-0000-0000-0003-4682-F" and "hdl:1839/00-0000-0000-0003-4692-D" at endpoint "endpoint1.example.org" and the resource identified by "hdl:4711/1 at endpoint "endpoint2.example.org". The aggregator is asked to perform an unrestricted query at endpoint "example 2.example.org". This is signaled to the aggregator by leaving the list of resource identifiers for the respective endpoint empty.400 The aggregator is asked to search the resources identified by "hdl:1839/00-0000-0000-0003-467E-9", "hdl:1839/00-0000-0000-0003-4682-F" and "hdl:1839/00-0000-0000-0003-4692-D" at endpoint "endpoint1.example.org" and the resource identified by "hdl:4711/1 at endpoint "endpoint2.example.org". The aggregator is asked to perform an unrestricted query at endpoint "example3.example.org". This is signaled to the aggregator by leaving the list of resource identifiers for the respective endpoint empty. 401 401 402 402 A real-world example to restrict the search at the aggregator (using HTTP POST, and searching for the string "bellen") could look like the following (formatted for brevity):