-
|
The styleguide lacks information about Enumerations. Here are some 'style topics' I'd love to see covered: 1. Are there any naming conventions for Enumerations? 2. What are the criteria for turning something into an Enumeration? Whereas there is a 3. Do Enumeration Members always use Class-like casing? My understanding is that Enumeration Members are instances (rdf:type) of the specific Enumeration. Yet, they use the same casing as classes, such as Something like AerobicActivity seems like a good case for punning, where it occurs as both an instance of the PhysicalActivityCategory and as a subclass of for example PhysicalActivity. This seems analogous to the Wikidata example here: https://www.wikidata.org/wiki/Q1152037 Given that some Enumeration Members are unlikely (?) to be used as proper classes, what is the rationale for adopting the class casing? And more generally, would it be possible to provide some guidelines here, detailing typical characteristics that these Enumeration Members exhibit? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
There are also cases like https://schema.org/CreditCard which have both an enumeration and an instance personality - |
Beta Was this translation helpful? Give feedback.
-
|
The one thing to mention about Google-specific interpretation right now (just for conversation about mass consumption that's not in the spec) is that we allow non-prefixed enumeration values as well (just like @types). So we currently support |
Beta Was this translation helpful? Give feedback.


There are also cases like https://schema.org/CreditCard which have both an enumeration and an …