# data[].attributes.body
Best practices gets to the user level and addresses how best results are achieved when engaged in the entity.

# data[].attributes.body
Best practices gets to the user level and addresses how best results are achieved when engaged in the entity.

# data[].attributes.body
Policies are about principles, values, and main ideas used to make decisions about accepting and developing elements in an entity.

# data[].attributes.body
Policies are about principles, values, and main ideas used to make decisions about accepting and developing elements in an entity.

# data[].attributes.body
Governance is about directing, controlling, and accounting for an entity.

# data[].attributes.body
Governance is about directing, controlling, and accounting for an entity.

# data[].attributes.body
Follow best practices for writing competencies and competency life-cycle management. Identify examples, e.g., IEEE’s new defining competencies paper.

# data[].attributes.body
Utilize competency management tools that follow data standards and use public URIs for interoperability and for search and discovery. Identify tools and standards followed.

# data[].attributes.body
Publish human and machine readable competencies to open registries.Identify open registries that offer free or reasonable services.

# data[].attributes.body
Utilize competency registries to explore and discover competencies. Identify Competency Explorer and participating registries.

# data[].attributes.body
Has click through agreement to consent to the terms and conditions established by T3 for access and use of the Competency Explorer

# data[].attributes.body
User creates an account to track system usage and build a larger community of those who do engage with the system

# data[].attributes.body
Providers provide conditions and permissions that are applicable to their competency frameworks

# data[].attributes.body
Respect the aims, business models, IPR of the people who provide the data you use.

# data[].attributes.body
Type in your your framework ideas

# data[].attributes.headline
Align your competencies to similar competencies issued by others, or integrate other publisher's competencies into your framework

# data[].attributes.subject
Align your competencies to similar competencies issued by others, or integrate other publisher's competencies into your framework

# data[].attributes.headline
Use LRMI associations to link Learning Resources and Assessments to appropriate competency statements. 

# data[].attributes.subject
Use LRMI associations to link Learning Resources and Assessments to appropriate competency statements. 

# data[].attributes.headline
Never create a duplicate URI for a published statement, only point to the canonical version. 

# data[].attributes.subject
Never create a duplicate URI for a published statement, only point to the canonical version. 

# data[].attributes.body
Define a common structure for authoring a competency statement that aides in transparency, interoperability, and clarity.

# data[].attributes.body
Determine the differences between your competences and competences issued by others and analyze if these differences need or can be reduced.

# data[].attributes.body
Consumers can save competencies so they may re-use and share.

# data[].attributes.body
Use the most open license that is compatible with your business model; use the most widely compatible / most used license that fits your needs.

# data[].attributes.body
Consumers access to the competencies/framework align to the defined provider ability to save, share, and modify.

# data[].attributes.body
Help potential consumers and potential providers understand the value of this tool, and how it can provide positive value to them.

# data[].attributes.body
Consumers agree to basic governance guidelines. What should these governance elements be? To use fidelity and ethics in the access of frameworks to align to Provider defined levels of access and use.

# data[].attributes.body
The ability for two organizations to establish relationships between their existing competencies or competency framework (e.g. equivalent to). Associations could also be unilateral, in that one organization accepts another organization's competency, but not vice versa. A taxonomy would likely be needed that supports this use case.

# data[].attributes.body
A subset of schema elements that at least one property from any organization's schema must align to in order to be considered for mapping.

# data[].attributes.body
Higher education (supply) and industry (demand) develop competency frameworks together to ensure students (consumers) achieve readiness in marketplace sectors.

# data[].attributes.body
1) how do I propose or change a functional capability?

2) how is the proposal evaluated?

3) how is the changed version controlled?

4) how is the change rolled out?

# data[].attributes.headline
Provider licenses applicable to end users (as opposed to registry-to-registry use agreements)

# data[].attributes.subject
Provider licenses applicable to end users (as opposed to registry-to-registry use agreements)

# data[].attributes.body
This may have been the intension of cell 7 in the meeting presentation https://docs.google.com/presentation/d/1uP4u_LQM7WOLbHamauclIdxdGk5h0AdA/edit#slide=id.g15e56e6a30a_0_30 to differentiate between the providers license controlling rights/use by end users discovering a framework through the Explorer and privileges and prohibitions controlling interactions between registry nodes. While pushing toward open end user licensing going forward is admirable, the fact remains that most large providers already have in place bespoke licenses (and terms of use pages) controlling what an end user can and cannot do. For me, the policy here is that the Explorer must always telegraphs that existing, bespoke license to the end user in all public Explorer interfaces to a framework and/or competency.

# data[].attributes.headline
Providers as key stakeholder in the Exchange governance

# data[].attributes.subject
Providers as key stakeholder in the Exchange governance

# data[].attributes.body
This may sound counter intuitive or even strange, but the governance complexity over time for a functioning Explorer is likely to be around transparent and effective conflict investigation and resolution in cases of internode misbehavior--i.e., issues stemming from one node's handling of another node's data in violation of an Explorer common agreement. Policy should dictate the who, what and how of such conflict resolution.

This should not be confused with registry node (provider) vs end user conflicts since such conflicts are controlled by the provider's standard public rights/use and would be handled by the provider as though the Explorer weren't in the picture.

# data[].attributes.body
Deliver a sandbox environment for where developers can access technical documentation, set up test accounts, and experiment with the tool(s) for prototyping and evaluation.

# data[].attributes.body
Ensure the tool's user interface is intuitive to use by engaging providers (and their customers) in UI/UX testing.