-
Notifications
You must be signed in to change notification settings - Fork 3
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
A Field is an ExpressionMap #26
Comments
Agreed.
You mean add these properties to rml-core? We don't want to do that, since that would couple rml-core to rml-lv. The choice was made early on to have separate modules that build on core (or on each other) to give implementations a choice to implement only specific modules. |
No, I mean to have an explicit bullet list like core:
So, something like:
This can be done only for properties specific to fields, since those inherited from ExpressionMaps are already defined in core. |
Ah I see. Also agreed. |
moving this discussing to issue kg-construct#26, as agreed
Hi, spec says "A field is an ExpressionMap that gives a name to an expression."
Actually, also in the ontology, Fields are subclasses of expression maps. Thus, I would phrase this more explicitly as: "A field is a particular kind of
ExpressionMap
".As for the
ExpressionMap
specification, we also suggest to list the additional properties of Fields (e.g.,rml:fieldName
orrml:field
), instead of having them informally introduced in the text only.The text was updated successfully, but these errors were encountered: