Skip to content

Specify an extensible format within the YAML for agents to add further information #8

Description

@jonathanKingston

As explained by @renormalist in #1 (comment) the ability to extend the YAML format is important for producers and consumers.

I suggest we work here on finding the most suitable extendible format within the YAML.

Activity

  1. kinow commented on Feb 8, 2015

    @kinow
    Member

    Hey @jonathanKingston, maybe this issue can be merged with #9?

  2. jonathanKingston commented on Feb 8, 2015

    @jonathanKingston
    MemberAuthor

    @kinow this is about extending the YAML for individual implementations, similar to X-headers, data attributes or web components. #9 is more about standardising the core set of functionality. I would like to keep them separate still.

    I know there has been some convention to prefix rules with characters and so on, however I think something more robust would be better.

    However I would like to standardise the words in the spec around how to extend even if its just picking an old suggestion.

  3. kinow commented on Feb 8, 2015

    @kinow
    Member

    Oh, got it @jonathanKingston, thought it was more like #9, defining entries and schema. Thanks for clarifying :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions