--
You received this message because you are subscribed to the Google Groups "Fedora Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-communi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks Andrew.
Does the fcrepo4-vagrant include ACL and Audit
features? I was not sure and chose the war with ACL and Audit features instead.
I think REST API should handle Object and Datastream manipulation well. In Fedora 3, In order to expose methods, I also need to associate content models to an object. Typically I add a triple in “RELS-EXT” datastream for one content model association. For example, in order to use infusionCModel methods, I provide following triple to RELS-EXT:
Subjet: info:fedora/Application:infusion
Predicate: fedora-model:hasModel
Object: info:fedora/domain:infusionCModel
The “Application:infusion” is a PID for the infusion object. This object provides all required resources (data, js, css, xslt) to run the application
The “domain:infusionCModel” together with “domain:infusionSDef” and “domain:infusionSDep” provide interfaces and WSDL for “Application:infusion” to access other services. Currently, many services are running through SAXON engine that bundled with Fedora 3.
Now, my question for Fedora 4 is:\
1. How do I associate a content model (or similar component) to a container?
2. How do I define the interfaces that CMA provided in Fedora 3, so that my object (container) can utilize other applications’ services?
My email reply got rejected. So just paste the same email here.
Thanks,
Wei
Thanks Andrew.
Does the fcrepo4-vagrant include ACL and Audit features? I was not sure and chose the war with ACL and Audit features instead.
I think REST API should handle Object and Datastream manipulation well. In Fedora 3, In order to expose methods, I also need to associate content models to an object. Typically I add a triple in “RELS-EXT” datastream for one content model association. For example, in order to use infusionCModel methods, I provide following triple to RELS-EXT:
Subjet: info:fedora/Application:infusion
Predicate: fedora-model:hasModel
Object: info:fedora/domain:infusionCModel
The “Application:infusion” is a PID for the infusion object. This object provides all required resources (data, js, css, xslt) to run the application
The “domain:infusionCModel” together with “domain:infusionSDef” and “domain:infusionSDep” provide interfaces and WSDL for “Application:infusion” to access other services. Currently, many services are running through SAXON engine that bundled with Fedora 3.
Now, my question for Fedora 4 is:\
1. How do I associate a content model (or similar component) to a container?
2. How do I define the interfaces that CMA provided in Fedora 3, so that my object (container) can utilize other applications’ services?
Thanks,
Wei
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
To me, it sounds like this use case, which was also motivated from the wish to retain some CMA-like functionality:
https://wiki.duraspace.org/pages/viewpage.action?pageId=68059414
Egbert Gramsbergen