Comments (8)
detail but in the case of RML (given that FnO is aligned with RML but not R2RML),
it should be reference-based term map (instead of column-based) or function map
before reaching the point of voting, should we perhaps look into our use cases or call for use cases?
The use cases might give us insights regarding what might be the most commonly intuitive.
from rml-fnml.
You're right, added definition for a function map and used that one where relevant, see change at 506737a2c9f952d9aebcb651176f8e00dc801057
from rml-fnml.
Ah yes, and right now the default term type depends on whether the term map is an object map or not is (implicitly) extended into
If the term map does not have a
rr:termType
property, then its term type is:
- rr:Literal, if it is an object map and at least one of the following conditions is true:
- It is a column-based term map or a also fnml:FunctionMap
- It has a
rr:language
property (and thus a specified language tag).- It has a
rr:datatype
property (and thus a specified datatype).- rr:IRI, otherwise.
I have no real opinion for what should be the default case. I'll clarify in the spec what the current situation is, but I don't want to force that as solution. Maybe we should just vote or smth?
from rml-fnml.
detail but in the case of RML (given that FnO is aligned with RML but not R2RML),
it should be reference-based term map (instead of column-based) or function map
You're right and I also had that insight before changing the spec, it's now as below, in accordance with the current RML spec
If the term map does not have a
rr:termType
property, then its term type is:
rr:Literal
, if it is an object map and at least one of the following conditions is true:
- It is a reference-based term map, or also a fnml:FunctionMap
- It has a
rml:languageMap
and/orrr:language
property (and thus a language map and/or a specified language tag).- It has a
rr:datatype
property (and thus a specified datatype).rr:IRI
, otherwise.
👍 on the use cases :)
from rml-fnml.
It is a reference-based term map, or also a fnml:FunctionMap
getting picky with details now but the one is in a human readable format, ie reference-based term map and the other in machine-readable format, ie fnml:FunctionMap
.
Better keep both human-readable: reference-based term map and function map
or both in machine-readable format: rr:TermMap
with rml:reference
and fnml:FunctionMap
or a hybrid :)
(I'm personally in favor of the former)
from rml-fnml.
similar question here, do we have use cases in the end for this? If not, maybe we need to consider having a collective call for issues that we want to work on and we don't have use cases?
from rml-fnml.
Considering this definition (and for now fnml:FunctionMap
as a term map), if the FunctionMap
is a rr:subjectMap
and no rr:termType
is provided then the default type is rr:IRI
, did I understand it correctly?
Ah yes, and right now the default term type depends on whether the term map is an object map or not is (implicitly) extended into
If the term map does not have a
rr:termType
property, then its term type is:
rr:Literal, if it is an object map and at least one of the following conditions is true:
- It is a column-based term map or a also fnml:FunctionMap
- It has a
rr:language
property (and thus a specified language tag).- It has a
rr:datatype
property (and thus a specified datatype).rr:IRI, otherwise.
I have no real opinion for what should be the default case. I'll clarify in the spec what the current situation is, but I don't want to force that as solution. Maybe we should just vote or smth?
from rml-fnml.
Given the text at https://kg-construct.github.io/fnml-spec/#fnml-outputtermmap, I close this issue with commit 257a79f, feel free to reopen
from rml-fnml.
Related Issues (20)
- What should an engine do with the generated FnO execution triples (from the function triples map)? HOT 5
- Mismatch in naming of `fnml:outputMap` vs its target `fnml:ReturnMap`
- Typo in Example 6: use nested function? HOT 1
- fnml:ReturnMap HOT 2
- Visual overview of connections FNML HOT 9
- Why does a valueMap not have a specific termMap subclass? HOT 7
- Use newly introduced ExpressionMap as domain for execution, return, and returnMap HOT 11
- naming of properties in light of single namespace HOT 3
- Testcases: add tests HOT 1
- Re-structure the repo and change name HOT 1
- Use correct prefix for test-cases
- Adjust test-cases to match ontology changes
- Use the correct references for the RML Core parts
- Function definition with SPARQL to be considered in the future
- test cases and fno definitions
- Issues with test cases HOT 8
- Issues with shapes and ontology
- Special handling of RDF term types in used software library (e.g. from RDFJS, JENA, etc)? HOT 4
- Add a diagram aligned with the rest of the specs HOT 2
- Is the class `fnml:OutputTermMap` necessary? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rml-fnml.