is there a way to use `@container:@list` with custom props?

[VladimirAlexiev]

iirds-consortium/models#19

iiRDS is an important spec for Intelligent Documentation using RDF metadata.
https://www.iirds.org/fileadmin/iiRDS_specification/20231110-1.2-release/index.html#example-43 shows the structure of iirds:DirectoryNode that makes the sequential and hierarchical structure of a document.
Currently it's defined as RDF/XML, but the next release will include JSON-LD.

As you can see, it uses a custom list structure instead of the standard rdf:List.
Is there a way to trick JSON-LD into supporting @container:@list with custom list props?
I suspect that no, so is it feasible to modify JSON-LD to support such use case (@gkellogg)?

Note: reading the iiRDS spec more closely https://www.iirds.org/fileadmin/iiRDS_specification/20231110-1.2-release/index.html#x6-9-1-directory-nodes, the mapping is not so clean because iirds:DirectoryNode are not pure list items:

• may contain data: rdfs:label and iirds:has-directory-structure-type
• may not point to data: iirds:relates-to-information-unit (the analog of rdf:first) is optional
• may point to a lower-level list (has-first-child)

So I'll cancel the original issue iirds-consortium/models#19

[gkellogg]

We discussed the idea in 1.0, when alternative list formats were emerging (e.g., Ordered List Ontology), but it didn't go further.

While this is something that could technically be done, I don't think our charter will be open to these types of changes, but it's worth discussing on a call sometime; we can add a topic for that on a future call.