Open k00ni opened 7 years ago
Cool idea, but I think for this we should be able to tell, that our interfaces are actually of use. So we need some evaluation resp. real applications using it.
Main argument would be to support/enable interoperability of different RDF implementations like EasyRdf, ARC2, hardf or even Redland. All use different formats, some simple arrays, some class-based.
I started with a basic file: https://github.com/SaftIng/fig-standards/blob/psr-rdf/proposed/rdf/rdf.md
Link to a discussion about hardf supporting this standard too: https://github.com/pietercolpaert/hardf/issues/14
I proposed my current working draft on the PHP-FIG mailing list: https://groups.google.com/forum/#!topic/php-fig/Z1dds-mBRrE
Current state of interfaces:
For each interface, except Node, an example implementation is available. Related code is located in this repository: https://github.com/SaftIng/PsrRdf
I started a discussion with the maintainers of
with regards to support standardized RDF interfaces. With hardf this makes all major RDF libraries.
EDIT: Added hardf Link.
@k00ni thanks for championing this work for so long! I'm sorry to see it seems to have stalled (re: https://github.com/php-fig/fig-standards/pull/958).
FWIW, there may be some opportunity to revisit this under a different banner--but with the same goals. Several of the JavaScript RDF implementers formed the RDF.js Community Group at the W3C: https://www.w3.org/community/rdfjs/ They're working now to revitalize the community by combining code efforts, and working toward revising/publishing the Interface Specification: RDF Representation (which is currently focused on JavaScript...obviously :wink:).
It might be worth working with that community to reignite your efforts for a common interface across the PHP libraries. Bonus points (for everyone!) if these mostly match across languages too! 😄
At any rate, just wanted to thank you for your efforts.
Cheers! 🎩
@BigBlueHat Thank you!
@white-gecko: I would like to propose major Saft/Rdf interfaces to php-fig to see, if we can set a standard here, about how to model RDF triples, statements and quads.
It would be about:
Maybe adding further interfaces, like StatementIterator, or even example implementations?
Reason: I talked with the hardf, EasyRdf and ARC2 developers and i would like to suggest a common ground for future development. A contract how to describe RDF would be a good start.
What you think?