Results 86 comments of GVogeler

Is converting `label` to an object with properties `content` and `language` the easiest way? Or is there the possibility to achieve it keeping the current data model valid?

sounds reasonable. So we would replate the `refs` section with something like the following? ``` { "_links": { "curies": [ { "name": "api", "href": "/{rel}", "templated": true } ], "api:factoid-ref"...

The option can include three cases: 1. `false`='and' in a single statement 2. `matchAll `= 'and' in 1-n statements 3. `matchAny `= 'or' in 1-n statements

Keeping the parameter optional would be achieved by excluding it from `complianceLevel=1`

I see two options: 1. sort by mixing hooked-in charters with original charters 2. update `cei:issued` in hooked-in charters when the referenced charter is published. First option is probably too...

Could this chieved by adding the index `[1]` to the `tei:persName` in in https://github.com/icaruseu/mom-ca/blob/master/my/XRX/src/mom/app/index/widget/index.widget.xml#L839 ?

Currently https://www.monasterium.net/mom/index/wikidata?pm=A (for instance) lists the entry with the xml:id `P_wikidata_Q1531556` and several others twice, but it should only be one.

There are probable two options: 1. remove this slot in case of aggregated collections 2. include a computed index methods (exist-trigger) to create an internal representation of these aggregationes The...

Check https://github.com/icaruseu/mom-ca/blob/59703228e9de2b222be9439fc61cdd530a8c78bd/my/XRX/src/mom/app/charter/widget/charter.widget.xml#L1278 , https://github.com/icaruseu/mom-ca/blob/59703228e9de2b222be9439fc61cdd530a8c78bd/my/XRX/src/mom/app/charter/widget/my-charter.widget.xml#L514 and https://github.com/icaruseu/mom-ca/blob/59703228e9de2b222be9439fc61cdd530a8c78bd/my/XRX/src/mom/app/charter/widget/saved-charter.widget.xml#L332 (and consider how to refactor this to have only one definition of this)