Skip to content

Relationship between "string forms" and "object forms" of natural language values #756

@evanp

Description

@evanp

Section 4.7 says:

"name" identifies the JSON string form for the name property while "nameMap" represents the object form.

Later:

Accordingly, in the JSON serialization, the terms " name", "summary", and "content" represent the JSON string forms; and the terms " nameMap", "summaryMap", and " contentMap" for represent the object forms.

This describes the serialization of these properties: one is a string, the other is an object. It doesn't describe what they're for, though. When should a publisher use name, and when should they use nameMap? Can they use both? Why or why not?

I think we use these as default plus variant. name is the default name in the language of the document; nameMap is all the alternate names in other language (maybe including the default name).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions