You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @hvdsomp, the current approach is to describe the service within the data return from the root, using (among others) LDP. Do you have use cases where this would not be sufficient? If so I'd be happy to hear more.
Using HATEOS ideas, this:
When the FAIR Data Point Service root URL receives an HTTP GET request (e.g., http://mydomain.com/fdp/)
would typically be implemented using the Well-Known URI approach, see
https://tools.ietf.org/html/rfc5785 and https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml . Meaning, one would expose eg
http://mydomain.com/.well-known/fdp/ and register
fdp
The text was updated successfully, but these errors were encountered: