Difference between revisions of "Talk:ESciDoc Application Profiles"
Jump to navigation
Jump to search
(New page: Complex Types like * Creator ** the proposed data model in eSciDoc looks like this: *** CreatorType can either be: **** Person, which has the following properties: ***** Complete Name **...) |
|||
| Line 22: | Line 22: | ||
***** Artist | ***** Artist | ||
***** Editor, .... | ***** Editor, .... | ||
If we want the Application Profile to be Dublin-Core-Compliant, an issue with such complex types arises:<br /> | |||
The [http://dublincore.org/usage/documents/profile-guidelines/ DC Application Profile guidelines] define Application Profiles as flat structures by allowing for relational attributes such as | |||
* Refines | |||
* Refined By | |||
* Encoding Scheme For | |||
* Has Encoding Scheme | |||
* Similar To | |||
Revision as of 13:56, 29 January 2008
Complex Types like
- Creator
- the proposed data model in eSciDoc looks like this:
- CreatorType can either be:
- Person, which has the following properties:
- Complete Name
- Family Name
- Given Name
- Alternative Name
- Person Title
- Pseudonym
- Organisation
- Identifier
- Organisation, with the following properties:
- Oranisation Name
- Address
- Identifier
- Person, which has the following properties:
- Creator Type has a further property:
- Creator Role, which can be:
- Author
- Artist
- Editor, ....
- Creator Role, which can be:
- CreatorType can either be:
- the proposed data model in eSciDoc looks like this:
If we want the Application Profile to be Dublin-Core-Compliant, an issue with such complex types arises:
The DC Application Profile guidelines define Application Profiles as flat structures by allowing for relational attributes such as
- Refines
- Refined By
- Encoding Scheme For
- Has Encoding Scheme
- Similar To