OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Required attribue with a default enumerated attribute value

In article <COL119-W34A7452319DE17FB85BC62F1A40@phx.gbl> you write:

>Is it possible to make a required attribue with a default enumerated 
>attribute value.

That doesn't make sense.  How can it be required and have a default?

>At the moment I have something like this in my DTD file:
>< !ATTLIST element-name attribute-name (en1|en2|en3) "en3">
>This means that this is valid when I dont't want it to be:
>< element-name> < element-name />

Why not?  It's equivalent to <element-name attribute-name="en3"/>.
If you want the user to have to specify the attribute, mark it

<!ATTLIST element-name attribute-name (en1|en2|en3) #REQUIRED>

>Is it possible then to force the attribute-name to be present so in an XML
>Editor when the element-name is created it automatically creates this:
>< element-name attribute-name="en3"> < element-name />

It seems you want to have the attribute be required, but have an
editor default to a particular value.  XML doesn't have any way to
specify that kind of interaction with editors.  By "default value",
XML means one that's used when the user doesn't specify one, not one
that is inserted by an editor.

-- Richard
Please remember to mention me / in tapes you leave behind.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS