💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.
• Other: I want to discuss something else.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.
EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As a product maintainer,
I want to use GitHub as much as possible
In order to avoid relying on specs on hosted servers.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. OpenAPI spec URLs point to GitHub raw YAML resources, e.g., https://raw.githubusercontent.com/commonality/archetypes/master/schemas/v1/quantities/quantities.yaml
• 2. All links in the repo point to raw.githubusercontent.com (including Swagger Validation badges)
• 3. All Archetype API and SDK Documentation resources reside in the /docs directory
• 4. All documents in the /docs directory are published to commonality.github.io
• 5. commonality.github.io resources leverage RunKit as much as possible.

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.
EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As an API consumer,
I need to define and understand the roles and relationships between Parties
In order to communicate with, market and sell to or by good and services from.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. A Party can have zero or more PartyRoles.
• 2. PartyRoles have PartyRoleIdentifiers that represent their uniqueness.
• 3. PartyRelationships specify the semantics in which each Party plays a PartyRole.
• 4. PartyRoles can be associated with PartyRoleTypes, which store common information about a set of PartyRole instances.
• 5. PartyRelationshipTypes can be associated with PartyRelationships, which store common information about a set of PartyRelationship instances.
• 6. PartyRelationshipConstraints specify the names of the PartyRoles that may adopt client and supplier (or buyer and seller) sides of a PartyRelationship of a specific PartyRelationshipType.
• 7. Responsibilities describe activities that a PartyRoleType is expected to perform.
• 8. AssignedResponsibilities represent Responsibilities assigned to specific PartyRoles; AssignedResponsibilities may (or may not) have from and to dates.
• 9. PartySummary objects provide "snapshots" of summary contact information about a Party, in relation to a particular context.

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.

EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As an API consumer,
I need to model Money and Currency by Locale
In order to accomidate future Orders and capture business transactions.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. Currency is represented with an OpenAPI 2.0 spec.
• 2. Money is represented with an OpenAPI 2.0 spec.
• 3. PaymentMethod is represented with an OpenAPI 2.0 spec.
• 4. PaymentCard is represented with an OpenAPI 2.0 spec.
• 5. Payment is represented with an OpenAPI 2.0 spec.

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• CIr: I want to discuss something else.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.

EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As a {role},
I must/need/want/should {do something}
In order to {achieve value}.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. Job Applicants receive a confirmation email after they submit their resumes.
• 2. An Applicant's resume information isn't lost when errors occur.
• 3. {criterion-three}
• 4. {criterion-four}

appveyor.yml

install:
  - ps: Install-Product node '7'
  - npm install -g npm --silent --quiet
  - npm install --silent --quiet

platform:
  - x86
  - x64

build: off

test_script:
  - node --version
  - npm --version
  - npm test

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.

As an API consumer,
I want to consistently describe essential information about people, organizations, and their preferences,
In order to conduct business unambiguously and clearly.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

The following valid, well-formed OpenAPI 2.0 documents and JSON schemas specify:

• 1. TheParty represents properties that belong to an identifiable, addressable entity that may have a legal status and that normally has autonomous control over (at least some of) its actions.
• 1.1. The PartyIdentifier uniquely identifies a Party
• 1.2. The RegisteredIdentifier represents identifiers assigned by recognized or statutory bodies
• 1.3. EffectiveDates represent valid "from" and "to" date ranges
• 2. Address represents contact information by
• 2.1. ⚠️ GeographicAddress
• 2.2. ⚠️ TelecomAddress
• 2.3. ⚠️ EmailAddress
• 2.4. ⚠️ UrlAddress
• 2.5. ⚠️ AddressProperties
• 3. Person represents information about human beings
• 3.1. IsoSex represents sex
• 3.2. Gender expresses femininity and masculinity as a continuum of attributes
• 3.3. Ethnicity represents ethnic and cultural backgrounds
• 3.4. ⛔️ BodyMetrics provide information about the human body
• 3.5. PersonName represents peoples' names
• 4. Organization represents administrative and functional structures
• 4.1. OrganizationName provides the name of an Organization
• 4.2 ⚠️ OrganizationUnit represents an Organization that is part of another Organization
• 4.3 ⚠️ Company represents companies
• 4.4 CompanyGroup represents a related group of Companies
• 4.5. CompanyName represents a company name
• 4.6. ⛔️ Partnerships and SoleProprietors represent their legal counterparts
• 5. Preference expresses a Party's choice of or liking for something
• 5.1 PreferenceType provides a range of PreferenceOptions for Parties
• 6. Expose the APIs with Swagger-UI.

