Difference between revisions of "Faces Application Profile Album"
Jump to navigation
Jump to search
m (User:Kurt/Faces Application Profiles StudySet moved to User:Kurt/Faces Application Profile StudySet: first proposal of faces StudySet type) |
m (User:Kurt/Faces Application Profile StudySet moved to Faces Application Profile StudySet: first proposal of faces StudySet type) |
(No difference)
| |
Revision as of 12:41, 3 June 2008
Namespaces[edit]
| Term URI | http://purl.org/dc/terms/ |
| Name | dcterms: |
| Label | Dublin Core terms |
| Term URI | http://purl.org/escidoc/metadata/terms |
| Name | escidoc: |
| Label | eSciDoc terms |
Syntax Encoding Scheme[edit]
| String data type definition | |
| Name | <string> |
| Label | Character string |
| Definition | A string of ASCII characters. No formatting tags may be included. The following characters must be encoded for XML: '&' - '&'; '<' - '<'; '>' - '>'. A limited list of non-ASCII characters may be included encoded as character entities. |
Describing a Study Set[edit]
| Term URI | http://purl.org/dc/terms/title |
| Name | title |
| Label | Title |
| Defined by: | - |
| DC Definition | A name given to the resource. |
| DC Comment | - |
| eSciDoc Definition | The name of a study set. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: 1; |
| Best practice | The complete name should be generated automatically from given name and family name |
| Open Questions | - |
| Term URI | http://purl.org/escidoc/metadata/terms/partner |
| Name | partner |
| Label | Partner |
| Defined by: | - |
| eSciDoc Definition | A short description of a study set. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: 1; |
| Best practice | - |
| Open Questions | - |