-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hypergraph Interchange Format invitation #17
Comments
Thanks, that's a great idea, IMO, and I'll discuss it with our team. If I understand the schema correctly, we would have to represent all incidences here, though, so the file size would increase. This could become a problem for hosting the data, but we'll cross that bridge when we arrive on it. As side-note (I can also open an issue for this), it would be helpful to see an example of a simple hypergraph and its corresponding HIF representation. The repo currently does not contain any examples. |
Sounds great! I think these tutorials can help in case you haven't seen them:
I also notice you use the TopoX suite, and we started discussions with them as well. We have a minimal example of interoperability here: Expect more improvements in the docs soon as we write our paper, but here is a snippet about the encoding:
It would be great to have your feedback and you are welcome to open issues in our repository or send it my way. |
Thanks, yes, already taking a look at this! We'll be in touch! 😄 |
Hi! I'm Martín and I'm a developer working in the HIF project, an effort to share higher-order datasets developed by members of HyperNetX, XGI and other established higher-order network libraries.
I was just watching Bastien's talk, and found out about MANTRA. I see that the JSON format is important in this library but maybe you can still consider using the HIF standard JSON Schema. We are looking to expand the community (pszufe/HIF-standard#25) and it would be great to have you!
Let me know and I can give you more information. PS: we'll be at NetSci2025.
The text was updated successfully, but these errors were encountered: