From: Richard C. <ri...@cy...> - 2006-03-01 15:59:37
|
Geraint, On 1 Mar 2006, at 13:24, Geraint Edwards wrote: > Richard Cyganiak wrote: >> Oh, OK. Actually, there's a Mozilla bug filed for this: https:// >> bugzilla.mozilla.org/show_bug.cgi?id=106516 . Doesn't seem to get >> much attention. I voted for it. > > Yes - I found that after my message :-( > >> Why don't you take a stab at adding rdf:li support to the >> RdfSerializer? I'm sure that would benefit other folks as well. >> Look at writeDescriptions() and writeGroup() for a place to start. > > Yes - a generic rdf:li serializer should be straightforward. I'd > probably suggest adding a configuration constant to allow the switch? Sounds good to me. > My requirements are a bit more involved than just serialization > since I want Mozilla to pass back to the server information about > changes made to the datasource locally. I therefore need to make > sure that Mozilla is given enough information that it can pass back > to the server and allow me to identify and modify my DBmodel > statements as necessary. That's an interesting scenario. Would it work if you replaced the whole model on the server with the changed version from the Mozilla client? Just for the record, the RAP parser can deal with rdf:li just fine. > I'll certainly pass back to the community what I come up with as a > solution. since RAP seems like the ideal backend to a server based > Mozilla datasource. Let us know how it goes and if we can help. Richard > > Geraint > |