Re: Should Inline be private in the private part of a package spec?

["Randy Brukardt" <randy@rrsoftware.com>]

"Georg Bauhaus" <rm.dash-bauhaus@futureapps.de> wrote in message 
news:503754ae$0$6582$9b4e6d93@newsspool3.arcor-online.net...
> On 24.08.12 06:22, Randy Brukardt wrote:
>
>>> Ada software engineers are asked to use a domain specific vocabulary
>>> in their program (which here is about car status). The status web
>>> server engineers can be asked the same when producing tagged text
>>> they then delegate to the web guys who write the XSLT to be run in
>>> the browser. I think Vasiliy already indicated how. And yes, it has
>>> to come from somewhere.
>>
>> You need to go to "Overengineering Anonymous". The original problem
>> statement was "send to a browser", which means HTML has to be present
>> somewhere. All the rest of this is huge amounts of overkill.
>
> This is the way larger customers produce software based systems.
> The procedures are such that several teams work at their own pace.
> Changes need to be made to modules of the system, if possible.

Sure, you need good interfaces. XML does nothing to help there (as Dmitry 
has pointed out continually, and you pointed out yourself by babbling about 
"vocabulary").

> It is not the kind of system where you have a single server
> maintained by a single team. The HTML+CSS+... needs to be the
> result of they system's modules working.
>
> You can't have all customers of ${car maker} drive their cars
> to the next shop to have staff install an updated part of
> a web page, can you?

If you need to update a web page, your processes have already failed. No one 
needs (nor should want) to change the presentation of data every few weeks; 
so long as the data is presented accurately (which is the point of testing 
and verification), nothing ever needs to change.

                  Randy.