Object-oriented programming (OOP) paradigm is a prevalent method for designing computer software. In OOP data structures are represented as classes, which declare a set of named properties. This is especially important in statically typed languages, where this structure is fairly rigid and usually does not change at runtime. That structure causes friction when data in other representations needs to be accessed as objects. A well-known manifestation of this issue is the object-relational impedance mismatch, which occurs when data from relational database management systems is used in an OOP program. Developers face similar issues when using RDF data, which, even though seemingly object-oriented, has a number of properties different from typical objects in OOP sense. I’d like to show two possible ways of overcoming this problem that can be used in programs written for the .NET framework.