Please raise any concerns, looking for feedback. I wanted to make sure OSLC-CM 2.0 implementers are aware of this change. This affects all 2.0-based XML representations: ChangeRequest, ServiceProviderCatalog, ServiceProvider, etc.
To be clear, OSLC's RDF/XML constrained format for a ChangeRequest would look like: <?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/terms/"; xmlns:oslc="http://open-services.net/ns/core#"; xmlns:oslc_cm="http://open-services.net/ns/cm#"; xmlns:ex="http://example.com/bugtracker";> <oslc_cm:ChangeRequest rdf:about="http://example.com/bugs/2314";> <dcterms:title> Provide import </dcterms:title> ...end so on Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 > From: Dave <[email protected]> > To: oslc-core <[email protected]> > Date: 06/30/2010 02:58 PM > Subject: [oslc-core] Meeting notes and using rdf:RDF as root element > Sent by: [email protected] > > I posted some notes on the Core meeting agenda page for today: > http://open-services.net/bin/view/Main/OslcCoreMeetings20100630 > > One of the topics we discussed today was Link Guidance and the fact > that the proposed form for "link annotated with property-values" > requires <rdf:RDF> as the root element of OSLC Defined Resource > representations. > > We discussed the impact of this change on implementations now > in-flight and those moving from v1 to v2 and agreed that this change > is late-breaking but not too late. If we wait a week, it may be too > late so we agreed to get this change in now and then socialize and > gather feedback. > > The change is now in the Core spec draft as well as the RDF/XML and > Atom representation examples: > http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT > http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixBDRAFT > http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixEDRAFT > > Feedback is most welcome. > > Thanks, > - Dave >
