index

20111229_D3_3_eCOTOOL_ECSAP_agro_v1

eCOTOOL Europass CS Application Profile adapted to Agriculture

General notes

History

versiondatebychange
A.12011-11-23SimonInitial version
A.1.12011-12-29Simonremoving material appearing in D1.2

Information model / application profile

Key to the table columns

element number
An identifying number for reference. The number corresponds to the numbering in the ECS. The number structure reflects the hierarchy of the information structure: e.g. the element 3.2.1 is part of the element 3.2.
N: multiplicity
This uses the normal conventions as used in UML and elsewhere for how many of a particular element are allowed within the parent element. "1" means that there must be exactly one occurrence of this within the containing element. E.g. 3.2.1 must occur exactly once within every 3.2 structure (of which there can be any positive number). "0..1" means that it may or may not occur, but not more than once. "*" means optionally any number of times. "1..*" means it must occur at least once.
element content
This gives an explanation of what the element is.
data format
container
no data is associated with this element, as it just contains the lower-level elements.
string
plain unstructured text string of indefinite length
XHTML
formatted text, only XHTML and not other HTML, to preserve the integrity of an overall XML document
URL
link to existing web site for further information
URI
identifier that would normally resolve to a web page with useful information about the thing identified
CDATA string
This construct allows anything – even arbitrary XML – to be included within an XML document without disrupting the containing XML itself. See the XML spec. Essentially, this means not committing at this stage to a decision on how to represent addresses.
source spec
This column has suggestions for existing specifications on which to base the definition and format of the element.

Key to background colours

WhitePart of this information model implemented in the Web tool
PinkInformation not required in databases
Light blueNot specifically adapted for agriculture, for future good practice
GreenAdaptation to agriculture
Light greyAn informative comment, not part of the information model
Grey-greenA comment about the adaptation to agriculture
Dark greyA visual separator

Information model table

Please refer to D1.2 for the basic comments, which have been mostly removed for clarity. The remaining ones are relevant to the adaptation to agriculture.

element number N element content data formatsource spec
 
0.   1

Information about the document as a whole

 (container) -
0.1 1 document language ISO language code [1] ISO 639-1
0.2 1 identifier URI dcterms:identifier[2]
0.3 0..1 original identifier URI dcterms:identifier[2]
0.4 * contributor string, URI dcterms:contributor[2]
0.5 0..1 creator string, URI dcterms:creator[2]
0.6 0..1 created ISO date dcterms:created[2]
rfc 3339
0.7 0..1 last modified ISO date dcterms:modified[2]
rfc 3339
0.8 1 Sector classification string from vocab NACE codes

There appear to have been different ways of displaying the same NACE code. For this application profile, they shall be displayed according to the form given in the link just given. That is, EITHER exactly two digits, followed optionally by a "." character and optionally further digits, OR a single capital letter also as displayed on the official site, indicating a broad area usually covering more than one two-digit code. Agriculture covers "A" by itself, and any numeric code starting with "01", "02", or "03". A letter MUST NOT be followed by numbers.

The standard explanatory note is moved down from 0.8 to 0.9.

0.9 1 standard explanatory note XHTML [5]
 
1.   1

Title of the certificate

 (container) -
1.1 1 title text string dcterms:title[2]
1.2 0..1 title language ISO language code [1] ISO 639-1
 
2. 0..1

Translated title of the certificate

 string dcterms:title[2]
 
3.   1

Profile of skills and competences

 (container) -
3.1 0..1 complete text for section 3 XHTML [5]

3.1 is provided only for legacy purposes, as failing to provide clearly defined separate learning outcomes here severely limits the value of the ECS. 3.1 and 3.2 are alternatives, not to be used together.

3.2   * single learning outcome (or competency) (container) -
3.2.1 1 classification as ability or knowledge "ability" or "knowledge" -

Agricultural learning outcomes fall into the normal pattern of abilities (skills or competences, or sometimes known as "performance criteria") and knowledge. It is seen as useful to make this distinction here, as this will determine whether the item has an action verb or not.

3.2.2   1 structured short description text container -
3.2.2.1 0..1 action verb(s) (could be restricted to an agricultural vocabulary) string -
3.2.2.2 1 rest of short description string -
The action verb is mandatory if the learning outcome is classified as an ability.
3.2.3 0..1 learning outcome URI URI -
3.2.4   * single learning outcome category container -
3.2.4.1 1 classification scheme string -
3.2.4.2 1 category term string -

The URI identifies a well-structured learning outcome definition held elsewhere.

