[Oslc-Automation] State and Verdict Names
Rohit Shetty
rohit.shetty at in.ibm.com
Thu Jan 24 13:37:42 EST 2013
+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: rohit.shetty at in.ibm.com
Find me on: and within IBM on:
Embassy Golf Links Business Park, Block B
Bangalore, Karnataka 560071
India
From:
John Arwe <johnarwe at us.ibm.com>
To:
oslc-automation at open-services.net
Date:
01/24/2013 09:01 PM
Subject:
Re: [Oslc-Automation] State and Verdict Names
Sent by:
"Oslc-Automation" <oslc-automation-bounces at open-services.net>
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
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1588 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 470 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 467 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment-0002.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 494 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment-0003.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2404 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130125/c2128165/attachment.gif>
More information about the Oslc-Automation
mailing list