lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2021-11-22T11:15:42Zhttps://gitlab.gwdg.de/lido/development/-/issues/130Change element sequence in <place> element2021-11-22T11:15:42ZJutta LindenthalChange element sequence in <place> elementlido:partOfPlace should be the last sub-element within lido:place, otherwise nestings of lido:place are almost anreadable and extremely difficult to edit.lido:partOfPlace should be the last sub-element within lido:place, otherwise nestings of lido:place are almost anreadable and extremely difficult to edit.LIDO 1.1 finalmmarkus1mmarkus12021-11-16https://gitlab.gwdg.de/lido/development/-/issues/118Align description for <administrativeMetadata> and <descriptiveMetadata>2021-09-02T12:22:05ZHanna-Lena StolzAlign description for <administrativeMetadata> and <descriptiveMetadata>Explain different cardinality in root and child elementExplain different cardinality in root and child elementLIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolz2021-08-01https://gitlab.gwdg.de/lido/development/-/issues/143please remove from cc2022-02-24T09:38:40ZMathias Goebelplease remove from cci am getting noticed at your new issues in the cc section. can someone pls remove from the templates? thx.i am getting noticed at your new issues in the cc section. can someone pls remove from the templates? thx.https://gitlab.gwdg.de/lido/development/-/issues/134Schematron Rules do not apply to sch:assert2021-12-16T17:53:06Zmmarkus1Schematron Rules do not apply to sch:assertThe transformation does only include schematron rules that have sch:extends. A transformation for sch:assert need to be implemented.The transformation does only include schematron rules that have sch:extends. A transformation for sch:assert need to be implemented.mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/133Optimize CSS spacing in the accompanying document (terminology recommendations).2021-12-17T12:12:19ZHanna-Lena StolzOptimize CSS spacing in the accompanying document (terminology recommendations).mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/132Remove XSD heading complexTypes from page and menu2021-12-17T08:59:11ZHanna-Lena StolzRemove XSD heading complexTypes from page and menuLIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/131Introduction text for accompanying document (terminology recommendations)2021-12-17T12:02:06ZHanna-Lena StolzIntroduction text for accompanying document (terminology recommendations)Introduction text for accompanying document (terminology recommendations) would be helpful. Explain, what this document is about etc
Must be implemented in the transformationIntroduction text for accompanying document (terminology recommendations) would be helpful. Explain, what this document is about etc
Must be implemented in the transformationmmarkus1Hanna-Lena StolzJutta Lindenthalmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/128RelatedEventSet and RelatedEvent have the same label2021-11-15T10:42:53ZGudrun KnausRelatedEventSet and RelatedEvent have the same labelIn http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.pdf the element RelatedEventSet has the label Related Event and so does the element Related Event. Shouldn't be the label Related Event Set? (similar to Event Set?)In http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.pdf the element RelatedEventSet has the label Related Event and so does the element Related Event. Shouldn't be the label Related Event Set? (similar to Event Set?)Hanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/124style new class for elements which can not be expanded in tree view/add button2021-08-09T13:26:50ZHanna-Lena Stolzstyle new class for elements which can not be expanded in tree view/add buttonstyle new class ("ground") for elements which can not be expanded in tree view
add button "expand all" and "hide all"style new class ("ground") for elements which can not be expanded in tree view
add button "expand all" and "hide all"LIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/123sourceAppellation2021-08-25T08:12:24ZGudrun KnaussourceAppellationA titleSet can contain a title in different languages, each specified by the individual language attribute. In case each translation of the title stems from a different source I need to create a new titleSet for each title, otherwise the...A titleSet can contain a title in different languages, each specified by the individual language attribute. In case each translation of the title stems from a different source I need to create a new titleSet for each title, otherwise the titleSet becomes invalid.
Look at this invalid example:
<lido:titleSet lido:type="http://vocab.getty.edu/aat/300417194">
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="en">
Sketch: The Death of Henry IV and the Proclamation of the Regency</lido:appellationValue>
<lido:sourceAppellation>https://rkd.nl/explore/images/217905</lido:sourceAppellation>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="fr">
L'Apothéose de Henri IV et la proclamation de la régence de Marie de Médicis, le 14 mai 1610</lido:appellationValue>
<lido:sourceAppellation>sampleValue</lido:sourceAppellation>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="nl">
Olieverfschets: De dood en apotheose van Hendrik IV en het overdragen van het regentschap
aan Maria de' Medici, 14 maart 1610</lido:appellationValue>
<lido:sourceAppellation>sampleValue</lido:sourceAppellation>
</lido:titleSet>
In comparison to this valid snippet:
<lido:titleSet lido:type="http://vocab.getty.edu/aat/300417194">
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="en"
>oil sketch: The death and apothesis of Henry IV and the proclamation of the regency of
Maria de' Medici, 14 March 1610 </lido:appellationValue>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="fr">
L'Apothéose de Henri IV et la proclamation de la régence de Marie de Médicis, le 14 mai
1610</lido:appellationValue>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="nl">
Olieverfschets: De dood en apotheose van Hendrik IV en het overdragen van het regentschap
aan Maria de' Medici, 14 maart 1610 </lido:appellationValue>
<lido:sourceAppellation xml:lang="de"
>https://rkd.nl/explore/images/217905</lido:sourceAppellation>
</lido:titleSet>
Is there a chance to make the sourceAppellation element repeatable within the same titleSet?Hanna-Lena StolzRegine SteinJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/122resourceID: Change repeatablilty2021-06-25T09:47:59ZHanna-Lena StolzresourceID: Change repeatabliltyRepeatabilty needs to be adjusted to minOccurs="unbounded"Repeatabilty needs to be adjusted to minOccurs="unbounded"LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/119Terminology/Format recommendation: accompanying document2021-08-11T11:23:26ZHanna-Lena StolzTerminology/Format recommendation: accompanying documentDesignations and links have to be consolidated.
[Wiki](https://wiki.dnb.de/pages/viewpage.action?pageId=202447123)Designations and links have to be consolidated.
[Wiki](https://wiki.dnb.de/pages/viewpage.action?pageId=202447123)LIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/117display element for extentActor needed2021-06-20T15:00:37ZGudrun Knausdisplay element for extentActor neededcontrolled vocabulary in this case is less precise than the possibility to express the extent of participation with a longer sentence. Sample data values:
"Bronzeabguss nachträglich vom Künstler mit Ölfarbe bemalt"
"der Himmel im Bild ...controlled vocabulary in this case is less precise than the possibility to express the extent of participation with a longer sentence. Sample data values:
"Bronzeabguss nachträglich vom Künstler mit Ölfarbe bemalt"
"der Himmel im Bild wurde vom Restaurator 1876 von neuzeitlicher Übermalung befreit".mmarkus1Hanna-Lena Stolzmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/116displayDate needed for vitalDatesActor2021-09-23T12:09:39ZGudrun KnausdisplayDate needed for vitalDatesActorIn the EODEM sample file I have found the following:
```
<lido:vitalDatesActor>
<lido:earliestDate>active about 1506</lido:earliestDate>
<lido:latestDate>died 1576</lido:latestDate>
</lido:vitalDatesActor>
```
My first guess w...In the EODEM sample file I have found the following:
```
<lido:vitalDatesActor>
<lido:earliestDate>active about 1506</lido:earliestDate>
<lido:latestDate>died 1576</lido:latestDate>
</lido:vitalDatesActor>
```
My first guess was to change it into something like this:
```
<lido:vitalDatesActor>
** <lido:displayDate xml:lang="en">active between 1506 and 1576</lido:displayDate>**
<lido:earliestDate>1506</lido:earliestDate>
<lido:latestDate>1576</lido:latestDate>
</lido:vitalDatesActor>
```
but a) this it not valid and b) the type of date still needs to be characterized.
So it might look like this:
```
<lido:vitalDatesActor lido:type="http://terminology.lido-schema.org/lido00819">
** <lido:displayDate xml:lang="en">active between 1506 and 1576</lido:displayDate>**
<lido:earliestDate lido:type="estimated_date">1506</lido:earliestDate>
<lido:latestDate lido:type="estimated_date">1506</lido:latestDate>
</lido:vitalDatesActor>
<lido:vitalDatesActor lido:type="ttp://terminology.lido-schema.org/lido00787">
<lido:earliestDate lido:type="estimated_date">1576</lido:earliestDate>
<lido:latestDate lido:type="estimated_date">1576</lido:latestDate>
</lido:vitalDatesActor>
```
What do you think?Jutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/112resourceSource2021-05-28T17:15:49ZGudrun KnausresourceSourceWhat kind of type attributes are available for the element resourceSource? No terms in X-Tree or Wiki found.What kind of type attributes are available for the element resourceSource? No terms in X-Tree or Wiki found.Hanna-Lena StolzJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/111Add references for source elements2021-05-25T09:57:43ZJutta LindenthalAdd references for source elementsJutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/108sourceActorInRole- type attribute needed2021-05-21T05:19:10ZGudrun KnaussourceActorInRole- type attribute neededhttp://balilabs.de/rr/edlido.html?e=Beispielschnipsel_attribution.xml
In order to give a hint, whether the source is an uri or just a text (whether printed or not), shall we introduce a type attribute for any kind of source element? (no...http://balilabs.de/rr/edlido.html?e=Beispielschnipsel_attribution.xml
In order to give a hint, whether the source is an uri or just a text (whether printed or not), shall we introduce a type attribute for any kind of source element? (not sure)
Might also be relevant for:
sourceRelatedWorkSet/sourceAppellation/sourceRepositorySet/sourceDescriptiveNote/sourceMaterialsTechHanna-Lena StolzJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/101Replace "for a single" by "for one" where appropriate2021-05-13T11:11:44ZJutta LindenthalReplace "for a single" by "for one" where appropriateThe phrase "for a single [entity] ..." in the sense of "one [entity] per element" may be ambiguous. Therefore the phrase is replaced by "for one [entity] ...".The phrase "for a single [entity] ..." in the sense of "one [entity] per element" may be ambiguous. Therefore the phrase is replaced by "for one [entity] ...".Jutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/100Rename "For an attribute the element holds" in Terminology/Format recommendation2021-08-11T09:45:20ZJutta LindenthalRename "For an attribute the element holds" in Terminology/Format recommendationRename the phrase "For an attribute the element holds" in Terminology/Format recommendation for LIDO elements into:
"For the type attribute"
Example <classification>
Terminology/Format recommendation For the element: Linked open vocabul...Rename the phrase "For an attribute the element holds" in Terminology/Format recommendation for LIDO elements into:
"For the type attribute"
Example <classification>
Terminology/Format recommendation For the element: Linked open vocabulary for Classification
For the type attribute: LIDO Terminology for Classification typemmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/99Do not show Description of attributes in elements (except for type attributes)2021-06-21T14:07:50ZJutta LindenthalDo not show Description of attributes in elements (except for type attributes)1. Do not show Description of attributes in elements (except for type attributes)
2. Delete Terminology/Format recommendation for these attributes
Example <[place](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#place)...1. Do not show Description of attributes in elements (except for type attributes)
2. Delete Terminology/Format recommendation for these attributes
Example <[place](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#place)>
Attributes (except type attributes) are described seperately. There is no need to show descriptions for attributes in the element's description. Further reasons to abandon the display of attribute annotations:
- Since "Data values" does not distinguish between elements and attributes, the reference may be ambiguous.
- Only a seamingly arbitrary selection of attributes is shown.LIDO 1.1 final