It does. You have to treat the node+extension as a new node type, but the
"isA" mechanism allows browsers to transparently ignore the extension fields.
An extended WWWInline would look something like:
WWWInlineWithExtensions {
fields [ SFString name, MFString isA, MFString hints,
MFString genericRepresentations ]
name "http://....."
isA "WWWInline"
hints [ "Cache", "SomeOtherHint" ]
genericRepresentations [ "http://....", "http://...." ]
}
Browsers that don't have a WWWInlineWithExtensions should treat it as a
regular WWWInline (the next alpha of WebSpace should support isA; previous
versions ignored it).