[FEA]: Hypergraph Interchange Format invitation

[colltoaction]

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Hi, I'm a developer working in the HIF project, allowing hypergraphs to be shared across many libraries. I think it would be great for the Higher-order Network Science community to have support from the growing number of libraries for GPUs. I also think users of cugraph will greatly benefit from having access to higher-order datasets.

• https://github.com/pszufe/HIF-standard

I'm excited to see you already support hypergraphs, because this integration should be very straightforward. There are so far 4 well-established Python projects using HIF. You can take a look at the load/save methods that have been implemented:

• https://github.com/xgi-org/xgi/blob/main/xgi/convert/hif_dict.py
• https://github.com/pnnl/HyperNetX/blob/master/hypernetx/hif.py
• https://github.com/HGX-Team/hypergraphx/blob/master/hypergraphx/readwrite/hif.py
• https://github.com/Jpickard1/Hypergraph-Analysis-Toolbox/blob/main/Python/HAT/hypergraph.py#L561

Describe your ideal solution

def from_hif(json):
incidences = read_incidences(json)
nodes = read_nodes(json)
edges = read_edges(json)
return build_hypergraph(incidences, nodes, edges)

Describe any alternatives you have considered

As I mentioned the libraries above don't explicitly support GPUs, but the design of a language-independent interchange format can be a great foundation for collaboration.

Additional context

I hope you would consider taking a look at our repository where we provide the specification of a JSON format. It is an incidence-based encoding that is developed by members of HypergraphX, HyperNetX and XGI.

Let me know what you think and any way I can help make this happen!

Code of Conduct

• I agree to follow cuGraph's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request