You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: