gitgabrio commented on PR #6311:
URL: 
https://github.com/apache/incubator-kie-drools/pull/6311#issuecomment-2812053277

   > > > really well done @gitgabrio - thank you for the effort!
   > > > however I'm afraid that the whole software might be broken if omg - 
for whatever reason - don't have that files available.
   > > > what if we moved the files to our kie website? https://kie.apache.org
   > > > website is not part of the software release, so we have no legal 
restrictions for it.
   > > > thoughts?
   > > 
   > > 
   > > @porcelli I've no _strong_ opinion, TBH. Either case, there could be an 
outage, or files could be moved elsewhere (for whatever reason).
   > > Some details make me prefer the OMG URL:
   > > 
   > > 1. it is the "official" reference, and whenever updated/new models are 
published, those are the one to consider
   > > 2. the "kie-apache" approach would create a new burden to maintain a new 
"data storage"
   > > 3. the "kie-apache" approach would lead to two sources-of-truth/two 
databases-in-sync pattern, that generally is better to avoid.
   > > 
   > > Anyway, if someone else is willing to maintain it - and that means 
always, at every modification of DMN xsd, fine for me.
   > > @baldimir @yesamer : your thoughts ?
   > 
   > @gitgabrio I would consider that as a mirror, in case the official 
reference is not available.
   
   @porcelli @yesamer @baldimir @LightGuard 
   
   Duplicating xsd at a different position respect of referral one is just an 
anti-pattern that:
   1. brings in more complexity
   2. increase the workload
   3. aim to solve a problem that currently does not exists, and, if ever it 
will happen, it will be a consequence of much bigger problems to solve
   
   So, for the moment being, I think it does not make sense to spend time to 
that. 
   If, ever, there will be a real need for that, of ir someone else is willing 
to dedicate time to that, I think it could be done on a later PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to