2010
DOI: 10.1007/978-3-8348-9645-2
|View full text |Cite
|
Sign up to set email alerts
|

Architecture and Methods for Flexible Content Management in Peer-to-Peer Systems

Abstract: At times when the IT manager's best friend is systems consolidation (which is a euphemism for centralisation), it may come somewhat as a surprise for you that this book investigates decentralisation in the context of content management systems. It may seem quite obvious that content will and should be managed by the party who creates and owns the content, and hence should be held in a-somewhat-centralised and managed location. However, over the past few years, we have been witnesses of some important trends an… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2011
2011
2011
2011

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 0 publications
0
1
0
Order By: Relevance
“…We consider that documents are mere representations of content following a particular format (most often closed-source). A content management system is build from three main components [9] responsible with content a) collection, b) management, and c) publishing. Content collection consists in [10] i) authoring -create new content, ii) acquisition -get content from existing sources, iii) conversion -adapt content to system requirements, and iv) aggregation -split existing content in smaller pieces and augment them with metadata.…”
Section: A Requirements Analysismentioning
confidence: 99%
“…We consider that documents are mere representations of content following a particular format (most often closed-source). A content management system is build from three main components [9] responsible with content a) collection, b) management, and c) publishing. Content collection consists in [10] i) authoring -create new content, ii) acquisition -get content from existing sources, iii) conversion -adapt content to system requirements, and iv) aggregation -split existing content in smaller pieces and augment them with metadata.…”
Section: A Requirements Analysismentioning
confidence: 99%