Hi Team, "Steve's suggestion in [1] was to change the vocabulary name from "Common Resource Type Vocabulary" to "Common IT Resource Type Vocabulary", but if Core has another that it feels is clearer I suspect that would be agreeable as well. In anticipation of the "why not call it Reconciliation?" question, the simple answer is that Tivoli expects these resource types to be widely re-used across multiple domains, with reconciliation being merely one of those. The Performance Monitoring WG is already re-using several terms, despite having no need for reconciliation itself. "
2 Questions: Q1) There is 0 guarantee that the set of resource types defined by current of future OSLC domains will restrict themselves to IT resources only. Why would we change the name of a common vocabulary, where the intent of that common vocabulary is to be widely re-used across multiple domains, to a name that inherently pigeonholes the purpose and scope to an IT-centric set of resources? Q2) The Common Resource Type Vocabulary currently contains resource definitions that represent non-IT resources. Will there be an action to delete these resource types from the Common Resource Type Vocabulary, upon name change? If a deletion does occur, is there another common vocabulary that will be in use to contain these resource definitions? What is the proposal to handle conditions where there are common resource definitions that have both an IT and non-IT perspective? http://open-services.net/ns/crtv#Asset http://open-services.net/ns/crtv#Location http://open-services.net/ns/crtv#Path http://open-services.net/ns/crtv#ServiceInstance [1] http://open-services.net/pipermail/oslc-recon_open-services.net/2012-November/000010.html Regards, Jacob Jacob Yackenovich Tivoli Software | IBM | Research Triangle Park, NC [email protected] | (919) 224-1373
