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

Spaql query - Define policy for optional properties #23

Open
ghost opened this issue Sep 9, 2016 · 0 comments
Open

Spaql query - Define policy for optional properties #23

ghost opened this issue Sep 9, 2016 · 0 comments

Comments

@ghost
Copy link

ghost commented Sep 9, 2016

Some times we have to switch some patterns to OPTIONAL because if not, the query returns no result. It might be useful to define which property can be seen as optional (see for instance #21 for a pattern using the skos:notation predicate that needed to be turned to optional).

Plus, if we consider a pattern as OPTIONAL, we have to deal with the situation where it is not present in the ui.

More precisely:

  • is skos:prefLabel mandatory for a classification ? For an item ? For a level ? For a correspondence ?
  • the same with skos:notation.
ghost pushed a commit that referenced this issue Sep 9, 2016
See #23 and #22 for related issues
classification code is opotional, but if not present we will still get the label.
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

0 participants