Two classification schemes are seen as relevant, and as many classifications may be recorded as wanted.

  1. The NACE Rev. 2 classification scheme may be used again here to identify a sector specifically relevant to the particular learning outcome. See the note at element 0.8 for the correct format.
  2. The AGROVOC vocabularies may be used to indicate topics connected with a particular learning outcome.

 
4.   0..1

Range of occupations accessible to the holder

 (container) -
4.1 0..1 unstructured text for this XHTML [5]
AND/OR a structured list of accessible occupations
4.2   * single accessible occupation (container) -
4.2.1 1 accessible occupation name string -
4.2.2   * single accessible occupation identifier (container) -
4.2.2.1 1 occupation classification system/scheme string -
4.2.2.2 1 occupation classification code/term string -
For agriculture, the use of appropriate occupational classification schemes should be agreed and specified. There may be more than one of these, and in any case the ability to classify an occupation in other ways should be retained.
4.2.4 0..1 legal considerations XHTML [5]
For agriculture, it might be useful to link to a page explaining the legal basis of agriculture across Europe.
 
5. Official basis of the Certificate ignored -
 
5.1   1

Awarding body

 (container) -
5.1.1 1 name of awarding body string -
5.1.2 0..1 address of awarding body CDATA string see XML spec
5.1.3 0..1 phone of awarding body string -
5.1.4 0..1 e-mail of awarding body e-mail string RFC 5322
5.1.5 0..1 website of awarding body URL -
5.1.6 0..1 status of awarding body string -
 
5.2   0..1

National / regional authority

 (container) -
5.2.1 1 name of authority string -
5.2.2 0..1 address of authority CDATA string see XML spec
5.2.3 0..1 phone of authority string -
5.2.4 0..1 e-mail of authority e-mail string RFC 5322
5.2.5 0..1 website of authority URL -
5.2.6 0..1 status of authority string -
5.1 and 5.2 could be adapted to agriculture by a tool having a comprehensive list of awarding bodies for agricultural qualifications, and authorities regulating them.
 
5.3   0..1

Level of the certificate

 (container) -
5.3.1   * single framework and level (container) -
5.3.1.1 1 framework name string credit:scheme[3]
5.3.1.2 0..1 framework URI (if available) URI credit:scheme[3]
5.3.1.3 1 level in framework string from vocab
(for EQF: "1" to "8")		 credit:level[3]
5.3.2 0..1 other unstructured level information XHTML [5]
 
5.4   0..1

Grading scale / Pass requirement

 (container) -
5.4.1 0..1 unstructured grading scale information XHTML [5]
5.4.2   * structured grading information (container) -
5.4.2.1 1 grade, as on an actual Certificate for which this is the supplement (default: Pass) string -
5.4.2.2 0..1 explanation of requirements for that grade XHTML [5]
 
5.5 0..1

Access to next level

 XHTML [5]
Potentially, this could be adapted to agriculture by adding structure relevant to progression in agricultural learning education training and professional development.
 
5.6   0..1

International agreements

 (container) -
5.6.1 0..1 unstructured text for this XHTML [5]
5.6.2   * single related qualification (container) -
5.6.2.1 1 other qualification URI -
5.6.2.2 1 relation to other qualification URI SKOS mapping properties [4]
 
5.7 0..1

Legal basis

 XHTML [5]
Tools could help adapt this to agriculture by holding details of all relevant laws.
 
6. 1

Officially recognised ways of acquiring the certificate

 XHTML [5]
It may be possible that in agriculture some common structures were agreed that could form the basis for structuring this element. At present no such common agreements are known.
 
7. 0..1

Entry/access requirements

 XHTML [5]
Entry/access requirements is a promising area for adaptation to any particular sector, including agriculture. It seems more likely to get agreement on a structure and vocabularies for this section within a sector, rather than generally. Each individual entry/access requirement could be one of
  • an agriculture-related qualification (with URI if available)
  • an agricultural competence definition (ideally with URI)
  • another quality or characteristic relevant to agriculture
 
8. 0..1

Additional information

 XHTML [5]
 
9. 1

National reference point

 XHTML [5]
 

Notes

[1] ISO 639-1 language codes
Viewable at Wikipedia or the Library of Congress
[2] Dublin Core
See the DCMI Metadata Terms
[3] Educational Credit Information Model
CWA 16077, available as a whole from ftp://ftp.cen.eu/CEN/Sectors/TCandWorkshops/Workshops/CWA16077.pdf
[4] Simple Knowledge Organization System
See http://www.w3.org/2004/02/skos/
[5] XHTML
An effective interoperability specification might need to specify a subset or profile of XHTML, to allow links and formatting, but probably not embedded content.