Hi David,

Right, Cargo is stricter than Semantic MediaWiki about entering data: you can't come up with your own property names and their values. I think that’s a plus: the data structure, set of allowed values, etc. should be consistent across all pages, not subject to arbitrary changes on individual pages. If there are subtleties in the data that can't be fully handled with the current structure (and there often are), then you indeed may have to consider those kinds of of options, and decide in each case on the best tradeoff between simplicity and flexibility.


On Thu, Aug 26, 2021, 9:43 AM David Epstein <davideps@umich.edu> wrote:
When I last tried semantic mediawiki (years ago), it permitted (perhaps even emphasized) generating structured data through writing that contained typed links. The "type" was a predicate that explained the relationship between two pages. I think it was also possible to store a tuple of data inside the link, which may convey the strength of the predicate (for example) when such information was important and ignore it when it was not important (I may be confusing this functionality with another extension)

Is any of this inline schema building possible with Cargo or are all typed links made in the form data fields? For example, in the common AUTHORS and BOOKS example, what happens if the AUTHOR is actually unknown but there are several likely AUTHORS? One option may be to add a whole field to BOOKS for LIKELY AUTHORS. Another way might be to create an intermediate page AUTHORSHIP that ties AUTHOR to BOOK with a field that explains the relationship in more detail. But, perhaps there is a way to add more nuance to the AUTHOR assignment itself? Could this information be conveyed in the AUTHORS field through an additional piece of information placed in parentheses?


MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/