Hello,
most of requirement tools that I know used a multi level tree structure to represente data and not a list (ReqIf, Doors, R4J, ...).
Lyo Model is based 3 levels Tree (project, requirement collection, requirement). So if we want to present the tree without a view, just to let user browse and understand data has they already know it, we need to keep order and level. I already have level in my system but I loose the order information just because the data structure doesn't keep order.
If I weel understand you, you don't want to keep the order. Because RDF don't want it by nature. Is that it ?
But it's force user to query a second time the server to get the order.
For exemple, I see this post, where doors user query twice time Doors with internal api to get the order after getting data from OSLC :
I am sorry, maybe we don't have the good approach. But I don't understand why OSLC must loose this information.
Because as OSLC client, it's interesting to show data as they really are in server.
I am really sorry, because my understanding of Lyo is maybe wrong ... For me this tools/ protocol help us to connect data between cross domain application.
Could you help me ? Must I use other approach ?