SPARQL Import as a separate extension (like it was at RoamJS.com) about developer HOT 1 OPEN

Absolutely, I understand where you're coming from with your suggestion to revert the SPARQL import to a standalone extension. Your points are valid, particularly regarding the ease of use for non-developers and the potential for increased visibility and user adoption.

Here's a bit of insight into why things are the way they are currently:

• Streamlining Development: One of the main reasons the extensions were consolidated was to streamline the development process. Maintaining a plethora of repositories can be quite taxing, especially with limited resources.

• Community Contribution: On the bright side, the open-source nature of our work means that community members are always welcome to contribute. If there's a general consensus that a separate SPARQL extension would be beneficial, anyone in the community can fork the relevant code and create it. We're all for community-driven initiatives that can enhance the ecosystem.

• Collaborative Opportunities: If this is a project close to your heart, and you're interested in spearheading the initiative to separate out the SPARQL functionality, I'm open to discussing freelance opportunities. ``

from developer.