ontolog-forum
[Top] [All Lists]

Re: [ontolog-forum] RDF vs. EAR

To: "[ontolog-forum]" <ontolog-forum@xxxxxxxxxxxxxxxx>
From: Duane Nickull <duane@xxxxxxxxxxx>
Date: Tue, 06 Dec 2011 10:21:36 -0800
Message-id: <CB039C88.AD65%duane@xxxxxxxxxxx>
Ah - WRT to RDF/XML parsers, I have to agree.  It is not the parser per se
but the mandatory registered callbacks for specific events such as
encountering an RDF triple in the raw parse stream.    (01)

Duane 
________________________________________    (02)

Überity.com
Principal Data Architect &
Adobe LiveCycle ES Consultant Services
http://www.uberity.com
Blog | http://technoracle.blogspot.com
Twitter | @duanechaos    (03)





On 11-12-06 9:30 AM, "Kingsley Idehen" <kidehen@xxxxxxxxxxxxxx> wrote:    (04)

>On 12/5/11 11:15 PM, Duane Nickull wrote:
>> On 11-12-05 5:45 PM, "Kingsley Idehen"<kidehen@xxxxxxxxxxxxxx>  wrote:
>>
>>> Yes, but for bootstrap at InterWeb scale, it hasn't worked. Today's
>>> developer aren't ready to absorb the cost of parser development
>>> especially in the Open Source era where purchasing commercial quality
>>> grade libraries isn't the preferred options. People really like the
>>> "Free" part of the "Freedom" aspect of Open Source. Basically, they
>>>want
>>> the "Free Beer" and that's where XML parser problems start.
>> DN: I have to disagree with this.  I've worked in the commercial
>>software
>> industry since XML was a recommendation in 1998 and have worked on
>> numerous solutions around B2B.   The most widely used XML parsers are
>> FOSS.  Xerces, JDOM et al for Java are driving most large businesses XML
>> parsing requirements. Almost every language has good XML capabilities.
>
>Correct!
>
>I should have said: RDF/XML parsers. That's the nightmare.
>
>>
>> The main cost of XML interchange is mapping the instance data to the
>> business services based on its' semantics.
>
>As per my statement above, I should have been clearer, the context of my
>XML comments was really RDF/XML.
>
>We have built our own XML parsers and also evaluated those of others.
>When used appropriately XML is very useful.
>
>Links:
>
>1. http://www.ohloh.net/p/4186/analyses/latest -- one of our FOSS
>projects, note the XML percentile re. source code (circa. 1998 we
>developed DBMS hosted XML and XSLT parsers prior to eventual open source
>release) .
>>
>> Duane
>> _
>>
>> Überity.com
>> Principal Data Architect&
>> Adobe LiveCycle ES Consultant Services
>> http://www.uberity.com
>> Blog | http://technoracle.blogspot.com
>> Twitter | @duanechaos
>>
>
>
>-- 
>
>Regards,
>
>Kingsley Idehen        
>Founder&  CEO
>OpenLink Software
>Company Web: http://www.openlinksw.com
>Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>Twitter/Identi.ca handle: @kidehen
>Google+ Profile: https://plus.google.com/112399767740508618350/about
>LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>
> 
>_________________________________________________________________
>Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>Shared Files: http://ontolog.cim3.net/file/
>Community Wiki: http://ontolog.cim3.net/wiki/
>To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>     (05)



_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J    (06)

<Prev in Thread] Current Thread [Next in Thread>