3003 · Identity and context

Identity preface · Standards, carriers and exact keys

Distinguish a standard identifier, its carrier, a lookup location and namespace authority.

Typed identity roles Asset record rather than page address

Open a workspace beside this lesson. Protected links keep their existing access gates; no new permission is granted by this course.

Why this matters

Physical systems already contain identifiers; integration must preserve them rather than replace them with labels.

A carrier transports a value. A URL locates a resource. Neither alone proves an identity allocation or an authorized relationship.

Step by step

01
Classify what each representation does
Screen or control: P1 key-type controls
Why: Different representations answer different questions.
How: Inspect GIAI, GDTI and SGLN examples. Describe the physical unit, document or location role; separately identify the prefix and non-issued state.
What you should see: Three typed-role explanations.
Verify: PGLN is banned as a ThingDaddy ID type. The prefix is never treated as a company-authority grant.
02
Separate address from access
Screen or control: Exact sample P5 inspector
Why: Resolvable context and permitted action are separate gates.
How: Compare an exact EPC URN with the page URL used to inspect it. Record which identifies a proposed participant and which locates a view.
What you should see: A key-versus-location distinction.
Verify: The page URL is never substituted for the retained EPC identity.

What is happening under the surface

Read the preface as an argument for persistent, typed references, not proof of exclusive superiority over every other system.

Use the current key-role palette and explicit assignment state. The book’s older key inventory and examples are not the current construction specification.

Common mistakes

Copying alphanumeric or obsolete book examples as valid current ThingDaddy proposals.
Assuming an identifier’s digits establish owner, legal party or permission.

The records an agent needs

Current demo state and current governance supersede older illustrative construction examples. This lesson does not mint a key, infer allocation or introduce a new public routing mechanism.

Exact retained identities

urn:epc:id:giai:0614141.4

Anonymous package occurrence pointers

#/P1/manufacturerPrefix#/P1/prefixEvidence#/P1/demo_giai#/P1/demo_gdti#/P1/demo_sgln

Fields or record paths to inspect

key_typestateallocation_authority_evidenceidentity_equivalence_asserted

Pointers locate records; hashes pin bytes; lesson numbers locate teaching material. None substitutes for an applicable assigned GS1 identity.

Apply what you learned

Create a representation table for one anonymous asset.

Prepare these outputs

Identifier role
Carrier role
View URL role
Allocation/authority unknowns

Review your work against these checks

Key, carrier and URL are distinct
Original supplied identifiers are preserved
No allocation is inferred from a label or digit pattern

Check your reasoning

A scanner reads an asset identifier. What has been established?

This answer stays in page memory, is cleared when you leave, and is not sent or recorded as certification, validation or authority.

Source and current boundaries

Identity preface · design principle. Adapted, anonymous teaching prose; not a quotation or independent verification of the author’s assertions.

Source part word/document.xml; original document SHA-256 71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f. Exact paragraph/table locators are retained; page numbering is not verified.

The preface includes older syntax examples, scale claims and routing assertions. They are preserved in the original source, not promoted into current rules or public mechanisms.

Current governance adds exact-source retention, unknown-state, disclosure, validation and scoped-authority safeguards. Those safeguards are not represented as quotations from the historical book.

Numeric lesson numbers are educational content locators, not GS1 identities. Linked public screens use an anonymous non-issued fixture; reading, retrieval and practice do not authorize physical/cloud execution or constitute model-weight training.