Define common informational properties.


There is a significant need for common properties to provide general informational descriptive values such as "label" and "description".

We need this even in core URF when describing classes and properties, to provide a human description, for example. In order for these to be defined in the URF specification, it might seems that we need to put them in some sort of namespace, just like e.g. RDFS does with rdfs:label. From past experience, they definitely should not go in the urf- namespace, or people will think that they are specific to URF and not general informational properties. The first thought might be to place them in the info- ad-hoc namespace.

In order to promote their usage and to follow latest trends, it seems beneficial to place these directly in the default namespace. This runs the risk of collisions, but that may be a risk worth taking. We might stress the value of convention, and that the semantics of default namespace properties are dependent on context anyway. This would certainly make them more likely to be used (even if inadvertently). The problem with this approach is if we read in some data (e.g. from a gene description database) and the "name" means something different. (But shouldn't that be in a separate namespace? It could the meaning be that different, if these properties are only used for informational purposes, for indexing and such?)

Likely properties:

  • name

  • author

  • title

  • description

  • label

  • lang

See also HTML 5.2 § Standard metadata names.




Garret Wilson


Garret Wilson