[Data-modeling] RFCs that define a protocol

[Jeff Prucher]

I probably know even less about this than you do, but I'd suggest that
"Obsoleted by" (if the property is used) be a phylogeny pattern with a
reciprocal property "Supercedes".

Jeff

> -----Original Message-----
> From: data-modeling-bounces at freebase.com 
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of Vishal Talwar
> Sent: Monday, April 27, 2009 4:06 PM
> To: data-modeling
> Subject: [Data-modeling] RFCs that define a protocol
> 
> There is an open request for adding an "RFCs that define this 
> protocol" property to the Internet Protocol type. Since I 
> know almost nothing about the subject matter, I'd like to 
> open this up for input from everyone here. Specifically,
> 
> 1. Should this property be limited to the Internet Protocol 
> type, or can RFCs define other types of protocols?
> 
> 2. There should be a new type to model RFCs, and I'm 
> considering the following properties:
>    - Status (informational|experimental|...)
>    - Date published (/type/datetime)
>    - Published by (/people/person)
>    - Obsoleted by (rfc)
>    - Specifies protocol (internet protocol)
> 
>    Am I missing anything?
> 
> 3. Should RFCs be assigned keys that correspond to their 
> serial numbers? We could then easily generate 
> URL-template-based links to RFCs themselves, assuming the 
> IETF URLs are regular.
> 
> The original discussion took place here:
> http://www.freebase.com/discuss/threads/guid/9202a8c04000641f8
> 000000009f237f8?domain=/computer
> 
> Thanks!
> Vishal
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>