Skip to content

Commit

Permalink
Moving displayName and identifier from OrgType to AbstractRoleType
Browse files Browse the repository at this point in the history
  • Loading branch information
semancik committed Jul 31, 2014
1 parent 0b7ac41 commit 3f264a1
Showing 1 changed file with 30 additions and 29 deletions.
59 changes: 30 additions & 29 deletions infra/schema/src/main/resources/xml/ns/public/common/common-3.xsd
Expand Up @@ -6041,6 +6041,35 @@
<xsd:complexContent>
<xsd:extension base="tns:FocusType">
<xsd:sequence>
<xsd:element name="displayName" type="t:PolyStringType">
<xsd:annotation>
<xsd:documentation>
Human-readable name of the role or org. It may be quite long, container national characters
and there is no uniqueness requirement.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>Display Name</a:displayName>
<a:displayOrder>100</a:displayOrder>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>

<xsd:element name="identifier" type="xsd:string" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Identifier of the role or org. It should be a structured information usually used for
refering to the role or org or correlating it in various systems. E.g. numeric organizational
unit identifier, role code, etc. It should be unique in its "own" scope. E.g. an organizational
unit identifier should be unique in the scope of all organizational units but it may conflict
with an identifier of a project.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>Identifier</a:displayName>
<a:displayOrder>110</a:displayOrder>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>

<xsd:element name="inducement" type="tns:AssignmentType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Expand Down Expand Up @@ -6717,35 +6746,7 @@
<xsd:complexContent>
<xsd:extension base="c:AbstractRoleType">
<xsd:sequence>
<xsd:element name="displayName" type="t:PolyStringType">
<xsd:annotation>
<xsd:documentation>
Human-readable name of the org. It may be quite long, container national characters
and there is no uniqueness requirement.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>Display Name</a:displayName>
<a:displayOrder>100</a:displayOrder>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>

<xsd:element name="identifier" type="xsd:string" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Identifier of the org. It should be a structured information usually used for
refering to the org or correlating it in various systems. E.g. numeric organizational
unit identifier. It should be unique in its "own" scope. E.g. an organizational unit identifier
should be unique in the scope of all organizational units but it may conflict with an
identifier of a project.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>Identifier</a:displayName>
<a:displayOrder>110</a:displayOrder>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>


<xsd:element name="orgType" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Expand Down

0 comments on commit 3f264a1

Please sign in to comment.