From: Clark C . E. <cc...@cl...> - 2002-07-25 14:46:21
|
On Wed, Jul 24, 2002 at 07:14:03AM +0000, sh...@zi... wrote: | PRIVATE TYPES | | For folks that don't have interoperability concerns, we need | a way to mark types. Basically, private types allow you to | attach metadata to parts of your YAML. Typically, the private | type would correspond to a "class" in the programming language, | but other uses may be derived. Implementations must respect | the "!!" marker for private types and provide YAML callers hooks | to manipulate/specify types as needed. Implementations for | languages with good introspection capabilities (e.g. Perl, Ruby, | Python, etc.) will provide good "default" methods for mapping | between YAML types and programming language classes. Agreed. And I'm proposing that to keep all type-family's URIs, private type !whatever is mapped to ($scheme)yaml.org/private/whatever where $(scheme) is the scheme we choose; I'm proposing "urn:dns:" instead of "http://" since "urn:dns:" doesn't imply that a http retrievable resouce must exist. In this way a type family *is* a URI, complete with semantics. Best, Clark -- Clark C. Evans Axista, Inc. http://www.axista.com 800.926.5525 XCOLLA Collaborative Project Management Software |