-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
additional names for a centre #245
Comments
Prioritising for myself; it's a short job and it would be good to handle it asaP. |
This is what we have there right now, it must have been a rather quick patch: <xs:element name="centre" maxOccurs="unbounded">
<xs:complexType mixed="true">
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element ref="a"/>
<xs:element ref="nodeInfo"/>
</xs:sequence>
<xs:attribute name="id" type="xs:ID" use="required"/>
<xs:attribute name="deposition" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
</xs:element> I suggest to change "name" to "centreName", to make it more specific. I also suggest that |
Eliza says that |
|
In the suggestion, |
OK, so the first step could be for me to change |
Just a remark for now: if we end up using |
Interim update (no, we're not done yet, it seems): <xs:element name="centre">
<xs:complexType mixed="false">
<xs:sequence>
<xs:element name="name" type="xs:string">
<xs:annotation>
<xs:documentation>the full name of the centre</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="registryLink" minOccurs="1" maxOccurs="unbounded"/>
<xs:element ref="nodeInfo"/>
</xs:sequence>
<xs:attribute name="id" type="xs:string" use="required">
<xs:annotation>
<xs:documentation xml:lang="en">'shorthand' for the centre that acts as its ID</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="deposition" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
</xs:element> So, So we need to coordinate on this change, and maybe actually postpone it till post-CAC -- we should restrict ourselves to fixes and cosmetics, for the time being. BUT let me add Eliza to the assignees, and let me drop the priority label. |
Meeting decision: keep it in this milestone and try to handle it before the release. Piotr will prioritize it for himself. |
We've already seen issues where a centre is called one name in the CLARIN network, another in Text+, and has a third name for other purposes (or there exist minute organisational differences perhaps not fully relevant from the point of view of the SIS).
The listing of TALAR in re3data is a nice example of several issues, notably of handling the naming differences:
https://www.re3data.org/repository/r3d100010152
Let us make it possible to use more than one name for a centre / repository. Let these names get qualified by optional attributes whose content is going to end up in brackets after the name. Hmm, or a loose attribute as above and a controlled
@ri
attribute, that could be used for the purpose of filtering...One way or another, this is a schema + implementation ticket, so I am self-assigning it for the schema part and will switch to Eliza once I'm done.
The text was updated successfully, but these errors were encountered: