
> The part I'm not getting is why this thread is discussing application-specific requirements for structural constraints on data
> without reference to BIBFRAME profiles, which are _all about_ specifying structural constraints on data.

Because this thread, to my understanding, isn't about structural constraints at all, and never was. Structural constraints are an interesting topic, but as I understood Rob Sanderson's original critique, the question of "types vs. properties" isn't about constraint at all. It's about extension.

Yes, precisely.  The constraints are a distraction that came in from the discussion over whether it was a good idea to *require* inferencing or not.

Rob

--
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305
https://listserv.loc.gov/cgi-bin/wa?A3=ind1411&L=BIBFRAME&E=quoted-printable&P=1006571&B=--047d7bacb50297131e050782b632&T=text%2Fhtml;%20charset=UTF-8
listserv.loc.gov
crawl=CC-MAIN-2020-45
1449
application/http; msgtype=response
sha1:JNIVDY54OOKBBIUK62ELVXYWAA2GPVRW
<urn:uuid:f678a498-7807-49e9-bb06-ed263742c5be>
2020-10-20T15:39:47Z
140.147.239.86
text/html
sha1:LNLRSL2X3AXIGSD3UXMY7SDPTPORYEFX
<urn:uuid:800cbe4c-4f27-42d0-9f16-7cb1d1677a95>
https://listserv.loc.gov/cgi-bin/wa?A3=ind1411&L=BIBFRAME&E=quoted-printable&P=1006571&B=--047d7bacb50297131e050782b632&T=text%2Fhtml;%20charset=UTF-8
response
<urn:uuid:bbe70d95-d18b-4982-a2f6-9e26fde3ff73>
isPartOf: CC-MAIN-2020-45
publisher: Common Crawl
description: Wide crawl of the web for October 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-199.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/