Opened 7 years ago
Closed 7 years ago
#989 closed task (worksforme)
CLARIN-FCS endpoints cardinality
| Reported by: | Eduard Drenth | Owned by: | Dieter Van Uytvanck |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | AAI | Version: | |
| Keywords: | fcs endpoint design | Cc: | Sander Maijers |
Description
Do I understand correctly that the FCS design assumes one endpoint per search engine, where a search engine may or may not search multiple resources?
Change History (3)
comment:1 Changed 7 years ago by
| Cc: | Sander Maijers added |
|---|
comment:2 Changed 7 years ago by
comment:3 Changed 7 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
In short: it's more or less up to the center.
If an endpoint acts as a bridge to one or more local search engines. An endpoint can provide access to multiple resources, but you could also have one endpoint per resource.
All endpoints of the center should be registered in the center registry and will then be picked up by the FCS Aggregator (or other tools could query the center registry and talk to the endpoints).
P.S. Most of your recent tickets are general FCS questions and not software of specification issues.
Please send those questions to the FCS Taskforce Mailinglist (tf-fcs@lists.clarin.eu). If you're not a member, we can subscribe you.
Tickets in Trac should be used for software issues with the reference implementation or issues with the specification material (documents, xml schemas, etc). Thanks!