Intermediate templates

[Sebastiano-G]

To satisfy the constraints of complex models while preserving the usability and user-friendliness of the product, Template creators should be allowed to define multiple linked Templates (referring to different classes) to be associated with a single Web form. In other words, the end-user should be able to generate multiple Records (with different Classes) by filling a single form.

For instance, let's consider the following example about the modelling of provenance information with CIDOC-CRM:

<https://example.com/work/663763> a crm:E22_Man-made-object ;
     crm:P24i_changed_ownership_through <https://example.com/acquisition/22734637> ;
     crm:P24i_changed_ownership_through <https://example.com/acquisition/22734638> ;
     crm:P24i_changed_ownership_through <https://example.com/acquisition/22734639> .

<https://example.com/acquisition/22734637> a crm:E8_Acquisition ;
    crm:P22_transferred_title_to <https://example.com/person/223> ;
    crm:P4_has_time-span <https://example.com/acquisition_timespan/0466456> .

<https://example.com/acquisition_timespan/0466456> a crm:E52_Time-Span ;
	crm:P81a_end_of_the_begin "1640-01-01"^^xsd:date ;
	crm:p81b_begin_of_the_end "1862-12-31"^^xsd:date .

Instead of filling in three different forms (Man-made-object; Acquisition; Time-Span), the end-user will need to select the Man-made-object Template, fill in a "Time-span of the Acquisition" input field, and save the data. The system will automatically process it and generate three separate Records (one for each class).