Just mentioning that this Value Object Descriptor approach seems to be expanding scope beyond adding types to VRS for loquacious exchange based on the conversation we had with VA today. It seems like its more of an independent spec that can be used with or without VA (maybe this belongs within schemablocks?).
Anyway, before this takes firm root we may want to consider the scope of this spec and either constrain it or cleverly rename/refactor the acronym to reflect that scope. I do love the name though, but it should provide the right context.
i like vrsatile. so i'm closing this. we can always say that it originated because of the VRS need for such a versatile solution and that's why it covers more than VRS. anyway, i'm closing this
Just mentioning that this Value Object Descriptor approach seems to be expanding scope beyond adding types to VRS for loquacious exchange based on the conversation we had with VA today. It seems like its more of an independent spec that can be used with or without VA (maybe this belongs within schemablocks?).
Anyway, before this takes firm root we may want to consider the scope of this spec and either constrain it or cleverly rename/refactor the acronym to reflect that scope. I do love the name though, but it should provide the right context.