Difference between revisions of "User:Inga/container tocs"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
* [[ESciDoc Container Toc]] states "The only reason to provide more than one TOC for a container resource would be to have different selections of the container resource members. It is assumed that there is no use case for different selections of members of one single container. | * [[ESciDoc Container Toc]] states "The only reason to provide more than one TOC for a container resource would be to have different selections of the container resource members. It is assumed that there is no use case for different selections of members of one single container. | ||
* One TOC per container? | * One TOC per container? | ||
* What is the difference between | |||
Assumptions & : | Assumptions & : | ||
| Line 17: | Line 18: | ||
* Synchronizing terms and definitions for | * Synchronizing terms and definitions for | ||
** container | ** container | ||
** table of contents/tableOfContents/TOC - if the escidoc toc is semantically in sync with the METS concept | ** table of contents/tableOfContents/TOC - if the escidoc toc is an ordered and grouped overview of [selected] members, it may be semantically in sync with the METS concept "structMap" -> renaming to avoid confusion? | ||
** StructuralMap - if a structural map is the "flat" list of item reference | ** StructuralMap - if a structural map is the "flat" list of item reference, it may be semantically in sync with the METS concpet "fileSec" -> renaming? | ||
Revision as of 18:13, 13 March 2008
Resources available about containers and tocs:
- ESciDoc_Services:core_services shortly describes the Container Handler service and introduces the terms "Container", "TableOfContents" and "StructuralMap"
- ESciDoc Container Toc. This document introduces a TOC representation based on RSS 1.0 which is probably no longer in consideration. The Questions & Discussion section may be of further interest.
- API Documentation Container Handler, rest interface, framework release 0.9
Open Questions:
- ESciDoc Container Toc states "Grouping of direct members is not necessary; a hierarchical structure is build by container resources wich are linked as members." -> isn't the toc something like a grouping?
- ESciDoc Container Toc states "The only reason to provide more than one TOC for a container resource would be to have different selections of the container resource members. It is assumed that there is no use case for different selections of members of one single container.
- One TOC per container?
- What is the difference between
Assumptions & :
- Container members are independent from their container, thus each item/container can be member of n containers.
-> The requirement that "non-editors" would like to provide individual TOCs for an existing container - The TOC is an optional, but integral component/member of the container
->Changes in the TOC object should version the container object
Todos:
- Synchronizing terms and definitions for
- container
- table of contents/tableOfContents/TOC - if the escidoc toc is an ordered and grouped overview of [selected] members, it may be semantically in sync with the METS concept "structMap" -> renaming to avoid confusion?
- StructuralMap - if a structural map is the "flat" list of item reference, it may be semantically in sync with the METS concpet "fileSec" -> renaming?