Hello, At the IETF 105 Netmod meeting it was stated that the flexible solution to define the context schema inline (requested earlier on the mailing list) is quite complex, so a fourth simpler method to define content schema inline is needed.
The fourth method would add one more choice to choice content-schema-spec
case simplified-inline {
leaf-list module {
type string {
pattern '.+@\d{4}-\d{2}-\d{2}\.yang';
}
description The list of content defining YANG
modules including the revision date for each.
Usage of this leaf-list implies the modules are
used without any deviations and with all features
supported.;
}
}
An example instant data example could be:
<instance-data-set xmlns="urn:...:ietf-yang-instance-data">
<name>read-only-acm-rules</name>
<module>[email protected]</module>
<module>[email protected]</module>
<revision>
<date>1776-07-04</date>
<description>Initial version</description>
</revision>
<description>Access control rules for a read-only role.</description>
<content-data>...
Do you like it ? Adding this case are you OK with the content-schema-spec
definition?
Regards Balazs
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
