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

Add section for implementation considerations #6

Closed
pmaria opened this issue Mar 26, 2021 · 1 comment
Closed

Add section for implementation considerations #6

pmaria opened this issue Mar 26, 2021 · 1 comment

Comments

@pmaria
Copy link
Collaborator

pmaria commented Mar 26, 2021

There are several considerations that can be made when implementing RML+FnO. Some of these might need to be specified in their own section, others might be too specific too certain implementations, but might still be interesting to mention. For now we can add a section 'Implementation considerations' to collect these, as discussed in this slack thread

Examples of issues:

  • Handling programming language specific datatypes
  • Special handling of RDF term types in used software library (e.g. from RDFJS, JENA, etc)
    • e.g. what if a function returns an RDF literal with language tag?
  • What should an engine do with the generated FnO execution triples (from the function triples map)?
@bjdmeest
Copy link
Member

I created #8, kg-construct/rml-fnml#6, kg-construct/rml-fnml#1, to discuss the individual issues separately, and added a section in the spec :)

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