[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] question about relationship between JSR 170 and ebXMLRegistry
Peter Kacandes wrote:I am Sun's rep to JSR 170. <disclaimer> In the last few months I have been relatively disengaged. My information below may be somewhat dated. It may also be negatively pre-disposed. </disclaimer> JSR 170 is a Java API being developed within the JCP and will eventually be a standard Java API for content repositories. ebXML Registry is an XML Standard that may have implementations in Java and other platforms. JAXR is a JCP approved and fairly established Java API for XML Registries and Repositories. It is also a required part of the J2EE 1.4 platform. Very early in the JSR 170 life cycle I expressed the concern that it was duplicating work done in JAXR API and ebXML Registry without having any relationship to those pre-existing standards. I suggested that JSR 170 align with JAXR API and ebXML Registry to address that concern. The JSR 170 expert group decided not to alter course in light of that suggestion and is continuing to chart their own course. JSR 170 EG has several content management vendors as participants (more so than ebXML Registry TC). JSR 170 lacks most of the features of ebXML Registry. JSR 170 is a Java API while ebXML Registry is an XML Standard and a web service. Looking at my crystal ball, I personally do not quite see the long term viability for JSR 170 because it is not based on existing XML standards for Registry/Repository (ebXML Registry, ISO 11179 etc). -- Regards, Farrukh |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]