When you type in a url a request is made and the server responds. Linkedin controls that response and can send back whatever it likes.
McDonalds can control who they sell a burger to but if I want to give my burger to a homeless man outside they shouldn't be allowed to stop me. In this case it's worse the place will tell me the price of a burger but won't allow me to tell the anyone else.
Once the information is public it has entered the public domain
That's exactly what this injunction prohitibts them from doing: "To the extent LinkedIn has already put in place technology to prevent hiQ from accessing these public profiles, it is ordered to remove any such barriers"
LinkedIn have freely provided public data to any competitor but hiQ. If they were preventing any company from taking the data, say by putting it behind a user login with licensing, it would likely not be under consideration.
I.e. that's ok to build a wall, but it's not ok not to build the wall but sue some people among the ones who take a look at the house.
Then what do you consider the storefront, or public facing data of a website? Just the whois info on the domain?
The general public can't observe the locked contents of a server without hacking it. Hacking is trespassing.
I would modify your analogy to say the store front is public facing, just like some of the LI data is public facing. There is other LI data that is not public facing.
In my opinion, websites have a larger storefront, as well as multiple levels of access to internal data.
The web isn't an abstraction, it's a network of privately owned servers responding to requests. This order tells a company that they can't program their servers to look at who is making the request and refuse to respond on that basis.
What is actually happening, is that somebody is walking into the store, asks a question about the stock or the price of the products on sale, which the store employee willingly answers.
Then, all of the sudden, the store wishes to control what you do with the answer that was willingly given to you.
This is clearly absurd - and so too is wanting to control what people do with publically-available HTTP data. If it's public, it's public.
I personally do feel that LinkedIn is within their full rights to attempt to detect and restrict content being served to screen-scraping agents, but they must then accept that screen-scraping agents must be allowed to use any means necessary to impersonate a "normal" user browsing the (public) information that they publish.
This can't be a one-sided freedom.
These two statements do not agree with each other. An owner of a brick-and-mortar shop can't (legally) stand out the front and bar black people from entering, for example.
I don't think they can stop you from photographing through the window.
It's an interesting case.
They can't stop you from sharing the price its public now.
LIN gives this information (product price) for first few questions, then if you ask about 5th price they say: 403, no more for you. WHILE IF at the same moment, different person (or you in proxy-ip-disguise) comes and asks for 5th product price, LIN happily (and publicly) gives this information.
And if the person comes wearing googlebot tshirt, LIN drops to knees and give a ..... full-db-dump-job ;) Bing/Baidu thsirts also fit. Source: www.linkedin.com/robots.txt
HiQ simply says: that's unfair you can't decide who is good and whois bad. Effectively LIN bans any google competitor (documented case).
E.g. you may enter and look around. You may not take notes, pictures, or otherwise record what is here.
Obviously LinkedIn can't control the information itself. But this case isn't about the information in the abstract. It's about an HTTP request to a piece of private property, and how LinkedIn programs that private property to respond to an HTTP request. It's well-accepted that owners of private property can make it available to the general public, with whatever restrictions they please. There is no good reason to treat web servers differently than store fronts. LinkedIn should be able to control who accesses their web servers and how.