OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: XPATH query Take 2

Message text written by INTERNET:frankp@softed.com
I personallly feel the objection to the usage of OQL from certain parties
commercially based rather than technically based*, because certain vendors
don't want to have to implement OQL to be compliant. I can see where they
are coming from, implementing OQL is a little harder**, but I don't agree
that an international standard should be compromised for the commercial
of a few small, but vociferous, vendors.


You could turn this around and say that users want to buy cost effective
solutions - and why should they be forced to buy a Mercedes when a
Chevy Geo can get the job done for their business needs?

I have strongly argued that - since this is ebXML - we should at least
have XML based options - unless we are going to vote to change
everything to be ebOOxml.

Clearly the trend is to XML based backend systems.  This is not just
one vendor saying this - every DB vendor of significance has announced
XML product - and are members of the W3C.

Therefore it makes sense to listen to what they and their customers are

Remember international standards are only as good as the depth
of support they garner.  Monster.com is just jammed full of requests
for OQL specialists.  Out of 455,000 vacancies today - only 3 listed OQL,
and as a 'knowledge of is a plus' - not a requirement.
This tells you something right there.

International standards succeed when they deliver significant business
value.  Vendors have more at stake than anyone else in ensuring
an expanding and extensive marketplace.  They are least likely to
shoot themselves in the foot.   However - they have been known to
try and shoot all their competitors in the foot!  Ensuring an open and
common technology basis is the right approach here - and XML is
the choice.  XPath I view as a stepping stone - as I said earlier today,
its a good place to start - with positive benefits from the view point
of XML parsers interacting with Registries - cheap and straightforward
implementations for endusers - and can provide a solid
foundation from which to support more extensive and mature XML
query systems as the RC's become available later this year.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC