Re: RDF being phased out?

"rvj" <[email protected]> Mon, 7 Apr 2008 18:20:08 +0100
Newsgroups gmane.comp.mozilla.devel.rdf
Message-ID <[email protected]>
In  milarity terms I guess RDF might be called "forlorn hope" however I had 
still hoped that Mozilla's RDF would offer  an alternative approach to the 
redundancy of SQL field duplication

In fact my main concern over the last couple of years has been  whether RDF, 
or the  template generator would be able cope with normal CSS styling (I 
still dont know how style the currently selected item in a listbox with 
selected item icon).
Ive belated discovered how to do this but its not exactly been apparent 
through Mozilla documentation.

Am I correct in thinking  that the equivalent of RDF flush() is now 
officially available in Mozilla for XML  files
(presumably SAVE) ?












"Axel Hecht" <[email protected]> wrote in message 
news:[email protected]...
> rvj wrote:
>> just when I thought things were pretty stable....
>>
>>
>> any reasons why RDF to be phased out .... and what will replace it?
>>
>
> There are design bugs in our impl, and the impl never caught up with any 
> RDF standard, so we have a few bugs that are incredibly hard to fix, and a 
> plethora of not-backwards compatible changes to get the RDF testsuites to 
> pass.
>
> The first bucket wasn't tackled before we phased RDF out, the latter is 
> hard to do without.
>
> As for replacements, people like sql and json.
>
> Axel
>
>> "Axel Hecht" <[email protected]> wrote in message 
>> news:[email protected]...
>>> Fernandez, Sylvester J wrote:
>>>> Hi,
>>>>
>>>> I hear that use of RDF will be phased out in the future. Where can I
>>>> find out more about this development?
>>>>
>>> It depends. There are various different usages for RDF. Templates would 
>>> be one, the docs for the new stuff for that are on MDC. Then the stuff 
>>> that mailnews does wrt to RDF in Addressbook and friends, the rip out of 
>>> that is part of the tb 3 design plan.
>>>
>>> Basically, RDF is phased out, but still used all over, so we're 
>>> gradually moving over to not using it. That isn't really an overall 
>>> plan, but more of an agenda, that's happening at the pace of the 
>>> particular code pieces.
>>>
>>> Axel
>>