Difference between revisions of "Talk:ESciDoc Application Profiles"
Jump to navigation
Jump to search
Line 33: | Line 33: | ||
* Similar To | * Similar To | ||
One possible solution to the dilemma would look like: | One '''possible solution''' to the dilemma would look like: | ||
* use "person" as an element that refines "creator" with an encoding scheme that defines its components (complete name, family name, ...) | * use "person" as an element that refines "creator" with an encoding scheme that defines its components (complete name, family name, ...) | ||
* use "organisation" as an element that refines "creator" with a corresponding encoding scheme | * use "organisation" as an element that refines "creator" with a corresponding encoding scheme | ||
Line 39: | Line 39: | ||
**attach creatorRole as component of "person" and "organisation" with yet another encoding scheme (not sure whether or not nested encoding schemes are allowed) | **attach creatorRole as component of "person" and "organisation" with yet another encoding scheme (not sure whether or not nested encoding schemes are allowed) | ||
**or create an element "creatorRole" on the same level as "person" and "organisation" with a corresponding encoding scheme | **or create an element "creatorRole" on the same level as "person" and "organisation" with a corresponding encoding scheme | ||
'''Are there other suggestions?''' |
Revision as of 14:30, 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
One possible solution to the dilemma would look like:
- use "person" as an element that refines "creator" with an encoding scheme that defines its components (complete name, family name, ...)
- use "organisation" as an element that refines "creator" with a corresponding encoding scheme
- either
- attach creatorRole as component of "person" and "organisation" with yet another encoding scheme (not sure whether or not nested encoding schemes are allowed)
- or create an element "creatorRole" on the same level as "person" and "organisation" with a corresponding encoding scheme
Are there other suggestions?