Difference between revisions of "Faces Application Profiles"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* [[Faces_Application_Profile_FacesItem|Faces Application Profile FacesItem]] | * [[Faces_Application_Profile_FacesItem|Faces Application Profile FacesItem]] | ||
* [[Faces_Application_Profile_FacesPerson|Faces Application Profile FacesPerson]] (extended [[ESciDoc_Application_Profile_Person|ESciDoc Person]]) | * [[Faces_Application_Profile_FacesPerson|Faces Application Profile FacesPerson]] (extended [[ESciDoc_Application_Profile_Person|ESciDoc Person]]) | ||
* [[ | * [[Faces_Application_Profile_Organization|Faces Application Profile Organization]] (similar to [[ESciDoc_Application_Profile_Organization|ESciDoc Organization]]) | ||
==Faces Encoding Schemes== | ==Faces Encoding Schemes== | ||
Revision as of 15:35, 31 July 2008
|
Aim and Scope[edit]
The Faces Application Profiles (AP) document the descriptive elements used by the eSciDoc solution Faces to describe its content entities. Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in these APs.
In the first step, the APs are meant for documenting the existing requirements for the metadata. Later on, the APs shall be transformed to RDF.
Designated community[edit]
Functional requirements[edit]
Data model[edit]
If there is an overall data model. If not, detailed data models can be found at the beginning of each application profile.
Faces Application Profiles[edit]
- Faces Application Profile Album (similar to ESciDoc Publication)
- Faces Application Profile Collection (similar to ESciDoc Publication)
- Faces Application Profile FacesFile (similar to ESciDoc File)
- Faces Application Profile FacesItem
- Faces Application Profile FacesPerson (extended ESciDoc Person)
- Faces Application Profile Organization (similar to ESciDoc Organization)