Mike Amundsen mamund

## data.xml
<root>
  <thing name="car">
    <part name="hood" />
    <part name="door" />
    <part name="fender" />
    <part name="trunk" />
  </thing>
</root>

## a-uber-nesting.xml
<uber version="1.0">
  <data name="description">
    <data name="prefix">My name is</data>
    <data name="name">Stephen</data>
    <data name="postfix">and it's Tuesday.</data>
  </data>
</uber>

## a-uber-textnode.xml
<uber version="1.0">
    <data name="description">
        My name is
        <data name="name">Stephen</data>
        and it's Tuesday.
    </data>
</uber>

## a-uber-leading-text.xml
<uber version="1.0">
    <data name="description">
        My name is
        <data name="name">Stephen</data>
    </data>
</uber>

## a-uber-trailing-text.xml
<uber version="1.0">
    <data name="description">
        <data name="name">Stephen</data>
        is my name.
    </data>
</uber>

## 01-example.html
<html>
  <head>
    <title>Example #1</title>
  </head>
  <body>
    <h1>Example #1</h1>

    <form action="..." method="get">
      <input name="messageText" />
      <input type="createDate" />

## microblogging.xml
<alps>
  <doc>
    The example profile here contains details on customizing any representation media type for a specific
    application domain: Micro-blogging. It contains descriptions of valid data and transition values that
    can appear within resource representations. This document is presented as a complete blueprint for
    implementing a compliant client or server that supports the basic features of the target application
    domain (Micro-blogging).
  </doc>
  <link rel="help" href="http://amundsen.com/hypermedia/profiles/" />


## recipe-alps-00.xml
<alps version="1.0">

  <descriptor id="ingredient" type="semantic">
    <doc format="html">An ingredient of a cooking receipt</doc>
    <descriptor id="name" type="semantic" rt="http://alps.io/schema.org/Text">
      <doc format="html">The name of the ingredient, e.g. "flour"</doc>
    </descriptor>
    <descriptor id="amount" type="semantic">
      <doc format="html">Describes how much of the ingredient is to be used</doc>
      <descriptor id="unit" type="semantic" rt="http://alps.io/schema.org/Text">

## constrained-alps.xml
<alps>
  <link rel="profile" href="https://gist.github.com/mamund/f5ad7ebf2aa0833ceb89" />
  <doc>
    An example of a highly-constrained ALPS profile. One that leaves very
    few choices to implementors. I don't recommend this kind of profile
    design since the aesthetics of ALPS is to create profiles that focus
    on the problem and allow creative people to design their own solutions
    with that problem space.  - @mamund
  </doc>


## 01-users.js
{ "collection" :
  {
    "version" : "1.0",
    "href" : "http://api.example.com/users",

    "links" : [
    ],

    "items" : [
      {
	<root>
	<thing name="car">
	<part name="hood" />
	<part name="door" />
	<part name="fender" />
	<part name="trunk" />
	</thing>
	</root>
	<uber version="1.0">
	<data name="description">
	<data name="prefix">My name is</data>
	<data name="name">Stephen</data>
	<data name="postfix">and it's Tuesday.</data>
	</data>
	</uber>
	<uber version="1.0">
	<data name="description">
	My name is
	<data name="name">Stephen</data>
	and it's Tuesday.
	</data>
	</uber>
	<html>
	<head>
	<title>Example #1</title>
	</head>
	<body>
	<h1>Example #1</h1>

	<form action="..." method="get">
	<input name="messageText" />
	<input type="createDate" />
	<alps>
	<doc>
	The example profile here contains details on customizing any representation media type for a specific
	application domain: Micro-blogging. It contains descriptions of valid data and transition values that
	can appear within resource representations. This document is presented as a complete blueprint for
	implementing a compliant client or server that supports the basic features of the target application
	domain (Micro-blogging).
	</doc>
	<link rel="help" href="http://amundsen.com/hypermedia/profiles/" />
	<alps version="1.0">

	<descriptor id="ingredient" type="semantic">
	<doc format="html">An ingredient of a cooking receipt</doc>
	<descriptor id="name" type="semantic" rt="http://alps.io/schema.org/Text">
	<doc format="html">The name of the ingredient, e.g. "flour"</doc>
	</descriptor>
	<descriptor id="amount" type="semantic">
	<doc format="html">Describes how much of the ingredient is to be used</doc>
	<descriptor id="unit" type="semantic" rt="http://alps.io/schema.org/Text">
	<alps>
	<link rel="profile" href="https://gist.github.com/mamund/f5ad7ebf2aa0833ceb89" />
	<doc>
	An example of a highly-constrained ALPS profile. One that leaves very
	few choices to implementors. I don't recommend this kind of profile
	design since the aesthetics of ALPS is to create profiles that focus
	on the problem and allow creative people to design their own solutions
	with that problem space. - @mamund
	</doc>
	{ "collection" :
	{
	"version" : "1.0",
	"href" : "http://api.example.com/users",

	"links" : [
	],

	"items" : [
	{