Re: [Yaml-core] YAC 20

[Clark C . E. <cc...@cl...>]

| As for XML and Clark's point that it may appear in XML namespace URIs -
| that's not a problem. An XML namespace, when used in YAML, *always* ends
| with a '$tag-name'. Hence there's no ambiguity; to get the original XML
| namespace, just strip away anything after the last '$' - and this would be
| the XML tag name. The namespace URI itself can contain anything at all, $
| characters included.

Ahh... right. ;)

| # YAC 20
| abstract: Avoiding the yaml: scheme

Nice.

|  Shorthands will be handled as follows:
| 
|  A method '!scheme:...' is preserved as is.
|  Marker: There's a ':' and it appears before any '/' character.
| 
|  A method '!host.domain.tld/...' is prefixed with 'http://'.
|  Marker: There's a '/' before any ':' character; there is
|  a '.' before the '/'.
| 
|  A method '!one-word/...' is a shorthand for 'http://one-word.yaml.org/...'
|  Marker: There's a '/' before any ':'. There is no '.' before the '/'.
| 
|  A '!type' is prefixed with 'http://yaml.org/'. Marker: No ':' and
| no '/'.

Good.

|  One possible down side is that by encouraging people to use 'http:'
|  URL based URI names for their type names, we raise the issue of "what
|  does a type URI point to". This can be addressed by explicit wording
|  in the spec saying that YAML does not require or recommend that a type
|  name URI would point to any particular form of content, even in the
|  (common) case where the type name URI happens to be a URL. Note that
|  YAML allows arbitrary type name URI forms, and many of these don't allow
|  content retrieval in the first place. Also note that 'http:' based type
|  names are unavodable anyway due to their use in XML, so this question
|  has to be answered regardless of this YAC.

Ok.  Although I think all of the yaml.org linkages should
do something like RDDL.


|  # An http based type (using XML namespaces).
|  - |
|   !http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd$p
| 
|  # All possible ways to specify the integer type.
|  - |
|   !http://yaml.org/int
|   !yaml.org/int
|   !int
| 
|  # All possible ways to specify a Perl type.
|  - |
|   !http:perl.yaml.org/type
|   !perl.yaml.org/type
|   !perl/type
| 
|  # All possible ways to specify an application specific type.
|  - |
|   !http://timesheet.clarkevans.com/meeting
|   !timesheet.clarkevans.com/meeting
| 
|  # Illegal formats
|  - |
|   !:...
|   !/...
|   !//...
| 
|  # Specifying a format.
|  - |
|   !int|hex
| 
|  # Using a prefix.
|  - |
|   --- !http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd$^html
|    - !^body
|     - !^p ]
|      This is an HTML paragraph.

Ok.

| 
| dialog: []
| votes:
|  # The current votes by the YAML core team members.
|  - !yac.vote
|   who: oren
|   what: aye
|   when: 2002-02-10
| references:
|  - http://www.yaml.org/yacs/017
| replaces:
|  - http://www.yaml.org/yacs/003
|  - http://www.yaml.org/yacs/005
|  - http://www.yaml.org/yacs/019
| replaced by: []

I'll go for this one, 19 was good, but 
this one seems simpler.  Thanks oren.

Clark

-- 
Clark C. Evans                   Axista, Inc.
http://www.axista.com            800.926.5525
XCOLLA Collaborative Project Management Software