Weave Code
Provides a SparQl client.
Frequently asked questions about Schema Api
- Can I use this package directly in Laravel without Symfony?
- No, this package is Symfony-centric and requires a wrapper or facade. You’ll need to manually bind the client in Laravel’s service container and handle HTTP calls (e.g., with Guzzle or Symfony’s HttpClient). Start with a custom service class to abstract the Symfony dependencies.
- What Laravel versions and PHP requirements does this package support?
- The package itself has no Laravel-specific dependencies, but it requires PHP 8.1+ (for Symfony’s HttpClient). Laravel 10+ is fully compatible, but you’ll need to adapt the Symfony-based client for Laravel’s DI system. Test thoroughly with your Laravel version.
- How do I configure SPARQL endpoints for query vs. update operations?
- Define `query_endpoint` and `update_endpoint` in your Laravel config (e.g., `config/services.php`). For Blazegraph or Oxigraph, both can share the same URL. Authentication (Basic Auth, API keys) must be handled via HTTP client middleware or endpoint-specific configs.
- Does this package support SHACL validation for data governance?
- Yes, the package includes SHACL validation via a dedicated endpoint. Configure the `shacl_endpoint` in your config and use the validator methods (e.g., `validate()`) to enforce constraints. Note: SHACL requires additional setup (e.g., TopBraid or Apache Jena).
- How do I map SPARQL results to Laravel Eloquent models?
- There’s no native Eloquent integration. Manually parse SPARQL results into arrays and hydrate them into models using Laravel’s `Model::create()` or `Model::firstOrCreate()`. For complex mappings, consider a hydrator library or a hybrid approach (e.g., GraphQL for frontend + SPARQL for backend).
- What are the performance implications of SPARQL queries in production?
- SPARQL queries can be resource-intensive, especially with large knowledge graphs. Benchmark your endpoints (e.g., Blazegraph/Oxigraph) and implement retry logic with circuit breakers for unreliable endpoints. Optimize batch operations and avoid over-fetching data.
- Are there alternatives to this package for Laravel SPARQL support?
- Yes, consider `spatie/sparql` for a Laravel-native solution with lower integration friction, or use Laravel’s HTTP client directly with raw SPARQL strings for simpler use cases. If you need full SPARQL 1.1 compliance, this package is the most feature-rich but requires more setup.
- How do I handle authentication with SPARQL endpoints (e.g., Wikidata)?
- Configure authentication in your HTTP client (e.g., Guzzle middleware or Symfony’s `HttpClient`). For Basic Auth, use the `auth()` method on the client. For API keys, pass them as headers in the request. Store credentials securely in Laravel’s `.env` file.
- Can I use this for traditional relational data (e.g., MySQL tables)?
- No, this package is designed for semantic data (RDF/OWL graphs). For relational data, use Eloquent or Laravel’s Query Builder. SPARQL is overkill for CRUD operations and lacks the performance optimizations of SQL databases.
- What’s the best way to test SPARQL queries in Laravel?
- Mock the SPARQL client in unit tests using Laravel’s `Mockery` or PHPUnit. For integration tests, use a Dockerized SPARQL endpoint (e.g., Oxigraph) and assert query results against expected RDF triples. Avoid hitting third-party endpoints in tests to ensure reliability.
Weaver
How can I help you explore Laravel packages today?