Arnoud Engelfriet wrote:
Why bother with the technical implementation at all? Just say that you must prominently provide the information where to get the source from you to network users of the work.
I take it means: "you must prominently provide the information to network users of the work as to where to get the source from you".
Well the idea is that we are making sure that those users get the best chance of knowing that they have a right to the source code. When a software is used for running an online email website like gmail.com, the current wording requires a notification to be placed on the same UI that is provided for using the service. But as I read somewhere (which is why I added the "if this is not possible" wording) if a work is used on a DNS server or similar, there will be no UI -- a user's computer would merely communicate with the server in a limited language which would not allow it to ask for the source code -- in that case, the next best place is the company's website or something like that.
I did not think it was probable that a company providing such a service would have no place on the network connected to their activities, in other words, a website. So the current wording does not actually mandate that they *have* or *provide* such a location itself. What would happen when there is no such location on the network? Would the service provider be excused from providing availability information of the source code because they don't *have* such a location?
Shriramana Sharma.