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

fno:type is not defined, and inconsistently used #1

Closed
pchampin opened this issue Jun 23, 2020 · 1 comment
Closed

fno:type is not defined, and inconsistently used #1

pchampin opened this issue Jun 23, 2020 · 1 comment

Comments

@pchampin
Copy link

(not sure if this is the right place for giving feedback on https://fno.io/spec/, version from 2019-05-29?)

In examples 4, 6, 8 and 15, a property fno:type is used. However,

  • this property is not defined by the spec;
  • it is used inconsistently: in examples 4, 6 and 8, it is applied to the predicates linked to parameters; in example 15, it is applied directly to the parameters;
  • in examples 4, 6 and 8, it seems to duplicate the semantics of rdfs:range.
@bjdmeest
Copy link
Contributor

You are right! In fact, I extracted the spec from this repo and put it in a dedicated repo to better track these kinds of issues.
I also updated the spec to fix your actual comment: indeed fno:type should be applied directly to the parameter (https://fno.io/spec/#fn-parameter)

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

No branches or pull requests

2 participants