[Oslc-pm] Swag at on-going example re-cast to re-use ems:metric

[John Arwe]

Attached this time; today's wg call learned me ;-)

http://any23.org/ has a converter for those preferring other formats.
Given how blank nodes "look" in RDF/XML, you might/not like that over 
Turtle now ;-)
Especially since the converter is overly aggressive about splitting up the 
RDF/XML and is making it UNabbreviated.
I did clean up this XML to be easier on the eyes.  NB: any23 does not 
supply xmlns bindings, you'd have to add those back in if you want to 
validate the XML.

I used pm:NewXXX where I don't see anything directly re-usable from the 
EMS WG.
What is attached is notionally == to what we discussed on today's call/in 
[1] 




[1] 
http://open-services.net/pipermail/oslc-pm_open-services.net/2012-June/000023.html


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20120620/1ff2ce4d/attachment-0015.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20120620-PerfMonRec-002.ttl
Type: application/octet-stream
Size: 1574 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20120620/1ff2ce4d/attachment.ttl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20120620-PerfMonRec-002.xml
Type: application/octet-stream
Size: 1308 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20120620/1ff2ce4d/attachment.xml>