You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
A RML processor can then expose an API to be able to provide this source for mapping.
The text was updated successfully, but these errors were encountered: