I think it may be confusing to represent the file as a class. It may be better to just put a note connected to the content explaining how the file ties in to your system. For example:
http://img100.imageshack.us/i/fileannotate.png/
If you put the attribute on the class diagram to represent it as a file I think there will be too much ambiguity in your diagram.
If the file is going to be used a lot then you may want to define the file as a sterotype in your UML diagram. For example if the file contained email addreses you may define the stereotype as (As long as the name means something in your problem domain):
<< EmailAddressStore >>
Having said that, depending on what your using the file for, the class diagram may not be the best place to represent it. It may be more appropriate to have the file in the deployment diagram. Like the log file in this example:
http://upload.wikimedia.org/wikipedia/en/d/da/UML_Deployment_Diagram.gif