Subject: https://w3id.org/scholarlydata/inproceedings/www2012/dev/50Property: http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttps://w3id.org/scholarlydata/ontology/conference-ontology.owl#InProceedingshttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialObjecthttp://www.w3.org/2002/07/owl#Thinghttp://purl.org/spar/fabio/ProceedingsPaperhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationObjecthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Objecthttp://www.w3.org/2000/01/rdf-schema#ResourceProperty: http://www.w3.org/2000/01/rdf-schema#labelDecoupling Content ManagementProperty: http://www.w3.org/2002/07/owl#sameAshttp://data.semanticweb.org/conference/www/2012/dev/50Property: http://swrc.ontoware.org/ontology#abstractTraditional content management systems (CMS) are following a monolithic architecture. If they wouldn't, one could exchange UI components much easier and CMS developers could share many of the front-end components, also divide the effort and multiply quality. Our approach to decouple content management is to use RDFa enhanced templating and Backbone as a mid-layer to instantiate a rich editor and other interactive widgets when the user would like to edit the content. We show components and prototypes in development.Property: http://purl.org/dc/elements/1.1/creatorhttps://w3id.org/scholarlydata/person/henri-bergiushttps://w3id.org/scholarlydata/person/szabolcs-gruenwaldProperty: http://purl.org/dc/elements/1.1/subjectSemantic TechnologiesContent Management SystemsJavaSciptProperty: http://purl.org/dc/elements/1.1/titleDecoupling Content ManagementProperty: http://purl.org/ontology/bibo/authorListhttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50/authorListProperty: http://xmlns.com/foaf/0.1/makerhttps://w3id.org/scholarlydata/person/henri-bergiushttps://w3id.org/scholarlydata/person/szabolcs-gruenwaldProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#abstractTraditional content management systems (CMS) are following a monolithic architecture. If they wouldn't, one could exchange UI components much easier and CMS developers could share many of the front-end components, also divide the effort and multiply quality. Our approach to decouple content management is to use RDFa enhanced templating and Backbone as a mid-layer to instantiate a rich editor and other interactive widgets when the user would like to edit the content. We show components and prototypes in development.Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasAuthorListhttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50/authorListProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#isPartOfhttps://w3id.org/scholarlydata/conference/www/2012/dev/proceedingshttps://w3id.org/scholarlydata/conference/www/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#keywordJavaSciptContent Management SystemsSemantic TechnologiesProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#titleDecoupling Content Management

Subject: https://w3id.org/scholarlydata/conference/www/2012/dev/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasParthttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50

Subject: https://w3id.org/scholarlydata/conference/www/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasParthttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50

Subject: https://w3id.org/scholarlydata/person/henri-bergiusProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50

Subject: https://w3id.org/scholarlydata/person/szabolcs-gruenwaldProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/www2012/dev/50