You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Sandro Martini (JIRA)" <ji...@apache.org> on 2014/03/03 11:40:24 UTC

[jira] [Commented] (PIVOT-936) Create a XML Schema for BXML

    [ https://issues.apache.org/jira/browse/PIVOT-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917923#comment-13917923 ] 

Sandro Martini commented on PIVOT-936:
--------------------------------------

Hi, you are welcome to help us with this :-) ... an utility like this would be great.
But note that out Maven pom files are not for builds (we still have our original Ant build system), so probably it would be better to make/deploy this tool alone from Pivot, and we could host it at Apache-Extras for example here:
http://code.google.com/a/apache-extras.org/p/pivot-contrib/
in a dedicated subproject, and see later what to do.
If you are interested, send me an email with your Google account userid so I can give you write access there.
My problem is that that I still have very little time, so I can't help so much, but I'll try my best (for example the initial setup of the project, and enforce some of our best practices on code at the beginning) ... anyway be free to do a post in our mailing lists, so we can see what others think, and maybe gather some other contribution.

Thanks for now.

> Create a XML Schema for BXML
> ----------------------------
>
>                 Key: PIVOT-936
>                 URL: https://issues.apache.org/jira/browse/PIVOT-936
>             Project: Pivot
>          Issue Type: Improvement
>          Components: core-xml
>            Reporter: Labrosse Aurélien
>
> I saw an older bug that focuses on DTD, which was sadely closed. 
> From my point of view using XML without schema is dangerous for project adoption : as a model driven architecture fan, i can't use a perfect mapping to produce BXML code without an ugly generator. 
> The xml schema would suppress this limitation and leverage Pivot to a more professional level. It would allow its core syntax to be used in various existing model transformation tools available on the Open Source market.



--
This message was sent by Atlassian JIRA
(v6.2#6252)