use of data module

[thhck]

I'm puzzle by the <pos-label /> and <pos-description />

If I understand well there is some magic guessing which predicate to use in the Think object:

https://github.com/pod-os/PodOS/blob/ad2ea7b7e30805d212cc618affd660c387d69e3e/core/src/thing/Thing.ts#L128C1-L140

Would this be replaced with data module at some point ?

[angelo-v]

Yes, both elements consider several well known predicates that could be used as a label or description.

Not sure if this should be part of a data module. Data modules are supposed to be domain specific, but this is very generic logic. On the other hand similar logic is also present in SolidOS and perhaps it could be useful for other apps as well, so it might make sense to have a generic data module.

[josephguillaume]

There's anyway the generic pos-value where the predicate needs to be specified. Similarly, pos-picture has pos-image (though it take uri rather than predicate). Perhaps the documentation needs to point out the equivalence.

The way I think about it, PodOS core and data modules provide higher level abstractions where the user doesn't need to think about specific predicates to use. Some elements use these higher level abstractions, and some use low level UI data binding, e.g. with the predicate attribute.

Thing currently only allows read-only access to linked labels, descriptions and pictures. When providing write access, it'll be necessary to select which predicate to use. At that point it might be useful to have a (core) data module or at least a means of specifying a shape to use.