Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear documentation of rdf_current_prefix/2 #81

Open
wouterbeek opened this issue Jul 6, 2018 · 0 comments
Open

Unclear documentation of rdf_current_prefix/2 #81

wouterbeek opened this issue Jul 6, 2018 · 0 comments

Comments

@wouterbeek
Copy link
Contributor

wouterbeek commented Jul 6, 2018

rdf_current_prefix(:Alias, ?URI) is currently documented as follows:

If Alias is unbound and one URI is the prefix of another, the longest is returned first. This allows turning a resource into a prefix/local couple using the simple enumeration below.

rdf_current_prefix(Prefix, Expansion),
atom_concat(Expansion, Local, URI),

What does this mean? If Alias is unbound and URI is unbound, then the declared Alias-URI pairs are enumerated, regardless of the lengths of URI. If Alias is unbound and URI is bound, there is at most one solution for Alias, so there is no use for returning the longest solution first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant