- Your Fedora repository is a part of the Web
- What are the special qualities of your part of the Web?
- Durability
- Connections to the particular communities you serve.
- What qualities does your part of the Web share with the rest of the Web?
- HTTP, RDF, and RFDS/OWL/SKOS as common "languages"
- Good choices for syntax and semantics help us support our values
- We're interested in durability
- For syntax, that means sharing your syntax with a big community. HTTP does this.
- For semantics, that means sharing your semantics with a community committed to the same worldview. RFDS/OWL/SKOS help with this.
- More and more communities are publishing their common semantics in these languages. Can you think of some in use for your community?
- We're interested in extensibility
- Extensible syntax is minimal but powerful. RDF is this.
- Extensible semantics choose for open assumptions like OWA and against global conditions like UNA.
- We're interested in interoperability.
- Common syntax is completely necessary to interoperability.
- Common semantics lowers the cost of interoperability.
- Relationships to Fedora 3 concepts
- Fedora 3 content modeling did a lot of things at once!
- Ontology
- Workflow
- Validation
- Where do these functionalities go in Fedora 4?
- Ontology
- Workflow
- Outside the repository, at least in most circumstances
- Apache Camel now under extensive investigation
- Validation
- Suggestions?
- Make thoughtful commitments
- Your commitment to Fedora appears in:
- the way you manage your resources with respect to persistence, fixity, and other low-level technical aspects.
- Your commitment to the specific communities you serve appears in:
- what your resources mean (the vocabularies and ontologies you use to do content modeling) and
- your workflows, which are useful to the members of your communities.
- What does this look like in practice?
- Fedora is an object repository, not a triple store or general semantic store.
- Only put things in your Fedora repository for which only you are responsible
- For things for which the communities you serve are responsible, put them in other places (e.g. triple stores, Linked Data caches)
- Common vocabularies. What such vocabularies are you using now? Where are you storing or caching them?
- Common ontologies.
- Authorized facts (e.g. personal or corporate authority information).
- Don't build so that your repository is made responsible for anything other than the durability of your own stuff
- Don't provide discovery services directly over Fedora (don't use Fedora as an index).
- Don't use your repository to manage information that is ultimately transactional. E.g.,
- Identity management, groups management
- Workflow state a la Stanford "robot" systems (maybe an edge case)
- Choosing common vocabularies (common semantics) lets us share work with the communities that use those vocabularies
- MeSH example
- Choosing common ontologies (common semantics) lets us share work with the communities that see the world that same wayInferencing example using Plant Ontology
{"serverDuration": 94, "requestCorrelationId": "b4258ec1ce296563"}