[oslc-core] Should RDF/XML be MUST?

[Tack Tong]

+1 from me, thinking about Reporting Consumer perspective that has to deal
with any unknown Service Providers.

Tack


Date: Tue, 11 May 2010 07:41:51 -0700
From: Nick Crossley <ncrossley at us.ibm.com>
To: oslc-core <oslc-core at open-services.net>
Subject: Re: [oslc-core] Should RDF/XML be MUST?
Message-ID:

<OFFE02AAD1.F0D20B5B-ON88257720.00501015-88257720.0050BB62 at us.ibm.com>
Content-Type: text/plain; charset="us-ascii"

Personally, I do not care about RDF, but surely we must have at least one
common representation for OSLC.  If all domains are completely free to
mandate their own favored representation, then a cross-domain client is
put in an almost impossible position of having to deal with a potentially
large number of different representations.  Imagine a client trying to
trace down from requirements through CM, SCM, test cases, build automation
producing software assets, etc., and every one requiring a different
representation.

RDF/XML might not be the ideal way to represent RDF, but it is something
we seem to have invested quite a lot of time in already.  I believe it is
essential to have at least one common representation that is required by
all OSLC domains.

Nick.

Tack Tong
IBM Rational software
tacktong at ca.ibm.com
905-413-3232
tie line 313-3232:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100511/ecb6439d/attachment-0003.html>