...
- PCDM examples
- In an effort to bring some reality and clarity to how the Portland Common Data Model (PCDM) can be applied to existing repository use cases, the following collection-types were mapped into PCDM:
- Sufia / ScholarSphere - implementation of PCDM to extend Sufia Generic file capability to support complex works
- GeoHydra - implementation of PCDM for GIS
- Simple Postcard Example
- Disk Image Example
- Book
- In an effort to bring some reality and clarity to how the Portland Common Data Model (PCDM) can be applied to existing repository use cases, the following collection-types were mapped into PCDM:
- PCDM JSON-LD @context
- During a session detailing JSON-LD, it was suggested that a relatively simple and straight-forward exercise of creating a JSON-LD @context for the PCDM would go a long way towards facilitating consistent usage of JSON-LD with PCDM
- If you are interested in JSON-LD and/or PCDM, here is a ticket for this high-value, low-effort community contribution
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1415
- PCDM deploying to pcdmto pcdm.org with org with scripts
- In order to automate the deployment of the PCDM ontology based on updates to the 'master' branch, an auto-deploy setup should be established along the lines of the IIIF prior art
- Mega-thread discussion and next steps
Server-managed triples (SMT)
SMTs should be satisfied by the existing 'Prefer' header on GET requests (Prefer: return=representation; omit="http://fedora.info/definitions/v4/repository#ServerManaged")
This should be verified under a variety of scenarios
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1416
Non-repo subjects
For LDP compliance, ensure Fedora provides feedback when triples can not / will not be persisted
On PUT, Fedora `must` fail - http://www.w3.org/TR/ldp/#h-ldprs-put-failed
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1417
On POST/PATCH, Fedora must advertise constraints - http://www.w3.org/TR/ldp/#h-ldpr-http_post
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1418
Possibly the following blank-node/owl:sameAs pattern can address the issue of using non-repo resources
No Format ns:Object1 a some:LocalResource ; dcterms:creator [ rdfs:label "Rob Sanderson" ; owl:sameAs <http://www.stanford.edu/~azaroth/rdf#me> ]
LDP-RS creation on client request
Initially, respond with "501 Not Implemented" when clients request creation of LDP-RS
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1396
Eventually, TBD depending on further consensus/discussion
- Ugly repository URLs with nested paths are a direct result of underlying performance mitigation
- Investigate cost of JBoss to work ModeShape ticket:
- We should continue to make clear to community that F4 can support XML datastreams if users are not ready to transition to RDF
- There is community interest and support in moving F4 towards Memento for versioning
...