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

provide self-contained, normative description #93

Open
chiarcos opened this issue Jun 15, 2022 · 1 comment
Open

provide self-contained, normative description #93

chiarcos opened this issue Jun 15, 2022 · 1 comment

Comments

@chiarcos
Copy link

chiarcos commented Jun 15, 2022

In terms of readability, a problem is that many aspects of current RDF standards are defined in external documents. In general, this is a great idea, as it eliminates redundancies and creates synergies, but it is problematic for the occasional user. Taking the SPARQL function REPLACE as an example, this is currently defined with reference to XPath fn:replace, but it order for it to work, users need to

  • understand the SPARQL/RDF specifications,
  • understand the XPath/XML specifications,
  • retrieve the relevant bits from the XPath spec,
  • integrate it conceptually with their interpretation of the SPARQL/RDF specification, and
  • figure out common implementation details that are not documented in the XPath spec (e.g., double escaping of "\")

The second, third and fourth step in this process are completely unnecessary (other than for formal reasons), and with decreasing relevance of XML standards they even become a major obstacle, so having a compact (maybe even non-normative) description of these aspects in a single, coherent document (https://en.wikibooks.org/wiki/SPARQL/Expressions_and_Functions is quite good at this, actually) will improve readability a lot.

@TallTed
Copy link
Member

TallTed commented Jun 15, 2022

will improve readability a lot.

I daresay, will improve readability and usability a lot.

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