[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Lessons learned from recent projects and what of2007?

• From: "Stephen Green" <stephen_green@b...>
• To: <xml-dev@l...>
• Date: Tue, 16 Jan 2007 14:22:39 +0000

Hi and thank you Manos

I'd just plead a little that soon we might have a fair bit of
valuable business logic (such as codelists, business rules,
etc) besides the basic schemas of the model in an XForms
file for, say, a particular document in a given context or
language (or tax jurisdiction, say) and having then a way to
just load that form into something like MD4J could be very
cool indeed. It's great to get value from the schema alone
but UBL work has well proven in high profile that more than
the schema is necessary in real-life situations such as normal
business. The direction this is going though seems quite
optimal to me and maybe the progress speed is sufficient
to keep the relevant folk onboard - that would be great.

All the best

Stephen Green
 

>>> Manos Batsis <manos_lists@g...> 16/01/07 14:08:44 >>>
Quoting Stephen Green <stephen_green@b...>:
> 1. Pro XML: the business benefit of changing the model and
> just regenerating without changes needed to the applications
> except at the point where there is advantage to be taken from
> the change - this seems to be achievable to the extent the
> 'freeb-ubl', 'xslt4xforms' and 'xforms4ubl' projects show

Shameless plug but here it goes anyway: J2EE devs may appreciate MD4J
[1], a passive code generator in the form of an Ant (and soon Maven)
build task, that generates a J2EE application from your XMLized model
(currently Hibernate 3 mappings).


> 2. Con XML: the actual technologies themselves for doing this
> are still at an early stage of development and very limited in
> functionality and actual delivery of their potential and promise

True. For me it was a delima; either announce early to get some interest
to help the project move forward, or wait untill it reaches a certain
level of quality and user friedlyness (and risk having it end up in
/dev/null).


> So these two have to be weighed at a fundamental level when
> applying the technologies of XML, such as XSLT and XForms.


BTW the generators currently employed are using XSLT under the hood. I'd
like to support XMI, RNG and RDFS/OWL as input, but XForms seem very
distant to me. I guess i always had a bad impression for XForms because
OS tools are not there yet. As a webapp oriented dev, i'm tired of
seeing everyone trying to fill the client support gaps on the server's
side. It is a noble effort but...

[1] http://md4j.sourceforge.net/ 

Cheers,

Manos



_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ 
Or unsubscribe: xml-dev-unsubscribe@l... 
subscribe: xml-dev-subscribe@l... 
List archive: http://lists.xml.org/archives/xml-dev/ 
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php