You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@apdavison not a bad idea. those would need to be attached to the (web) service version. should be optional (in case services do not have a proper pattern)
Option A: A ServiceLinkPattern schema could have the following properties, if it would be linked from a FileRepository under the property "serviceLinkPattern":
sourceFileNamePattern (regex for the URL (?) of the file/file bundle that can be opened in the service)
linkPattern (regex for the URL that shows the connected file/file bundle in the service)
service (link to the WebServiceVersion)
I'm not sure though if it is smart to link it to the data repository.
Option B: A ServiceLinkPattern schema could have the following properties, if it would be linked from a WebServiceVersion under the property "serviceLinkPattern":
sourceFileRepository (URL to the source file repo or link to the FileRepository)
sourceFileNamePattern (regex for the URL (?) of the file/file bundle that can be opened in the service)
linkPattern (regex for the URL that shows the connected file/file bundle in the service)
Note that a WebServiceVersion could have 1-N ServiceLinkPattern (as many as there are file repos)
This would support auto-generating service links.
cf ContentTypePattern, FilePathPattern, FileRepositoryStructure
The text was updated successfully, but these errors were encountered: