On Sat, Aug 22, 2009 at 2:51 AM, Ian Hickson wrote:
> On Thu, 13 Aug 2009, Kevin Benson wrote:
> > On Thu, Aug 13, 2009 at 10:10 PM, Ian Hickson wrote:
> > > On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote:
> > >>
> > >> "This specification defines an abstract language for describing
> > >> docum
On Thu, 13 Aug 2009, Kevin Benson wrote:
> On Thu, Aug 13, 2009 at 10:10 PM, Ian Hickson wrote:
> > On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote:
> >>
> >> "This specification defines an abstract language for describing
> >> documents and applications, and some APIs for interacting with
> >> i
> What term would you recommend rather than "language" that is more
> understandable than "data model" or "information model"?
>
> Would "vocabulary" be ok?
"Vocabulary" may be an an improvement over "abstract language"--I'd
need to think further about that--but I think Kevin's suggestion is
likel
On Thu, Aug 13, 2009 at 10:10 PM, Ian Hickson wrote:
> On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote:
>>
>> "This specification defines an abstract language for describing
>> documents and applications, and some APIs for interacting with in-memory
>> representations of resources that use this lan
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote:
>
> "This specification defines an abstract language for describing
> documents and applications, and some APIs for interacting with in-memory
> representations of resources that use this language."
>
> The phrase "abstract language" concerns me.
"This specification defines an abstract language for describing
documents and applications, and some APIs for interacting with
in-memory representations of resources that use this language."
The phrase "abstract language" concerns me. It's not clear to me that
a language can be abstract, nor is it
