From: Oren Ben-K. <or...@ri...> - 2002-01-07 08:18:49
|
Brian Ingerson [mailto:in...@tt...] wrote: > > YAC#5: > > # The examples are wrong, should use > > # yaml://any/tld.domain.type names. > > This is from YAC#3.2 under http://www.yaml.org/YAC-list.html#done. > > Could someone please send me a fix for this. It's not really > my domain. Actually, what we settled on is a different YAC. Here's its formulation as YAC#19. BTW, note that using the scheme name 'type:' makes perfect sense now... but let's stick with 'yaml:' anyway :-) --- YAML:1.0 location: http://www.yaml.org/yacs/019 abstract: Uniform URI Mechanism for types owner: cce status: !yac/status state: accepted date: 2002-01-07 proposal: \ Use a uniform URI mechanism for types, not namespaces. rationale: \ Use a single mechanism for all type names. Create a top-level URI scheme yaml: as in YAC#005: make it a generic hierarchical URI for any language specific or generic data type. Use this URI scheme whenever there's no specific scheme specified. The authority is the language name or 'any' for generic types. The hiererchy is defined by the language. Unlike YAC#5, each URI stands for a single type rather than for a namespace. The | character is used as a merely syntactical device to avoid repeating a shared prefix between all types used in a given YAML tree ("data island"). There is no restriction that the prefix up to the | would designate a semantically meaningful "namespace". examples: - | The interpretation of transfer methods would be as follows: Transfer Method Type !type yaml:any/org.yaml.type !/tld.domain.based yaml:any/tld.domain.based !lang/package-and-type yaml:lang/package-and-type !scheme:whatever scheme:whatever dialog: [] votes: [] references: - http://www.yaml.org/yacs/003 - http://www.yaml.org/yacs/004 replaces: http://www.yaml.org/yacs/005 replaced by: Have fun, Oren Ben-Kiki |