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

Support for "provided sources" (was input stream as source) #91

Open
pmaria opened this issue Oct 8, 2024 · 1 comment · May be fixed by #95
Open

Support for "provided sources" (was input stream as source) #91

pmaria opened this issue Oct 8, 2024 · 1 comment · May be fixed by #95
Assignees
Labels
enhancement New feature or request proposal Proposal available for fixing this issue in the spec

Comments

@pmaria
Copy link
Collaborator

pmaria commented Oct 8, 2024

See discussion at #2 (comment)

The W3C Web Of Things vocabularies that are currently described in RML-IO are aimed at IOT data streams an hypermedia approaches of handling them. They are not a good fit for the purpose of describing a IO bytestream. Furthermore, there are more types of sources that could be provided to a RML processor programmatically, like e.g. an already deserialized JSON node or XML node etc. The options for this can vary across tech stacks and programming languages, so the proposal here is to shift the problem of handling the provided source type to the RML processor. Thus we provide a simple rml:Source type for provided sources:

Proposal:

[] rml:logicalSource [
  rml:source [
    a rml:ProvidedSource ;
    rml:sourceIdentifier "some identifier" ; 
  ] ;
] ;

A RML processor can then expose an API to be able to provide this source for mapping.

@pmaria pmaria self-assigned this Nov 9, 2024
pmaria added a commit that referenced this issue Nov 9, 2024
@pmaria pmaria linked a pull request Nov 9, 2024 that will close this issue
2 tasks
@DylanVanAssche DylanVanAssche added enhancement New feature or request proposal Proposal available for fixing this issue in the spec labels Dec 5, 2024
@DylanVanAssche
Copy link
Collaborator

Discussion moved to PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request proposal Proposal available for fixing this issue in the spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants