Explain the following: - normal fdp and fdp-index share the same code base, but index functionality is disabled by default - index maintains a curated list of fair data points (admin can accept/reject) - index harvests the metadata from listed fair data points, to enable sparql queries over all metadata - it copies the metadata from all the fdps into the local triple store - therefore it requires more memory than a typical fdp - index updates status of the individual fair data points based on regular incoming pings and harvesting results - ...?
Explain the following: