If you're using JavaScript for writing to a HTML Attribute, look at the .setAttribute and [attribute] methods which will automatically HTML Attribute Encode. Those are Safe Sinks as long as the attribute name is hardcoded and innocuous, like id or class.

Yeah, "virtual attribute" seems like dated terminology to me, so conceptually just a method.

I see a 'virtual attribute' as something we're forced to implement when using frameworks, ORMs and the like. Something that lets us inject our code into the path of whatever metaprogramming has been put in place for us. In a simple PORO like this, I don't see how it has meaning; it's just a method. :)

has_sauce is a "virtual attribute", a characteristic of the model that's dependent on the underlying toppings attribute.

This isn’t to say that multiplying code is good or bad – it’s a characteristic of all code regardless of quality.

There is also a need for mechanisms to support transformations and processesover time, both for scientific data and scientific ideas. These mechanisms should not only help the user visualize but also express time and change.

Temporal Data and Data Temporality: Time is change, not only ord

Traditional approaches to information processing present ‘‘information’’as given, well-defined and stable.