+1 for that Regards,
Rohit Shetty Architect - Manageability Integration, IBM Master Inventor Tivoli, Software Group, IBM Phone: 91-80-41055478 | Mobile: 91-98866-26248 E-mail: [email protected] Find me on: and within IBM on: Embassy Golf Links Business Park, Block B Bangalore, Karnataka 560071 India From: John Arwe <[email protected]> To: [email protected] Date: 01/24/2013 09:01 PM Subject: Re: [Oslc-Automation] State and Verdict Names Sent by: "Oslc-Automation" <[email protected]> For the record, I think making them terms is a miss on our part. I do agree that it's not worth being disruptive to implementations at this point. It seems like we *could* update the vocabulary, either outside of a domain spec train or in the next versioned revision of spec+vocabulary. What I'm thinking of as a vocabulary-level solution is, for each current lower-case-started "term" like http://open-services.net/ns/auto#new , add a new rdfs:Class (in this case, ...#New) with the same semantics. Making it a Class allows others to subClass it, which is one way to demonstrate consistency amongst objects when the same predicate occurs in multiple triples. We might also make #new a subclass of #New assuming that is possible compatibly. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
