On Tue, Jan 8, 2019, at 7:43 PM, Christanto Leonardo wrote: > > ``` > + /mycontent2 > - jcr:primaryNodeType = "nt:unstructured" > - sling:resourceType = "my/page" > - my:created = "2019-01-01T00:00:00Z" > - my:title = "Title 1" > ``` > > Here, you simply define a DataModel for `/apps/my/page` having my:created > and my:title properties. > So when other code inspect the resource (/mycontent2) using DataModel, it > will get Property instances for my:created and my:title. >
Okay, I think I'm getting there, it's just that we have a difference in terminology. Your idea is along the lines of being able to define a set of values that is exposed for a given resource. When I talk of a Type, it's not just a definition of what is there, it's the enforcement of those values. So in defining a "sling:type" of "folder" I expect to be able to define what values must be provided in order to create a resource of that type and that is respected without regard to the ResourceProvider that is responsible for that location.
