We can try to extend the concept of pattern to include such thing as annotation role which is optional and is included into templates when the pattern is expanded.

Had you met the next big guy on SW block - http://www.w3.org/TR/json-ld/

It is designed to express patterns.

Andy, The question of defaultRdsId for metatemplate instances was discussed on one email thread in September 2013. I've provided the following reasons for my implementation: Yes, no separate identification of the Description and RoleDescription instances. I've always thought about ID Spec in this wa...

Adding any kind of qualification by any means to the template instance will not help you with the basic fact -- template instance with a missing role is not a valid predicate under the P7 and can not be expanded. So there are no need for special meta property - verification code can find all templat...

I'm surprised you haven't added identities to the meta definitions since your stating you are relying heavily on these. Sorry, don't understand this. All metatemplate instances in the example above are identified: <p7tm:TemplateDescription rdf:about="#Classification__desc"> <p7tm:TemplateRoleDescri...

Another important example envisioned by Jan Glendinning and still never really implemented: To make a mapping as simple for domain expert as possible, we can define something like ParentChildPattern. And have a rule engine in the adaptor which can decide which complex data modeller's concept it is -...

collecting these three specialized templates in an instance of the template EnumeratedSetOf3Classes (http://www.15926.org/templatespecs/CL-SETOP-04.xml) with the Name "Test Pressure" Yes, except for two other aspects (not yet used in iRING User Group TIP mappings, but envisioned in JORD TSPs): 1. R...

Andrew, do you mean my identifiers for generic patterns, like "ClassificationOfContentOfPartInAssembly"? I had an intention to keep them informative from a datamodelling point of view, not engineering. Generic patterns are used in the process of TIP design and approval, not in the mapping. To ensure...

The reason I can't just list all subclasses of #BaseTemplateStatement is because other subclasses exist that are not Template definitions. I hope there will be none! But I agree that OWL part of the definition should be more rigorous to allow automated reasoning and verification. From the practical...

This means that they are not in the scope of ISO 15926, or perhaps in some future new Part of it (probably competing with Part 11). This means it is still on the implementation side, not standardised. The fact that implementation is synchronised between at least 3 teams gives a good chance that fut...