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
Should we store graphs? I think that for synthetic graphs (worst case, sparse-to-full) we should create generators. Also, I think that for real-world data we should provide converters to our format, instead of converted graphs storing.
The text was updated successfully, but these errors were encountered:
In our implementation (https://gitlab.com/ciromoraismedeiros/rdf-ccfpq) we use python functions for generating synthetic graphs. Here's a sample for generating complete graphs (n is the number of vertices):
def new_complete_graph(n, predicates):
graph = Graph()
for i in range(1,n+1):
s = str(i)
for p in predicates:
for j in range(1,n+1):
o = str(j)
graph.add(s,p,o)
return graph
Is that what you are looking for?
As for the data format, I believe we should make our implementations able to read any RDF format.
That is easily achievable in Python with RDFLib (https://pypi.org/project/rdflib/).
Should we store graphs? I think that for synthetic graphs (worst case, sparse-to-full) we should create generators. Also, I think that for real-world data we should provide converters to our format, instead of converted graphs storing.
The text was updated successfully, but these errors were encountered: