Classes for status, type and activity

The company type, status and activity properties should link to classes so that detail about which vocabulary can be included. Also, consider making names of these properties more consistent.






Tue, 27/03/2012 - 12:00


The properties "type", "status" and "activity" would be of little value if they were of type "String". For interoperability reasons, these properties should indicate which encoding they use. This can be achieved, for instance, by giving these properties a Complex Data Type "Code" (a Concept or Class in the conceptual model).


The UN/CEFACT Core Data Type Library can be a source of inspiration here. A data type Code could include the following attributes:

  • Code.content [1..1]: String
  • Code.list [0..1]: String
  • Code.listAgency [0..1]: String
  • Code.listVersion [0..1]: String

In a Linked Data World, the following additional properties could be useful:

  • [0..1]: URI
  • Code.inScheme [0..1]: URI

The content of this field is kept private and will not be shown publicly.