I have added the schema.org/PropertyValue entity to JDX model as well as it accompanying schema.org/propertyID property to accommodate the inclusion of the occasional property that is needed for a particular job description that: (a) cannot be found in a known namespace; and (b) is too fringe to justify addition to JDX as a new property.
This PropertyValue mechanism should be used sparingly and never where a specific property from a known namespace serves the purpose. Using PropertyValue as a substitute for such properties will not trigger the same linked data function as the predicate of an RDF triple.
I'm considering adding schema.org/PropertyValue to the range of schema:identifier for the same reason (already in the enumerated range of the property in schema.org).
I have added the
schema.org/PropertyValue
entity to JDX model as well as it accompanyingschema.org/propertyID
property to accommodate the inclusion of the occasional property that is needed for a particular job description that: (a) cannot be found in a known namespace; and (b) is too fringe to justify addition to JDX as a new property.E.g.,
This
PropertyValue
mechanism should be used sparingly and never where a specific property from a known namespace serves the purpose. UsingPropertyValue
as a substitute for such properties will not trigger the same linked data function as the predicate of an RDF triple.I'm considering adding
schema.org/PropertyValue
to the range ofschema:identifier
for the same reason (already in the enumerated range of the property in schema.org).