XML for Coders (XFC)

E

Erik Unger

Don't know how many other proposals like that are
circulating on the web - if anybody cares: this is mine :)

If some of you like it, i'll write a SAX parser and a converter!



?processingInstruction( text )

?xml(version="1.0")

elementName(attributeName="text" otherAttributeName='5')
{
subElementName(){} // should allow to remove empty () ?
// emptyElement{} // we also could remove empty {} and terminate with ';'
// emptyElement;
// emptyElement(attrib="");
"text"
'text: "Hello World!"'
}


// Single-line comment
/*
Multi-line comment
*/

![CDATA([ Some CDATA ])]

!DOCTYPE(greeting SYSTEM "hello.dtd")

!DOCTYPE( greeting [
!ELEMENT( greeting (#PCDATA))
])


!ENTITY(myEnt "x") // should we support entities ???

//Simple replacement for external entities:
[URI]

element(attrib="1<2")
{
"No special handling of '<>&%^'!"
}


NameSpace:element(AttributeNamespace:atrib="text"){}

html(xmlns='http://www.w3.org/TR/REC-html40')
{
head()
{
title(){"Page Title"}
}
body()
{
p(){ "Go " a(href='http://www.bouncingbytes.at'){"here"} }
}
}
 
P

Peter Hickman

It's all a bit like terse xml, except that yours is quite verbose for no good
reason that i can determine. You are just swapping one, verbose, syntax for
another.

How about this...

?text

elementName attributeName=text otherAttributeName=5
{
subElementName
"text"
}

html xmlns=http://www.w3.org/TR/REC-html40
{
head
{
title attribute='this needs to be in quotes' {"Page Title"}
}
!comment
body
{
p{ "Go " a href=http://www.bouncingbytes.at {"here"} }
}
}

I'm sure you can see the syntax and it is less 'just looks like C++/Java' that
people might find off putting. The purpose of a new version of xml is, surely,
to provide some improvement for some usage of xml rather than just another syntax.

The purpose of terse xml is just that, be terse without being obscure.
 
E

Erik Unger

Dimitre said:
This is *not* XML -- do not use "XML" in the name of your language to avoid
any confusion.

The syntax is not XML but the semantic is.
So how should i call it ?
Another Alternative Syntax for XML-like Meta Semantic (AASFXLMS) ?
But here XML is still in the name...

-Erik
 
E

Erik Unger

arachno said:
hehe. looks fancy ;)
but probably only c++-syntax supportes will like it ;)

Or Java, C# and all other {}-language coders,
which are a small minority on this planet ;)

-Erik
 
E

Erik Unger

Peter said:
It's all a bit like terse xml, except that yours is quite verbose for no
good reason that i can determine.

Many coders are used to reading such a C-like syntax!
How about this...

elementName attributeName=text otherAttributeName=5
{
subElementName
"text"
}

Looks nice too. But parentheses around attributes can help
making the syntax more clear (and easier to parse).
The purpose of terse xml is just that, be terse without being obscure.

OK. My goal is a (for humans and especially programmers) more _readable_ syntax,
not a 'better' and/or mor terse syntax.

-Erik
 
P

Patrick TJ McPhee

% The syntax is not XML but the semantic is.

??? XML has no semantics. All it is is syntax.

If you want a terser input syntax for XML, why not use SGML?
 
E

Erik Unger

Patrick said:
% The syntax is not XML but the semantic is.

??? XML has no semantics. All it is is syntax.

I know, but how should i call it ?
Meta-Syntax or, Semantic of the syntax... ;)
If you want a terser input syntax for XML, why not use SGML?

You have read the whole thread ?

and stop

-Erik
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,995
Messages
2,570,230
Members
46,819
Latest member
masterdaster

Latest Threads

Top