Difference between revisions of "ESciDoc Application Profile LegalCase"
Jump to navigation
Jump to search
| Line 260: | Line 260: | ||
* [[ESciDoc_Application_Profile_Publication]] | * [[ESciDoc_Application_Profile_Publication]] | ||
* [[ESciDoc_Application_Profile_Source]] | * [[ESciDoc_Application_Profile_Source]] | ||
* [[ESciDoc_Application_Profile_project-info]] | |||
== Related eSciDoc Encoding Schemes == | == Related eSciDoc Encoding Schemes == | ||
Latest revision as of 14:18, 10 March 2015
|
Introduction[edit]
Please enter all comments concerning the use cases on the discussion page.
eSciDoc PubMan Description Template: Legal Case[edit]
Literal Statement Templates (Properties)[edit]
Title[edit]
| Term URI | http://purl.org/dc/elements/1.1/title |
| Term Name | title |
| Label | Title |
| DC Definition | A name given to the resource. |
| DC Comment | - |
| eSciDoc Definition | Title of the legal case. |
| eSciDoc Comment | - |
| Type of term | Property |
| Domain | Legal Case |
| Range | Literal |
| Obligation | Optional |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
Court[edit]
| Term URI | http://purl.org/escidoc/metadata/terms/0.1/court |
| Term Name | court |
| Label | Court |
| eSciDoc Definition | The court where the legal case was treated. |
| eSciDoc Comment | - |
| Type of term | Property |
| Domain | Legal Case |
| Range | Literal |
| Language Constraint | no |
| Obligation | Optional |
| Occurrence | Min:0; Max: unboundend |
| Best practice | - |
| Remarks | - |
Identifier[edit]
| Term URI | http://purl.org/dc/elements/1.1/identifier |
| Term Name | identifier |
| Label | Case Reference Number |
| DC Definition | An unambiguous reference to the resource within a given context. |
| DC Comment | Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. |
| eSciDoc Definition | The identifier of the legal case. This value is world-wide unique. |
| eSciDoc Comment | - |
| Type of term | Property |
| Domain | Legal Case |
| Range | Literal |
| Obligation | Optional |
| Occurrence | Min: 0; Max: 1 |
| Version | 0.1 |
| Best practice | - |
| Remarks | - |
Non-Literal Statement Templates (Properties)[edit]
Issued[edit]
| Term URI | http://purl.org/dcterms/issued |
| Term Name | issued |
| Label | Date |
| DC Definition | - |
| DC Comment | - |
| eSciDoc Definition | - |
| eSciDoc Comment | - |
| Type of term | Property |
| Domain | Legal Case |
| Range | Literal/Date |
| Obligation | Optional |
| Occurrence | Min: 0; Max: 1 |
| Version | 0.1 |
| Best practice | - |
| Remarks | - |
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. |
| Date data type definition | |
| Name | <date> |
| Label | Date |
| Defined By | http://www.w3.org/TR/NOTE-datetime |
| Definition | Character string representing a date to the complete date level of the W3CDTF profile of ISO 8601 |
| URI data type definition | |
| Name | <URI> |
| Label | URI |
| Defined By | http://www.ietf.org/rfc/rfc2396.txt |
| Definition | Character string for a URI |
Schema[edit]
Related Application Profiles[edit]
eSciDoc
- ESciDoc_Application_Profile_Event
- ESciDoc_Application_Profile_File
- ESciDoc_Application_Profile_Organization
- ESciDoc_Application_Profile_Person
- ESciDoc_Application_Profile_Publication
- ESciDoc_Application_Profile_Source
- ESciDoc_Application_Profile_project-info