Copyright on XP icons...

Just found this a few minutes ago... thought it was quite interesting:

http://www.microsoft.com/permission/copyrgt/cop-img.htm#Icons

We've always wondered what Microsoft's official stand on their icons was, and I just came across this link... it's the only time I have ever seen Microsoft actually mention their policy on their icons.

I'm not saying its good or bad news, just that it has been discussed on here in the past and that a policy for them does exist apparently
5,265 views 8 replies
Reply #1 Top
I'm sure the same would go for icons and UI elements from Mac OS, as well.

I can see OS 'ports' as both a perk and a problem. On the one hand they are good advertising for the look and feel of a newer/different OS, but at the same time it allows people to *have* that look and feel without buying it.

I understand, though, that people want specifically targeted shortcuts, and to do that you need icons for the apps. My position has been that we should make generic icons, 'paint program', 'browser', etc., instead of borrowing the specific ones from Adobe or Netscape. Alas, that isn't what people want. I can understand it, but I'm not sure about it.

There are policies on every site that I disagree with, and this is the one here that gives me pause. Just as allowing people to cut and paste stolen photography harms wallpaper art as a whole, I think that using other people's interface and icons as building blocks for our skins and themes is no better.

When I gripe to someone that makes 'babe' wallpapers, I always tell them that Devart is full of 'babes' that take photos of themselves and gladly collaborate and share them with other artists. There's no need to steal. Here, we have UI designers, Iconists, etc., who are also happy to share their work with others. I'm not sure that there is a need to 'borrow' when you can do the work honestly, and promote other people's work at the same time through collaboration.
Reply #2 Top
Seems things aren't as gray as we've been told..........
Reply #3 Top
I think the problem with Microsoft's policy on Icon use is [as usual] it is specific/general legalese which unfortunately does not address Skinning in any way specifically, perhaps due to their Legal Departments ignorance of the field.
If skinning of an MS OS is seen as an addendum to the OS itself, and in particular, Windowblinds having the blessings of MS as a legitimate add-on, then skins made for it could very well be 'beyond' the wording of that policy.
It would be nice if MS were 'industry-specific' with the legalities of their icon use.
According to those terms, when Windowblinds calls up the program's icon [like IE] and displays it on my WB skin to indicate what window it is...that's 'not allowed'.
Hardly....it is the same OS running the same IE6 with the same icon, but it was MY code inclusion that made it show, so that's 'wrong'.

Until the Legal Dept of Microsoft directly communicates any limitations directly relating to skinning and customizing, no-one will 'really' know what 'goes'...
Reply #4 Top
Well, i think the difference resides in 'distribution'. Some apps reference installed applications to 'display' icons for the shortcuts. The user owns these icons, they reside in purchased software. On the other hand, when a skinner extracts those same icons, alters or manipulates them, then redistributes them independant of the application; I think they are on unsure footing at best.

I dunno, I respect the site, and will respect its policy until the issue is decided one way or another. I assume, being popularly poised between MS and Mac, all parties have ample awareness and opportunity to express their displeasure. This goes far beyond OS icons, though. It would be up to every application's developer whether they want the icons redistributed. That's a lot of favor to gain for big sets.

This, at least, is a purposeful decision. Many policies on other sites are just accidental by-products of their design.
Reply #5 Top
baker...don't forget though, that the 'purchase' of the OS only gives you rights to the icon's use, and not its actual 'ownership'.
The same applies to an Architect's drawings.
A client pays the Architect to create the drawing, however its copyright remains exclusively with the Architect and the client is ONLY allowed to use the drawing for its intended purpose - building the structure. Even framing the drawing and hanging it on a wall is not an expressed use and violates copyright...
Reply #6 Top
hrm... true. Since the purpose of an icon is to be referenced as a visible way of launching it, I would assume that any app that does so for that purpose would be within the icon's intended use.

Netscape/Mozilla references app's icons when pointed at the local drive. People use Powerdesk as a file browser, as well. Pulling them out on-the-fly for shortcuts would have to be legal, I think.

Either way, it is still very different than a skinner ripping them out of an app and manipulating them, imho. Unfortunately, opinion is all we have to go on.
Reply #7 Top
What I personally got from the policy statement was that generally using the icons in anyway other than for learning documentation was not allowed.

If you've got a link to an existing icon or have it as a shortcut, you’re not actually 'using' it, you’re just linking to it.

The same with the WindowBlinds example Jafo mentioned... your simply allowing the existing icon to be displayed next to or in the skin - it's not actually being 'used' and it's not specifically part of the skin, it's just an existing part of the GUI.

Actually using the icons in software menus, skin ports, icon ports, icon packages, icon re-colourings, icon re-releases, alterations, "artwork" or design elements etc... I believe they consider to be illegal according to this policy summary.

So is it illegal to 'use' them for whatever you want?... in short; yes, it seems it is.

But would Microsoft actually bother to follow up on any specific case... I seriously doubt it to be honest. But you never know... Apple have walked that road a few times already
Reply #8 Top
Apple has chased this issue in the past...but MS has not. The inference from the different tacks taken is that Apple is not pleased seeing its product being 'used' within a MS 'system'. but MS is either totally oblivious [I STRONGLY doubt], or is quite 'OK' with the concept of skinners making the MS OS just a bit more entertaining and enjoyable.
What we all are doing for MS has got to be a plus for them, not a 'minus'.
It'd be nice if someone who new Mr. Bill could get the 'official stance' straight from the horse's mouth...