...

1. A spreadsheet was programmatically created by Justin Littman (Stanford) from the Sinopia PCC Templates according to the DCMI Tabular Application Profile specification. A copy of the spreadsheet (March 2021 Comparison of PCC Sinopia Templates and SVDE Data) was used to evaluate row by row if SVDE PCC data has triples conforming to the template.
   1. No systematic attempt has been made to perform analysis from the other direction (to see if every pattern in SVDE is reflected in the Sinopia PCC templates), but there are undoubtably SVDE patterns absent from the Sinopia templates.
2. Analysis of the SVDE PCC data was performed using SPARQL queries on the LD4P cache available at: http://services.ld4l.org/fuseki/dataset.html?tab=query&ds=/PCC.
3. Every attempt was made to account for different patterns for bf:Works in the SVDE data, but the patterns may be too different to reconcile neatly with the Sinopia PCC Works patterns. This reflects the need for the community to decide on similar patterns for reflecting the WEMI model in BF, assuming this is a goal.
4. The bflc:Relationship pattern to capture relationships (between Works and other works, and Instances and other Instances) in the templates and in the SVDE data are not intuitive. There should be further analysis and community discussion about the extent to which the bflc:Relationship pattern should be used and/or avoided. 
5. The property bf:issuance seems to not be consistently applied for Serials in the SVDE data, and perhaps Monographs. This made it difficult to confidently say the SVDE data complied with the PCC templates usage of http://id.loc.gov/vocabulary/issuance/mono and http://id.loc.gov/vocabulary/issuance/serl for monographs and serial respectively as bf:issuance value. We need to solidify what pattern the community should use to confidently signal this information.

Categories of Differences

How SVDE Data and the Sinopia PCC Templates Differ

There are significant differences between the Sinopia PCC templates and SVDE data. In March 2021 Comparison of PCC Sinopia Templates and SVDE Data, Column L (with the header "SVDE Differences") captures compatibility and differences between the data and templates. Areas of compatibility are highlighted green, and differences are highlighted yellow. It may be that not all differences require action.

The type so of changes include, but are Including, but not limited to:

• SVDE data uses URIs for entities that Sinopia template creates bank nodes for.
• Sinopia template allows for URIs or literal, while SVDE only uses URIs.
• BIBFRAME class/subclass usage doesn't line up exactly (e.g. bf:Titles and bf:Instance subclasses)
• SVDE data does not use http://sinopia.io/vocabulary/hasResourceTemplate to connect entities to templates.
• Properties uses in templates are not found in the SVDE data.
• Properties used in the SVDE data are not found in templates.
• SVDE data links to values (often from id.loc.gov) seemingly not permitted by the sinopia:LabeledResource template.

SVDE/Sinopia Dataflow Questions

There are significant differences between the Sinopia PCC templates and SVDE data. In March 2021 Comparison of PCC Sinopia Templates and SVDE Data, Column L (with the header "SVDE Differences") captures compatibility and differences between the data and templates. Areas of compatibility are highlighted green, and differences are highlighted yellow; it may be that not all differences require reconciliation. We need to clearly define what actions we expect to be able to performed on the SVDE data in the Sinopia environment and vice versa. Depending on the answers to the following questions, we may need to consider changes to the tooling, data outputs, and/or templates.

...