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

RML Function should be an IRI ? #199

Open
Yalz opened this issue Jun 22, 2023 · 1 comment
Open

RML Function should be an IRI ? #199

Yalz opened this issue Jun 22, 2023 · 1 comment

Comments

@Yalz
Copy link

Yalz commented Jun 22, 2023

Issue type: 🐛 Bug

Description

I have the following "toWkt" function I'm trying to call in my Java code.

mappings:
  loc:
    sources: locations-source
    s: https://www.wegenenverkeer.be/id/verkeersmetingen/meetpunt/$(./@unieke_id)/geo
    po:
      - p: geo:asWKT
        o:
        - function: ex:toWkt
          parameters:
            - [ex:coordinates, $(breedtegraad_EPSG_4326)]
          datatype: xsd:integer

However when I translate this using YARRRML (via Matey), the tripples linked to the function are as follows:

map:omexec_000 rr:constant "http://example.com/toWkt" ;
	rr:termType rr:IRI .

When using this in combination with CARML, this can not be parsed because it expects the function as an IRI instead of a String.

Is this a bug in the YARRRML or rather a limitation on the CARML implementation ?

Environment

yarrrml-parser v1.3.3
carml-engine 0.4.7

@bjdmeest
Copy link
Collaborator

it's not a bug in se (map:omexec_000 rr:constant "http://example.com/toWkt" ; rr:termType rr:IRI . should be equivalent to map:omexec_000 rr:constant <http://example.com/toWkt>), but I agree that the default translation should be adapted to make the RML shape more intuitive

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