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

YARRRML Lessons learned #57

Open
bjdmeest opened this issue Jul 14, 2022 · 2 comments
Open

YARRRML Lessons learned #57

bjdmeest opened this issue Jul 14, 2022 · 2 comments
Labels
UCR Issue on Use Case/Recommendation

Comments

@bjdmeest
Copy link

Hi all, this is just a way to present some lessons learned we had when developing YARRRML:
a DSL that translates to (R2)RML, a mapping langauge that converts heterogeneous data sources to RDF.
Although the goal of YARRRML (a developer-friendly DSL to write RML documents that happen to be in Turtle) is different from YAML-LD,
it is at least a bit related :). Some things we encountered:

  • Using ~ as a convencience to 'tag' specific values, e.g., to specify, when mapping a value to a node, to map it to a literal (http://example.com/homepage~literal => "http://example.com/homepage") or an iri (http://example.com/homepage~iri => <http://example.com/homepage>). (we did not use _ since this might confuse users with blank nodes somehow), see eg https://rml.io/yarrrml/spec/#tabs-19. Also related to Choose prefix character to replace @ #55
  • A limitation of YAML we encountered was not being able to refer to another YAML-document. We had to include a mechanism to 'combine' multiple YAML files and handle external values (see https://github.com/RMLio/yarrrml-parser#yarrrml-parser-1)

If it makes sense to take this into account for YAML-LD, happy to continue the discussion!
If irrelevant, feel free to close this without further ado ;)

@gkellogg gkellogg added the UCR Issue on Use Case/Recommendation label Jul 14, 2022
@VladimirAlexiev
Copy link
Contributor

related to #19

@ioggstream
Copy link
Contributor

ioggstream commented Jul 18, 2022

Not advocating the use of $(DANGEROUS BASH COMMAND) in documents :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UCR Issue on Use Case/Recommendation
Projects
None yet
Development

No branches or pull requests

4 participants