index

20120122_D3_5_eCOTOOL_ECSAP_agro_v5

eCOTOOL Europass CS Application Profile adapted to agriculture, refined and optimised

General notes

History

versiondatebychange
ECS A.12011-11-23SimonInitial version
ECS A.22011-11-28Simonsplit version
ECS A.32011-12-08Simonrevision following discussion with Chiara
ECS A.42012-01-05Simonremoved comments already appearing in D1.2 or D3.3
ECS A.52012-01-22Simonminor final changes

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
GreenRefinement and optimisation
Light greyAn informative comment, not part of the information model
Grey-greenA comment about the refinement and optimisation
Dark greyA visual separator

Information model table

element number N element content data formatsource spec
 
0.   1

Information about the document as a whole

 (container) -
0.1 1 document language ISO 639-1 language code [1] RFC 5646
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

This element is necessary for any sector-specific adaptation of the ECS Application Profile. It can be used by tools to adapt their behaviour in a sector-specific way even if the tool is used by several sectors simultaneously.

The standard explanatory note is renumbered from 0.8 (as in D1.2) 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 639-1 language code [1] RFC 5646
 
2. 0..1

Translated title of the certificate

 string dcterms:title[2]
 
3.   1

Profile of skills and competences

 (container) -
3.1 0..1 learning outcome URI for section 3 as a whole URI -

There may be a close correspondence between the skills or competences given by the certificate as a whole and one particular external definition. If there is a URI for this, it should be put here.
3.2 0..1 complete text for section 3 XHTML [5]

If the URI of a separate definition corresponding to the certificate as a whole is given, then if text is given in 3.2 above it should correspond to text in the separate definition. However, there should be no text in 3.2 if the profile of skills and competences is structured, as normal, into separate learning outcomes, as in 3.3 below. Another way of putting this is that even where Section 3 is properly structured, there may be a URI for the certificate as a whole, but no text in 3.2. In any case, the text for the competence corresponding to the whole certificate will be given by the separate definition identified by the URI in element 3.1.

In no cases should there be content in element 3.2 together with items in element 3.3. They are alternatives, strictly exclusive.

The element for "single learning outcome" is renumbered from 3.2 (as it is in D 2.1) to 3.3
3.3   * single learning outcome (or competency) (container) -
3.3.1 1 description of learning outcome as "ECS-friendly" text string -
3.3.2 0..1 learning outcome URI URI -
The component part URI leads to a full(er) expansion of the learning outcome, where further structure is given. Compared with D3.3, this version for D3.5 of the application profile reverts to the original form given in D1.2, because the detail is better placed in a separate structure, where it can be reused for different purposes. The separate structure is given in a separate table.
 
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 (it is possible to envisage situations where both may be appropriate)
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 -
4.2.4 0..1 legal considerations XHTML [5]
 
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.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]
 
5.6   0..1

International agreements

 (container) -
5.6.1 0..1 unstructured text for this XHTML [5]
5.6.1 is sufficient for immediate use; however 5.6.2 is included as an optional alternative for future better practice. Both may be used.
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]
 
6. 1

Officially recognised ways of acquiring the certificate

 XHTML [5]
 
7. 0..1

Entry/access requirements

 XHTML [5]
 
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.