bossenti opened a new issue, #1373: URL: https://github.com/apache/streampipes/issues/1373
### Body Although, we have a dedicated [vocubalury ](https://github.com/apache/streampipes/tree/dev/streampipes-vocabulary) that provides extensive definitions of several [domain properties](https://streampipes.apache.org/docs/docs/extend-sdk-stream-requirements.html#specifying-semantics) and other stuff, we have plenty of places in our code where we still have hard coded domain properties. One example can be found [here](https://github.com/apache/streampipes/blob/dev/streampipes-extensions/streampipes-processors-geo-jvm/src/main/java/org/apache/streampipes/processors/geo/jvm/jts/processor/epsg/EpsgProcessor.java#L55). ### Tasks - [ ] collect hard-coded domain properties - [ ] extend (and rework) vocabulayry - [ ] replace hard-coded domain properties by vocabulary - [ ] (extend vocabulary by common runtime names, see https://github.com/apache/streampipes/discussions/1265) ### Mentoring As this issue is marked as good first issue: one of @dominikriemer, @tenthe, or @bossenti are happy to provide help for getting started, just tag (one of) them if you want to start working on this issue and need some help. This issue is ideal for people that are interested in getting started with StreamPipes and its SDK. Related: https://github.com/apache/streampipes/discussions/1312 ### StreamPipes Committer I acknowledge that I am a maintainer/committer of the Apache StreamPipes project. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
