From ed5640d8b587fbcfed7dd7967f3de04b37a76f26 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 11:06:44 +0200 Subject: Adding upstream version 4:7.4.7. Signed-off-by: Daniel Baumann --- sfx2/classification/CommonTypes.xsd | 103 +++++ sfx2/classification/README | 7 + sfx2/classification/baf.xsd | 299 ++++++++++++++ sfx2/classification/baf_loext.xsd | 19 + sfx2/classification/example.xml | 89 ++++ sfx2/classification/example_ca-ES.xml | 71 ++++ sfx2/classification/example_fr-FR.xml | 84 ++++ sfx2/classification/example_hu-HU.xml | 71 ++++ sfx2/classification/example_nl-NL.xml | 71 ++++ sfx2/classification/example_pt-BR.xml | 89 ++++ sfx2/classification/example_sl-SI.xml | 76 ++++ sfx2/classification/example_zh-CN.xml | 89 ++++ sfx2/classification/xAL-types.xsd | 510 +++++++++++++++++++++++ sfx2/classification/xAL.xsd | 671 +++++++++++++++++++++++++++++++ sfx2/classification/xNL-types.xsd | 221 ++++++++++ sfx2/classification/xNL.xsd | 283 +++++++++++++ sfx2/classification/xlink-2003-12-31.xsd | 89 ++++ 17 files changed, 2842 insertions(+) create mode 100644 sfx2/classification/CommonTypes.xsd create mode 100644 sfx2/classification/README create mode 100644 sfx2/classification/baf.xsd create mode 100644 sfx2/classification/baf_loext.xsd create mode 100644 sfx2/classification/example.xml create mode 100644 sfx2/classification/example_ca-ES.xml create mode 100644 sfx2/classification/example_fr-FR.xml create mode 100644 sfx2/classification/example_hu-HU.xml create mode 100644 sfx2/classification/example_nl-NL.xml create mode 100644 sfx2/classification/example_pt-BR.xml create mode 100644 sfx2/classification/example_sl-SI.xml create mode 100644 sfx2/classification/example_zh-CN.xml create mode 100644 sfx2/classification/xAL-types.xsd create mode 100644 sfx2/classification/xAL.xsd create mode 100644 sfx2/classification/xNL-types.xsd create mode 100644 sfx2/classification/xNL.xsd create mode 100644 sfx2/classification/xlink-2003-12-31.xsd (limited to 'sfx2/classification') diff --git a/sfx2/classification/CommonTypes.xsd b/sfx2/classification/CommonTypes.xsd new file mode 100644 index 000000000..b0404bc9b --- /dev/null +++ b/sfx2/classification/CommonTypes.xsd @@ -0,0 +1,103 @@ + + + + + Specification Name: OASIS CIQ TC - CIQ V3.0 + Description: Defines the W3C schema with commonly used types in the name, address and party schemas + (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT) + Produced by: OASIS Customer Information Quality Technical Committee + URL: http://www.oasis-open.org/committees/ciq + Version: 3.0 + Status: Committee Specification + Copyright: 2006-07, OASIS, http://www.oasis-open.org + Last Modified: 18 September 2007 + Last Modified by: Ram Kumar, Chair, OASIS CIQ TC + + + + + Normalized and Collapsed String + + + + + + + + A list of values to indicate the level of reliability of the data + + + + + The data was validated and is considered to be true and correct. + + + + + Indicates that at least some part of the content is known to be incorrect. + + + + + + + A list of values to indicate the status of the entity + + + + + + Date Valid from to Date Valid to + + + + Could be start date, issue date, validity start date, etc + + + + + Could be end date, expiry date, validity end date, etc + + + + + + A group of commonly used attributes for internal reuse + + + + If set to true then indicates that the value is an abbreviation or initial. If set to false then the value is definitely not an abbreviation. If omitted then it is not known if the value is an abbreviation or not. + + + + + + A group of commonly used attributes for internal reuse + + + + This attribute indicates what level of trust can be given to the parent element. Omit this attribute if the data quality is unknown. If the data quality is known, the value is "Valid, else "InValid" + + + + + Date the data quality is valid from + + + + + Date the data quality is valid to + + + + + + The language used (name of human language, e.g. en, en-US) + + + + Human Language used. e.g. "en", "en-US", "en-AUS", etc + + + + diff --git a/sfx2/classification/README b/sfx2/classification/README new file mode 100644 index 000000000..54c778ff4 --- /dev/null +++ b/sfx2/classification/README @@ -0,0 +1,7 @@ +Involved standards: + +- BAF is +- BAILS is +- xAL is +- xNL is +- xlink is \ No newline at end of file diff --git a/sfx2/classification/baf.xsd b/sfx2/classification/baf.xsd new file mode 100644 index 000000000..abf003b38 --- /dev/null +++ b/sfx2/classification/baf.xsd @@ -0,0 +1,299 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/sfx2/classification/baf_loext.xsd b/sfx2/classification/baf_loext.xsd new file mode 100644 index 000000000..593eb0117 --- /dev/null +++ b/sfx2/classification/baf_loext.xsd @@ -0,0 +1,19 @@ + + + + + + + + + + + + + + + + + + + diff --git a/sfx2/classification/example.xml b/sfx2/classification/example.xml new file mode 100644 index 000000000..a5065e3d9 --- /dev/null +++ b/sfx2/classification/example.xml @@ -0,0 +1,89 @@ + + + + TSCP Example Policy Authority + + TSCP Example Policy + + urn:example:tscp:1 + + + + + + + UK-Cabinet + 0 + + + + + + + Document: Header + + Classification: General Business + + + + UK-Cabinet + 1 + + + + + + + Document: Header + + Classification: Confidential + + + Document: Footer + + This content is marked Confidential. Do not distribute it externally without business approval. + + + Document: Watermark + + Confidential + + + + UK-Cabinet + 2 + + + + + + + Document: Header + + Classification: Internal Only + + + Document: Footer + + This content is marked Internal Only. Do not distribute it outside of the business. + + + Document: Watermark + + Internal Only + + + + UK-Cabinet + 3 + + + + + + + + + + diff --git a/sfx2/classification/example_ca-ES.xml b/sfx2/classification/example_ca-ES.xml new file mode 100644 index 000000000..f62d6473f --- /dev/null +++ b/sfx2/classification/example_ca-ES.xml @@ -0,0 +1,71 @@ + + + Autoritat de polítiques TSCP de exemple + Política TSCP de exemple + + urn:example:tscp:1 + + + + + + UK-Cabinet + 0 + + + + + + Document: Header + Classificació: afers generals + + + + UK-Cabinet + 1 + + + + + + Document: Header + Classificació: confidencial + + + Document: Footer + Aquest contingut és de caràcter confidencial. No el distribuïu externament sense autorització. + + + Document: Watermark + Confidencial + + + + UK-Cabinet + 2 + + + + + + Document: Header + Classificació: només d’ús intern + + + Document: Footer + Aquest contingut és només d’ús intern. No el distribuïu externament. + + + Document: Watermark + Ús intern + + + + UK-Cabinet + 3 + + + + + diff --git a/sfx2/classification/example_fr-FR.xml b/sfx2/classification/example_fr-FR.xml new file mode 100644 index 000000000..4e0ab9922 --- /dev/null +++ b/sfx2/classification/example_fr-FR.xml @@ -0,0 +1,84 @@ + + + + Exemple d'autorité TSCP + + Exemple de stratégie TSCP + + urn:example:tscp:1 + + + + + + + UK-Cabinet + 0 + + + + + + + Document: Header + + Classification : professionnel + + + + UK-Cabinet + 1 + + + + + + + Document: Header + + Classification : confidentiel + + + Document: Footer + + Ce contenu est marqué confidentiel. Ne le communiquez pas à l'extérieur sans un accord de l'entreprise. + + + Document: Watermark + + Confidentiel + + + + UK-Cabinet + 2 + + + + + + + Document: Header + + Classification : exclusivement en interne + + + Document: Footer + + Ce contenu est marqué pour un usage interne exclusivement. Il ne doit pas être communiqué à l'extérieur de l'entreprise. + + + Document: Watermark + + Interne exclusivement + + + + UK-Cabinet + 3 + + + + + diff --git a/sfx2/classification/example_hu-HU.xml b/sfx2/classification/example_hu-HU.xml new file mode 100644 index 000000000..1bb6e9488 --- /dev/null +++ b/sfx2/classification/example_hu-HU.xml @@ -0,0 +1,71 @@ + + + TSCP példa irányelv-szolgáltató + TSCP példa irányelv + + urn:example:tscp:1 + + + + + + UK-Cabinet + 0 + + + + + + Document: Header + Besorolás: Általános üzleti + + + + UK-Cabinet + 1 + + + + + + Document: Header + Besorolás: bizalmas + + + Document: Footer + Ez a tartalom bizalmasként van megjelölve. Ne terjessze külső feleknek vezetői jóváhagyás nélkül. + + + Document: Watermark + Bizalmas + + + + UK-Cabinet + 2 + + + + + + Document: Header + Besorolás: csak belső + + + Document: Footer + Ez a tartalom csak belső felhasználásúként van megjelölve. Ne terjessze a szervezeten kívüli feleknek. + + + Document: Watermark + Csak belső + + + + UK-Cabinet + 3 + + + + + diff --git a/sfx2/classification/example_nl-NL.xml b/sfx2/classification/example_nl-NL.xml new file mode 100644 index 000000000..7afc17043 --- /dev/null +++ b/sfx2/classification/example_nl-NL.xml @@ -0,0 +1,71 @@ + + + Voorbeeld beleidsauthoriteit TSCP + Voorbeeld beleid TSCP + + urn:example:tscp:1 + + + + + + UK-Cabinet + 0 + + + + + + Document: Header + Classificatie: Algemeen bedrijfsvoering + + + + UK-Cabinet + 1 + + + + + + Document: Header + Classificatie: Vertrouwelijk + + + Document: Footer + De inhoud van dit document is vertrouwelijk. Verspreid het uitsluitend met de vereiste toestemming. + + + Document: Watermark + Vertrouwelijk + + + + UK-Cabinet + 2 + + + + + + Document: Header + Classificatie: Intern + + + Document: Footer + De inhoud van dit document is uitsluitend voor intern gebruik. Verspreid het niet buiten de organisatie. + + + Document: Watermark + Intern + + + + UK-Cabinet + 3 + + + + + diff --git a/sfx2/classification/example_pt-BR.xml b/sfx2/classification/example_pt-BR.xml new file mode 100644 index 000000000..e8a0bfdb2 --- /dev/null +++ b/sfx2/classification/example_pt-BR.xml @@ -0,0 +1,89 @@ + + + + Exemplo de autoridade de políticas TSCP de segurança + + Exemplo de política de segurança da informação + + urn:example:tscp:1 + + + + + + + UK-Cabinet + 0 + + + + + + + Document: Header + + Classificação: Corporativo + + + + UK-Cabinet + 1 + + + + + + + Document: Header + + Classificação: Confidencial + + + Document: Footer + + Conteúdo confidencial. Vedada a distribuição externa sem aprovação da empresa. + + + Document: Watermark + + CONFIDENCIAL + + + + UK-Cabinet + 2 + + + + + + + Document: Header + + Classificação: Restrito + + + Document: Footer + + Conteúdo restrito. Vedada a distribuição externa. + + + Document: Watermark + + RESTRITO + + + + UK-Cabinet + 3 + + + + + + + + + + diff --git a/sfx2/classification/example_sl-SI.xml b/sfx2/classification/example_sl-SI.xml new file mode 100644 index 000000000..13a4bcfdf --- /dev/null +++ b/sfx2/classification/example_sl-SI.xml @@ -0,0 +1,76 @@ + + + Avtoriteta primera politike TSCP + Primer politike TSCP + + urn:example:tscp:1 + + + + + + UK-Cabinet + 0 + + + + + + Document: Header + Stopnja zaupnosti: splošno poslovanje + + + + UK-Cabinet + 1 + + + + + + Document: Header + Stopnja zaupnosti: zaupno + + + Document: Footer + Ta vsebina ima oznako zaupno. Ne razširjajte je zunaj brez poslovne odobritve. + + + Document: Watermark + Zaupno + + + + UK-Cabinet + 2 + + + + + + Document: Header + Stopnja zaupnosti: interno + + + Document: Footer + Ta vsebina ima oznako interno. Ne razširjajte je izven podjetja. + + + Document: Watermark + Interno + + + + UK-Cabinet + 3 + + + + + + + + + + diff --git a/sfx2/classification/example_zh-CN.xml b/sfx2/classification/example_zh-CN.xml new file mode 100644 index 000000000..43acce556 --- /dev/null +++ b/sfx2/classification/example_zh-CN.xml @@ -0,0 +1,89 @@ + + + + TSCP 示例策略授权 + + TSCP 示例策略 + + urn:example:tscp:1 + + + + + + + UK-Cabinet + 0 + + + + + + + Document: Header + + 保密等级：一般性商务 + + + + UK-Cabinet + 1 + + + + + + + Document: Header + + 保密等级：保密 + + + Document: Footer + + 此处的内容被标记为“保密”。未经许可，请勿对外披露。 + + + Document: Watermark + + 保密 + + + + UK-Cabinet + 2 + + + + + + + Document: Header + + 保密等级：内部专用 + + + Document: Footer + + 此处的内容被标记为“内部专用”。未经许可，请勿对外披露。 + + + Document: Watermark + + 内部专用 + + + + UK-Cabinet + 3 + + + + + + + + + + diff --git a/sfx2/classification/xAL-types.xsd b/sfx2/classification/xAL-types.xsd new file mode 100644 index 000000000..052299007 --- /dev/null +++ b/sfx2/classification/xAL-types.xsd @@ -0,0 +1,510 @@ + + + + + Specification Name: OASIS CIQ TC - extensible AddressLanguage Types (xAL-types) + Description: Defines the W3C schema that provides enumeration lists to support xNL v3.0 + (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT) + Produced by: OASIS Customer Information Quality Technical Committee + URL: http://www.oasis-open.org/committees/ciq + Version: 3.0 + Status: Committee Specification + Copyright: 2006-07, OASIS, http://www.oasis-open.org + Last Modified: 18 September 2007 + Last Modified by: Ram Kumar, Chair, OASIS CIQ TC + + NOTE: This is the schema that users can customise the enumeration lists to meet their + exchange requirements. The enumeration values provided are ONLY SAMPLES and + is not complete. It is up to the application to decide what the values should be. To achieve + interoperability between applications using this specification, it is recommended that an + SLA/agreement is in place as to what the enumeration values will be used in this file + + + + + A list of types of addresses + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A list of types of address identifiers + + + + + + A list of types of address line, e.g. street details, locality details + + + + + + A list of types of usage of the address + + + + + + + + + + + + + + + A list of administrative area types + + + + + Only name of the administrative area without its type, e.g. NSW, CA, Quebec + + + + + The type of the area, e.g. state, district, province, etc. + + + + + + + + + A list of administrative area name element types + + + + + Name of the administrative area + + + + + + Reference location information in support of the administrative area. e.g. Territory of France + + + + + Other supporting information + + + + + + + A list of codes for name of administrative area + + + + + + A list of country name element types + + + + + Name of the country e.g. AUSTRALIA + + + + + Although a Country, could be classified as a territory of a country. For example, "NOUVELLE CALEDONIE" is a territory of "FRANCE". + + + + + + + A list of codes for name of country + + + + + + A list of codes for datum + + + + + + A list of codes for mode of delivery of address + + + + + + A list of directions for geo-coordinates + + + + + + + + + + + A list of name types for commonly used Number type + + + + + Applicable to mail box office names such as PO BOX, GPO BOX, MAIL BAG NO., etc. + + + + + Indicates that the element contains the lower value of a range, e.g. 25 in 25-37 + + + + + Indicates that the value is a range, e.g. 25-37 + + + + + Indicates that the element contains the top value of a range, e.g. 25 in 25-37 + + + + + Indicates that the element contains some value that is important, but not exactly the number itself. E.g. PoBox can be a prefix in PoBox 2020, street no. A-15, where A is the prefix and 15 is the number + + + + + Indicates that the element contains some value that is important, but not exactly the number itself. E.g. 'bis' in '45 bis' + + + + + Indicates that the value is number, e.g. 2020 in PoBox 2020. The actual value can be alpha-numeric. + + + + + Indicates that the value is a separator that is expected to be preserved. Examples are / - #, as in 15-A where "-" is the separator + + + + + Indicates that the value is an extension number of some identifier, e.g. 01 in Private Bag 2330-01, where the main number of the private bag is 2330, 12345-1223 in post code where 1223 is the extension + + + + + + + A list of locality name element types such as name of locality, reference data in support of locality + + + + + Name of the locality + + + + + + Any reference locality data in support of the locality. e.g. Next town north of Town A, via-town name + + + + + Other supporting information + + + + + + + A list of codes for name of locality + + + + + + A list of locality name types such as Municipality, Village, Area, etc + + + + + + + + + + + + + + + A list of meridian codes + + + + + + A list of types of postal delivery offices + + + + + + A list of postal delivery point types + + + + + + + + + + + + + A list of codes for projection + + + + + + A list of name types for premises + + + + + Names of Premises such as airport, hospital, university, military base, etc. Can also be the name of the building or house or apartment + + + + + Where in the building/landmark the premises is located, e.g. lobby, ground floor, penthouse, or where in a larger complex (e.g. airport) the address is located. + + + + + Free text description that is required to logically connect the 2 premises + + + + + Roads and streets within boundaries of larger complexes/premises such as hospitals, airports, etc. + + + + + Free text description of some other location and how this premises relates to it, e.g. 300m from water station, new the police station, etc. + + + + + additional supporting information + + + + + + + A list of premises type + + + + + + + + + + + + + + + + + + + + A list of rural delivery types such as road, air, water + + + + + + A list of sub administrative area name element types + + + + + Name of the sub administrative area + + + + + + Reference location information in support of the sub administrative area + + + + + Other supporting information + + + + + + + A list of codes for name of sub administrative area + + + + + + A list of sub administrative area name types + + + + + + + + + + + A list of sub locality name element types + + + + + + + + Other supporting information + + + + + + + A list of codes for names of sub locality + + + + + + A list of sub locality types + + + + + + + + + A list of sub premises types + + + + + + + + + + + + + A list of name element types for thoroughfare + + + + + Just the name part, such as Baker in Baker Street. + + + + + North Archer Street, where "North" is PreDirection + + + + + Archer Street North, where "North" is PostDirection + + + + + This value indicates that the element contains the street name and street number. E.g. 39 Baker Street. Use this when you do not want to break the thoroughfare into atomic types + + + + + Baker Street, where Baker is Name and Street is Type + + + + + 21 Archer Street (Full thoroughfare details) + + + + + Full details of a thoroughfare in a single line (unstructured) +e.g. 39 Baker Street North + + + + + When more than one street name is required to identify the location this type can be used to connect them with values such as CORNER OF or VIA. + + + + + Free text description of some other location and how this thoroughfare relates to it, e.g. 300m from water station, new the police station, etc. + + + + + Additional description like intersection, cross streets, etc + + + + + + + A list of types for thoroughfare (e.g. STREET, ROAD, CRT) + + + + diff --git a/sfx2/classification/xAL.xsd b/sfx2/classification/xAL.xsd new file mode 100644 index 000000000..13babc615 --- /dev/null +++ b/sfx2/classification/xAL.xsd @@ -0,0 +1,671 @@ + + + + + Specification Name: OASIS CIQ TC - extensible Address Language (xAL) + Description: Defines the W3C schema for representing addresses + (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT) + Produced by: OASIS Customer Information Quality Technical Committee + URL: http://www.oasis-open.org/committees/ciq + Version: 3.0 + Status: Public Review Draft 03 ERRATA + Copyright: 2007-08, OASIS, http://www.oasis-open.org + Last Modified: 08 April 2008 + Last Modified by: Ram Kumar, Chair, OASIS CIQ TC + NOTE: Do not modify this schema as it will break specifications compatibility + + + + + + + + Top level element for address with geocode details + + + + + Complex type that defines the structure of an address with geocode details for reuse + + + + + Container for free text address elements where address elements are not parsed + + + + + + Free format address representation. An address can have more than one line. The order of the AddressLine elements must be preserved. + + + + + + + What does the address line describe? e.g. Street details, suburb details, post code details, whole address, etc + + + + + + + + + + + + + + + + Country details + + + + + + + + + + Details of the top-level area division in the country, such as state, district, province, island, region, etc. Note that some countries do not have this + + + + + + Data associated with the Administrative Area. e.g. Full name of administrative area or part of it. eg. MI in USA, NSW in Australia, reference location to the administrative area + + + + + + + + semantics of data associated with name + + + + + Name of administrative area represented as a code. e.g. "COL" for COLORADO + + + + + Type of code used to represent name as a code + + + + + + + + + + The next level down division of the area. E.g. state / county, province / reservation. Note that not all countries have a subadministrative area + + + + + + Data associated with the SubAdministrative Area. e.g. Full name of sub administrative area or part of it. + + + + + + + + semantics of data associated with name + + + + + Name of administrative area represented as a code. e.g. "COL" for COLORADO + + + + + Type of code used to represent name as a code + + + + + + + + + + + Type of sub administrative area + + + + + + + + + + Type of administrative area. e.g. state, city, town, etc + + + + + + + + + Details of Locality which is a named densely populated area (a place) such as town, village, suburb, etc. A locality composes of many individual addresses. Many localities exist in an administrative area or a sub administrative area. A locality can also have sub localities. For example, a municipality locality can have many villages associated with it which are sub localities. Example: Tamil Nadu State, Erode District, Bhavani Taluk, Paruvachi Village is a valid address in India. Tamil Nadu is the Administrative Area, Erode is the sub admin area, Bhavani is the locality, and Paruvachi is the sub locality + + + + + + Data associated with the locality. e.g. Full name of the locality or part of it, reference location to the locality + + + + + + + + semantics of data associated with name + + + + + name of locality represented as a code + + + + + type of code used to represent name as a code + + + + + + + + + + A locality that is smaller and is contained within the boundaries of its parent locality. Note that not all localities have sub locality. For example, many areas within a locality where each area is a sub locality + + + + + + Data associated with the sub locality. e.g. Full name of the locality or part of it, reference location to the locality + + + + + + + + semantics of data associated with name + + + + + name of locality represented as a code + + + + + type of code used to represent name as a code + + + + + + + + + + + Type of sub locality + + + + + + + + + + Type of locality. e.g. suburb, area, zone, village, etc + + + + + + + + + Details of the Access route along which buildings/lot/land are located, such as street, road, channel, crescent, avenue, etc. This also includes canals/banks on which houses/boat houses are located where people live + + + + + + + + Another thoroughfare that is required to uniquely identify the location, such as an access route, intersection, corner, adjacent, boundary, etc + + + + + + + + + + + + + + + Details of the Premises (could be building(s), site, location, property, premise, place) which is a landmark place which has a main address such as large mail user (e.g. Airport, Hospital, University) or could be a building (e.g. apartment, house) or a building or complex of buildings (e.g. an apartment complex or shopping centre) or even a vacant land (e.g. LOT). Premises can have many sub-addresses such as apartments in a building having its own addresses or buildings within an airport having its own addresses including its own thoroughfares + + + + + + + + Examples of sub-premises are apartments and suites in buildings, shops in malls, etc. or sub-addresses in a land mark place such as airports, military bases, hospitals, etc. Some countries have blocks within blocks + + + + + + + + Type of code used for sub premises type attribute + + + + + + + + + + + Type of code use for Premises Type attribute + + + + + + + + + A container for a single free text or structured postcode. Note that not all countries have post codes + + + + + + The postcode is formatted according to country-specific rules. Example: SW3 0A8-1A, 600074, 2067. This element can also be used to define the semantics of what each code in the post code means + + + + + + + + + + A container for postal-specific delivery identifier for remote communities. Note that not all countries have RuralDelivery + + + + + + Free text or structured description of rural delivery route. e.g. RD 6, + + + + + + Type of rural delivery. For some addresses, delivery to rural areas happens via water, air or road + + + + + + + + + Final mail delivery point where the mail is dropped off for recipients to pick them up directly. E.g. POBox, Private Bag, pigeon hole, free mail numbers, etc. + + + + + + Free text or structured description of a postal delivery point. + + + + + + + + + + + A delivery point/installation where all mails are delivered and the post man/delivery service picks up the mails and delivers it to the recipients through a delivery mode. Examples are a rural post office where post is delivered, a post office containing post office boxes/personal mail boxes. Note that not all countries have PostOffice. Can be used to represent overseas military addresses also along with PostalDeliveryPoint element + + + + + + Name or number of the post office in free text or structured form. + + + + + + Indicates the type of postal delivery office from where the mail will be distributed to the final delivery point by a delivery mode. Example: Post Office, Mail Collection Centre, Letter Carrier Depot, Station, etc. + + + + + + + + + GeoRSS GML from Open Geospatial Consortium (OGC – www.opengeospatial.net) is a formal GML Application Profile, and supports a greater range of features than Simple, notably coordinate reference systems other than WGS84 latitude/longitude. It is designed for use with Atom 1.0, RSS 2.0 and RSS 1.0, although it can be used just as easily in non-RSS XML encodings. + + + + + + Could be GeoRSS Simple or GeoRSS GML versions. Refer to http://georss.org/ and http://georss.org/gml for further documentation + + + + + + + + + Simple Geo-coordinates of the address/location + + + + + + Latitude details + + + + + Measure of the latitude in degrees + + + + + Measure of the latitude in minutes + + + + + Measure of the latitude in seconds + + + + + The direction of latitude measurement offset from the equator + + + + + + + + Longitude details + + + + + Measure of the longitude in degrees + + + + + Measure of the longitude in minutes + + + + + Measure of the longitude in seconds + + + + + The direction of longitude measurement offset from the equator + + + + + + + + + The collection of the coordinate numeric values for latitude amd longitude depends on the agreed position of the meridian. Declaration of the meridian is necessary as it cannot be assumed in the data + + + + + Type of code used. e.g. EPSG Code + + + + + The collection of the coordinate numeric values depends on the agreed datum within which the measurement was taken. Declaration of the datum is necessary as it cannot be assumed in the data + + + + + Type of code used. e.g. EPSG Code, WGS-84 + + + + + Coordinates have limited utility and application depending on the projection required for visualisation in a map. Declaration of projection is necessary as it cannot be assumed in data + + + + + Type of code used. e.g. EPSG Code + + + + + + + + + + Defines the type of address. An address type can be" Primary Address, Secondary Address, Rural Address, Military Address, etc. + + + + + A unique address identifier such as postal delivery identifier assigned to the address by local postal authority, e.g. DPID in Australia. + + + + + Type of address ID used. e.g. DPID, etc + + + + + A globally unique identifier assigned to the address + + + + + The purpose the address is used for. E.g. Postal, residential, business, exchange, update, create, delete, etc + + + + + Mode of delivery of address. For example: rural route, normal delivery, post office box, etc. + + + + + Status of the entity. e.g. Old, Current, Inactive, Active, etc + + + + + + A primary key to reference Address. + + + + + A foreign key to reference attribute Key of Address. + + + + + + + + + + + + Complex type that defines the name of the country and is reused in other CIQ specs + + + + + Data associated with the name of the country in whatever form available, e.g. full, abbreviation, common use, code of the country, etc. + + + + + + + + Semantics of data associated with name. + + + + + Name of the country represented as a code + + + + + Type of code used to represent name of country, e.g. iso-3166 + + + + + + + + + + + + + Complex type for internal reuse + + + + + + Indicates which part of number or identifier this element contains. Some "numbers" are as simple as 42 and some "numbers" are more like complex alphanumeric identifiers as Postcodes in UK or Canada, e.g. M2H 2S5. It may be necessary to separate the "number" into sub-elements and indicate what type of information each of them contains. + + + + + + + + + + Complex type for internal reuse + + + + + Data associated with the name of the Premises. e.g. Full name of premises or part of the name. E.g. Westfield shopping center, reference data to support the premises location, street in the premises + + + + + + + + Describes the type / part of name this element contains. + + + + + + + + + + Data associated with the number of the premises. E.g.House 15, number range, number suffix + + + + + + + + Complex type for internal reuse + + + + + Data associated with the thoroughfare details. e.g. Full thoroughfare name or part of it, type of thoroughfare, old name, new name, reference data in support of the thoroughfare + + + + + + + + Describes the type / part of name this element contains. + + + + + + + + + + Data associated with the number of the thoroughfare. E.g. 39 in 39 Baker Street, street range, street suffix + + + + + + Type of thoroughfare. eg. primary road, secondary road, road branch (e.g. Lane 14), road sub branch (e.g. Alley 21), adjourning street, cross street, closest street, etc + + + + + Type of code use for thoroughfare + + + + + + diff --git a/sfx2/classification/xNL-types.xsd b/sfx2/classification/xNL-types.xsd new file mode 100644 index 000000000..dc8769ae3 --- /dev/null +++ b/sfx2/classification/xNL-types.xsd @@ -0,0 +1,221 @@ + + + + + Specification Name: OASIS CIQ TC - extensible Name Language Types (xNL-types) + Description: Defines the W3C schema that provides enumeration lists to support xNL v3.0 + (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT) + Produced by: OASIS Customer Information Quality Technical Committee + URL: http://www.oasis-open.org/committees/ciq + Version: 3.0 + Status: Committee Specification + Copyright: 2006-07, OASIS, http://www.oasis-open.org + Last Modified: 18 September 2007 + Last Modified by: Ram Kumar, Chair, OASIS CIQ TC + + NOTE: This is the schema that users can customise the enumeration lists to meet their + exchange requirements. The enumeration values provided are ONLY SAMPLES and + is not complete. It is up to the application to decide what the values should be. To achieve + interoperability between applications using this specification, it is recommended that an + SLA/agreement is in place as to what the enumeration values will be used in this file + + + + + A list of possible values for joint name connector + + + + + + A list of possible values for types of name lines + + + + + + A list of all types of Party Name IDs + + + + + + A list of usage types of party name + + + + + + A list of person name element types, e.g. First Name, Last Name, Title, etc. + + + + + His Excellency, Honorable, etc. + + + + + A title signifies some sort of status, such as Mr, Miss, Ms (marriage status), or education such as Professor, PhD, Dr, etc. + + + + + The most important name element by which this particular individual is identified in the group. E.g. John, Sam, Brian for Anglo-Saxon cultures. + + + + + Name elements related to additional identification of the individual, such as names are parents or places. + + + + + Name element that identifies the group the individual belongs to and is identified by, such as Last Name, Surname, Family Name, etc. + + + + + Any other additional names that are not directly used to identify or call the individual, such as names of ancestors, saints, etc. + + + + + A simple nick name that is commonly used as part of the name. E.g. a fancy kick-boxer can be commonly known as Bill "Storm" Bababoons, where "Storm" is obviously an alias. + + + + + Junior, Senior, The Second, IV, etc. + + + + + + + + A list of usage types of person name + + + + + + A list of all types of person name IDs + + + + + + A list of all types of organisation name IDs + + + + + + A list of organisation name element types, e.g. Name, property type, liability type, etc. + + + + + "Sakthisoft" in "Sakthisoft Pty. Ltd". "Pty.Ltd" is the legal entity for the organisation name "Sakthisoft" + + + + + "Pty. Ltd" in Sakthisoft Pty.Ltd, where "Sakthisoft" is the name of the organisation. + +""Inc" in ABC Inc, where "ABC" is organisation name + + + + + Full Name of the organisation. e.g. Sakthisoft Pty. Ltd + + + + + + + A list of usage types for organisation name + + + + + + A list of common types for person names + + + + + + + + Name of an individual before marriage. + + + + + Former name of the person + + + + + Name that is commonly used by others, e.g. a simplified form of the official name. + + + + + A name given to an individual at birth, but later changed (common in some cultures) + + + + + Indicates that the party prefers to be called by this name + + + + + An official name of the person, e.g. as in the passport. incorporation certificate, etc. + + + + + + + + + + A list of common types for organisation names + + + + + + Former name of the organisation + + + + + + + + + unknown + + + + + + + A list of common types for subdivisions + + + + + + + + + + + diff --git a/sfx2/classification/xNL.xsd b/sfx2/classification/xNL.xsd new file mode 100644 index 000000000..d82c6ab7b --- /dev/null +++ b/sfx2/classification/xNL.xsd @@ -0,0 +1,283 @@ + + + + + Specification Name: OASIS CIQ TC - extensible Name Language (xNL) + Description: Defines the W3C schema for representing party names (Person or Organisation) + (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT) + Produced by: OASIS Customer Information Quality Technical Committee + URL: http://www.oasis-open.org/committees/ciq + Version: 3.0 + Status: Committee Specification + Copyright: 2006-07, OASIS, http://www.oasis-open.org + Last Modified: 18 September 2007 + Last Modified by: Ram Kumar, Chair, OASIS CIQ TC + + NOTE: Do not modify this schema as it will break specifications compatibility + + + + + + + + Reference to another Person Name or Organisation Name with primary and foreign key reinforcement. + + + + A primary key to reference Party Name. + + + + + A foreign key to reference attribute Key of Party Name. + + + + + + Reusable complex type for a party. A party is a person or an organisation + + + + + + Container for person name details. Same person with many types (e.g. alias, pet name, nick name) of names can be used by this container. + + + + + + + + + + A container for organisation name details. Same organisation with many types of names can be used by this container + + + + + + + + + + + A unique identifier of a party + + + + + Type of Party Name ID + + + + + Globally unique identifier + + + + + Type of use of this data. e.g. data exchange, contact, update, create + + + + + Status of the entity. e.g. Old, Current, Inactive, Active, etc + + + + + The connector used to join more than one person name. Example: Mr Hunt AND Mrs Clark, where AND is the JointNameConnector. The flow is from the preceding to the following. If there is more than 2 names then all names are connected using this connector in the natural order. + + + + + + + + + + + + + + Reusable complex type + + + + + Name or part of a name. + + + + + + + Clarifies the meaning of the element.Could be first name, middle name, etc. that is defined in the List list. Omit this attribute if the type of the name element is not known. + + + + + + + + + + + + Enumerated list of type of name. example: Alias, Nick Name, former name, known as, etc + + + + + A unique identifier of a person + + + + + Type of identifier + + + + + Globally unique identifier + + + + + Usage of a person name. How is it used and for what purpose. Allows user which name in a set of names to select for a given purpose. +e.g. used for legal purposes + + + + + Status of the entity. e.g. Old, Current, Inactive, Active, etc + + + + + + + + + + + + + + Reusable complex type + + + + + Name of the organisation. E.g. ACME Inc. + + + + + + + Clarifies the meaning of the element. Example: name, type . Omit this attribute if the type of the name element is not known. + + + + + + + + + + + Name of a subdivision of an organisation (e.g. department) + + + + + + + Type of sub division. e.g. department, warehouse, branch + + + + + + + + + + + + Enumerated list of common types of aliases or name types. + + + + + A unique identifier of an organisation + + + + + Type of identifier + + + + + Globally unique identifier + + + + + Usage of organisation name. How is it used and for what purpose. Allows user which name in a set of names to select for a given purpose. +e.g. used for legal purposes + + + + + Status of the entity. e.g. Old, Current, Inactive, Active, etc + + + + + + + + + + + + + + Define name as a free format text. Use this when the type of the entity (person or organisation) is unknown, or is not broken down into individual elements (e.g. unstructured, unparsed) or is beyond the provided types. The name represented may be formatted in the right order or may not be as it is not parsed/broken into atomic fields + + + + + + + Type define what this free format name line could mean. For example, the Type could be "Unknown" + + + + + + + + + + + + Container for defining a name of a Person, an Organisation or combination of the above as a joint name. + + + + + Person Name + + + + + Organisation Name + + + diff --git a/sfx2/classification/xlink-2003-12-31.xsd b/sfx2/classification/xlink-2003-12-31.xsd new file mode 100644 index 000000000..bfe7a792e --- /dev/null +++ b/sfx2/classification/xlink-2003-12-31.xsd @@ -0,0 +1,89 @@ + + + + + + XLink attribute specification + + + + + + + Enumeration of values for the type attribute + + + + + + + + + + + + + + + + + A URI with a minimum length of 1 character. + + + + + + + + + + + + A URI with a minimum length of 1 character. + + + + + + + + + + + + + Enumeration of values for the show attribute + + + + + + + + + + + + + + + + Enumeration of values for the actuate attribute + + + + + + + + + + + + + + + -- cgit v1.2.3