I think the concept of inline tagging is mostly good, but the practice is flawed. 

Where in bundle we use a high-water mark at the bundle level to indicate the highest content contained... there should be a similar high-water mark in the resource holding inline tagging. YET, if this was done with the .meta.security; then the inline extension would have nothing to do as .meta.security applies to everything. 

SO, I previously indicated that the extension has-inline-security-label should be replaced with a code in .meta.security..... I still think there should be a code... but now find a use for this root level extension. The root level extension should be of datatype CodeableConcept at 1..*; and hold the high-water mark. 

But, I am not sure this works either... as the Resource as handled by an application unaware of inline tagging needs to be told that the resource is high-water mark sensitive.

I am not convinced that this model will work except in an environment where policy indicates that inline will always be used, thus no need for a "has-inline...".