Dragos, I don't think we should require the use of Reportable REST for configuration resources.
I was going to suggest that OSLC recommend that service providers support non-abbreviated RDF/XML so RPE could consume configuration resources. However, after thinking about it more, this wouldn't solve the problem since RPE also requires an XML Schema. The schema for non-abbreviated RDF/XML is not very useful. What do you think? Would it be consumable? Perhaps the best way forward is for RPE to start consuming RDF, and using RDF2XML mapping to produce consumable XML? Regards, ___________________________________________________________________________ Arthur Ryman, PhD Chief Data Officer, Rational Chief Architect, Portfolio & Strategy Management Distinguished Engineer | Master Inventor | Academy of Technology Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: Dragos Cojocari/Romania/IBM@IBMRO To: Arthur Ryman/Toronto/IBM@IBMCA, Date: 05/27/2014 07:37 AM Subject: Configuration Reporting Subteam - RPE Progress Hey Arthur, I am not able to join the call today due to offline appointments I made to prepare for Innovate so I will provide my update here: 1. We have successfully made and end to end test of configuration aware document generation with RPE 1.3 and RQM 5.0.2. Example PDF documents, slides showing the process outline as well as a 4 minute video documenting the entire process are available here: https://jazz.net/jazz04/resource/itemName/com.ibm.team.workitem.WorkItem/46027 For the tests I have used the SSE PLE image prepared for Innovate. There are a few bugs in the QM version I used for the demo but they are fixed in the RQM dev stream. 2. The configuration information is interesting for the docgen scenario. I expect that report authors will often want to include in the document details on the exact configuration used ( see the PDFs I generated). For this example I created an XSD schema for the OSLC representation of the configuration but we need to standardize the Configuration resources and see if this information should be made available through the Reportable REST APIs. Regards, Dragos
