We had a recent case of this with RM, where they wanted to add new vocabulary to define some relationship inverses that they discovered were needed after finalization. For new specs and for new links in existing vocabularies, when the expected target in the "forward" direction is an OSLC-defined resource, is there a current consensus on whether it is better to define an inverse link in advance of a concrete scenario versus requiring clients to query for that information and/or approaching the relevant working group to extend the domain vocabulary with the inverse only after someone articulates a concrete scenario?
Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