4. Implementation notes

4.1. ℹ️ PartyIdentifier

PartyIdentifier has been defined, but it's neither available as an independent service, nor is it explicitly used in an HTTP response body. Instead, the property partyIdentifier is used.

4.2. ⚠️ Addresses

The following Address sub-types have been defined, but they're neither available as independent services, nor are they used in an HTTP response body. I did, however, add an addressType property with an enum for each. Should we also add an address-type input query parameter? Dunno.

⚠️ 2.1. GeographicAddress
⚠️ 2.2. TelecomAddress
⚠️ 2.3. EmailAddress
⚠️ 2.4. UrlAddress

4.3. ⚠️ AddressProperties

AddressProperties has been defined, but it's neither available as an independent service, nor is it explicitly used in an HTTP response body.

4.4. ⛔ BodyMetrics

Omitting this, for now, since I don't have access to ISO 7250-3:2015, "Basic human body measurements for technological design." There's no immediate need for it, anyway.

4.5. ⚠️ OrganizationUnit

OrganizationUnit has been defined, but it's neither available as an independent service, nor is it explicitly used in an HTTP response body. I'm unsure how to express the "Organization within another Organization" relationship. The authors depict this relationship with inheritance, but that smells weird to me.

4.6. ⚠️ CompanyGroup

CompanyGroup has been defined, but it's neither available as an independent service, nor is it explicitly used in an HTTP response body. I suppose it could simply provide an array of its related Companies, but since there's no immediate need for it, I'm not associating an operationId for it.

4.7. ⛔ Partnerships and SoleProprietors

Neither has been defined, nor been made available.

User story

As an API consumer,
I want to consistently describe the amount of something measured according to some standard of measurement,
In order to conduct business unambiguously and clearly.

Acceptance criteria

• 1. Metric represents a standard of measurement for quantities.
• 2. Unit represents a type of Metrics that is part of a SystemOfUnits
• 3. SystemOfUnits represents a set of related Units defined by a standard such as the International System of Units (SI)
• 4. SiBaseUnit provides common properties of SI base units
• 4.1. Ampere represents an SI unit of electric current
• 4.2. Candela represents an SI unit of luminous intensity
• 4.3. Kelvin represents an SI unit of temperature
• 4.4. Kilogram represents an SI unit of mass
• 4.5 Meter represents an SI unit of length
• 4.6. Mole represents an SI unit of amount of substance
• 4.7. Second represents an SI unit of time
• 5. DerivedUnit represents a combination of one or more base Units according to a specific equation
• 5.1. DerivedUnitTerm represents a term, i.e., a single Unit and its power within a DerivedUnit
• 6. LaborHour represents the amount of work corresponding to one person working for one hour.
• 7. Quantity specifies an amount that is measured in some Metric and can be used for
• 7.1. Arithmetic operations
• 7.2. Comparison operations
• 7.3. Rounding operations with a
• 7.3.1. RoundingPolicy that defines the mathematical semantics of the rounding operation, and a
• 7.3.2. RoundingStrategy that represents the type of rounding to be applied
• 8. Conversion with
• 8.1. StandardConversion defines a conversionFactor that can be used to convert a source Quantity to a Quantity in a targetUnit
• 8.2. UnitConverter represents a conversion process

Compliance with standards

Note

All archetypes have been defined, but not all of them have direct RESTful services that can operate on values.

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.
EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As an API consumer and producer,
I want to explicitly define rules and conditional logic independent of source code and database triggers,
In order to immediate define, execute, review, reuse, and quickly establish personalization and business constraints.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. TBD
• 2. TBD
• 3. {criterion-three}
• 4. {criterion-four}