Done.
On Thu, Apr 21, 2011 at 1:04 PM, Dave <[email protected]> wrote: > There is an error and an opportunity for clarification in the last > example of the OSLC Core spec Appendix C: > http://open-services.net/bin/view/Main/OslcCoreSpecAppendixLinks > > The example illustrates the anti-pattern of inlining values about one > resource within another resource, and it currently looks like this: > > <oslc_blog:attachment rdf:about="http://example.com/attachments/2"> > <oslc_blog:UploadedFile> > <dcterms:title>apache-wink-incubating-0.9.6.jar</dcterms:title> > </oslc_blog:UploadedFile> > </oslc_blog:attachment> > > The error is the placement of the rdf:about attribute, which should be > on the oslc_blog:Uploaded element. And the example could be clarified > by making it complete and showing the whole resource that contains the > property value, or at least the skeleton of the resource, for example: > > <rdf:RDF xmlns:oslc_blog="http://open-services.net/ns/bogus/blog# > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> > > <oslc_blog:Entry rdf:about="http://example.com/blogs/entry/5"> > > <dcterms:title>New Wink release available</dcterms:title> > > <!-- other property values --> > > <oslc_blog:attachment> > <oslc_blog:UploadedFile > rdf:about="http://example.com/attachments/2"> > <dcterms:title>wink-0.9.6.jar</dcterms:title> > </oslc_blog:UploadedFile> > </oslc_blog:attachment> > > </oslc_blog:BlogEntry> > > </rdf:RDF> > > Unless the workgroup has some objection(s), I'll go ahead and make > this correction and clarification after the upcoming weekend. > > Thanks, > Dave >
