From an OSLC perspective, a resource that has one or more enumerated property values has an RDF statement for each such value, referencing the URI of each enumeration member. It's good practice for the resource to reference an OSLC instance resource shape. A resource shape should define the allowed values for an enumerated OSLC property, but these just reference the URIs of those enumeration members. The enumeration members themselves typically have statements such as rdfs:label or dcterms:title to provide the name ofeach member. However, from an OSLC aspect, those statements can be in any RDF graph. Some applications may include those statements in the graph of the resource shape for convenience of OSLC clients, but in general, clients may have to perform a GET on the enumeration member URI to see statements against that subject. Some enumeration members might be defined in static vocabularies provided outside of any tool. This is just the way that OSLC, and linked data, is.

Report Builder (part of JRS) builds a type system model that covers enumeration values by querying LQE. That type system model can then serve the RB UI when it wants to show the user a list of allowed values for some meta property. The type system model is typically auto-refreshed every 12 hours.