I second this. There is a danger that tools will lock themselves in one form of rdf/xml even though there are many possibilities, let along the fact that rdf should not be thought of as an XML language
Simon Helsen, Ph.D. Advisory Software Engineer - Jazz Foundation Server Phone: 1-416-225-5717 | Mobile: 1-647-966-8280 E-mail: [email protected] From: Arthur Ryman/Toronto/IBM@IBMCA To: Dave <[email protected]> Cc: [email protected], [email protected], [email protected] Date: 06/20/2011 03:11 PM Subject: Re: [oslc] Seeking feedback on draft SDK proposal Dave, I took a quick look. One item popped out at me. Why are you suggesting we use JAX-B to parse RDF/XML? I think that is very problematic. Wouldn't it be simpler to use a toolkit like Jena? Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 Twitter | Facebook | YouTube From: Dave <[email protected]> To: [email protected], [email protected] Date: 06/17/2011 11:53 AM Subject: [oslc] Seeking feedback on draft SDK proposal Sent by: [email protected] Here's the start of a proposal for organizing the OSLC Tools project as an OSLC SDK: https://sourceforge.net/apps/mediawiki/oslc-tools/index.php?title=Proposal_for_OSLC_SDK The proposal is not complete and I'll need more community feedback to complete it. There are a number of issues to be considered in the proposal and I intent to call them out in sub-sequent emails to this list, in hopes of drawing people into the SDK conversation. Thanks, Dave _______________________________________________ Community mailing list [email protected] http://open-services.net/mailman/listinfo/community_open-services.net _______________________________________________ Community mailing list [email protected] http://open-services.net/mailman/listinfo/community_open-services.net
