2009-03/Leap2A organizational data

Belongs to the 2009-03/Leap2A specification &gt; predicates – see also 2010 developments

This information belongs within an organization element. To keep this conceptually separate, in parallel with 2009-03/Leap2A personal data, this is represented by the separate orgdata element.

orgdata
This element is for non-relational data about an organization. It belongs within an organization-type entry. As with a person, the most important reason for this is to ensure that information about an organization is listed exactly once, rather than duplicated.

Within the organization entry, any number of leap:orgdata elements can appear.

University of Somecity Somecity tech info@somecity.ac.uk UK http://www.somecity.ac.uk

For each orgdata element, there is one mandatory attribute and there are three optional attributes.

field
Each orgdata element has a mandatory leap:field attribute to distinguish what the field means. The values of the leap:field attribute should normally be taken from the list below. Otherwise, for extension purposes, the value of the leap:field attribute can be a URI, identifying a non-Leap2A predicate.

service
This is similar to service in persondata, except that the services here are mainly for ID purposes.

label
As elsewhere, label is intended to hold the version of the field name given in the originating system.

countrycode
This is optional, but specifically only for the "country" field, as in addresses, and is not allowed in other fields.

Orgdata fields
M is the allowed multiplicity within a single organisation entry.

{|border !field !M !Attributes needed !Format !Notes !

legal org name

 * 0..1
 * text
 * text

preferred org name

 * 0..1
 * text
 * If not present, assume legal org name is preferred. This can hold "trading name".
 * If not present, assume legal org name is preferred. This can hold "trading name".

country

 * 0..*
 * countrycode (optional)
 * Text. But, as in addresses, with an optional attribute of leap:countrycode following SIF(UK): 3-letter ISO 3166-1 code.
 * This is the country in which the organization, or relevant division, is based. If more than one country is given, the first one listed should be the one of the primary seat or head office.

website

 * 0..*
 * URL
 * Any URL associated with the organization, usually their own domain default page. If more than one is given, the first one should be the primary one.
 * Any URL associated with the organization, usually their own domain default page. If more than one is given, the first one should be the primary one.

id

 * 0..*
 * service
 * string
 * Typically, a registration number of the organization with some official body. Order is not significant.

email

 * 0..*
 * e-mail: rfc2822
 * If more than one is given, the first one should be the primary one.
 * If more than one is given, the first one should be the primary one.

workphone

 * 0..*
 * recommended format: full international, starting with + (+44 for UK)
 * If more than one is given, the first one should be the primary one.
 * If more than one is given, the first one should be the primary one.

minicom

 * 0..*
 * recommended format: full international, starting with + (+44 for UK)
 * Included because of SIF(UK) having it.
 * Included because of SIF(UK) having it.

fax

 * 0..*
 * recommended format: full international, starting with + (+44 for UK)
 * Pretty common for businesses.
 * Pretty common for businesses.

other

 * 0..*
 * label
 * }
 * }
 * }
 * }
 * }

Service abbreviations
Please suggest any others for inclusion here. Some attempt may be made to capture MIAP fields for providers and for awarding organizations.

Postal addresses
See leap:spatial, which applies as much to organizations as to people.