LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  March 2010

TEI-L March 2010

Subject:

Re: on ODD def of enumerated attr vals

From:

Ian Rons <[log in to unmask]>

Reply-To:

Ian Rons <[log in to unmask]>

Date:

Mon, 1 Mar 2010 08:24:32 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (12 lines)

Syd Bauman wrote:
> Here, the ident= attribute retains its semantics ala att.identified:
> it is the canonical name of the particular <valItem> construct that
> other portions of the ODD system can use (via their key= attribute) to
> refer to it. It gets to remain restricted to an xsd:Name. (It could
> even be restricted to xsd:NCName.)

It is not clear (to me, at least) that there is any need to have a canonical
name for each <valItem> in real-world scenarios, any more than there would
be for having a [log in to unmask]  At least, absent a cogent example I would (in
my ignorance) question this.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager