Description
RFC-5785 defines a path prefix for "well-known locations", i.e., /.well-known/. Paulheim and Hertling suggest the usage of /.well-known/void to gather VoID information regarding the datasets available in the server. The parser should implement this behavior.
A previous implementation of #118 would increase the impact of this feature.
Solution
- The Frontier could offer the addition of classes which are allowed to "extend" the list of new URIs based on internal rules. For the case described above such a class would simply go through all new URIs, extract the domains (maybe together with their path information as discussed in the paper) and add
/.well-known/void. Since we can assume it to be a dereferencable URI, the type of this newly generated URI can be set as well.
Description
RFC-5785 defines a path prefix for "well-known locations", i.e.,
/.well-known/. Paulheim and Hertling suggest the usage of/.well-known/voidto gather VoID information regarding the datasets available in the server. The parser should implement this behavior.A previous implementation of #118 would increase the impact of this feature.
Solution
/.well-known/void. Since we can assume it to be a dereferencable URI, the type of this newly generated URI can be set as well.