Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
text/xml no longer XML? #790
I don’t think that
In the definition list after this anchor, there is:
And “text document” explicitly excludes
So this does not literally (in a conventional wildcard sense) match, for example,
I think we should explicitly define the wildcards for common media types, instead of listing them as mere examples.
@eriksiegel I see your point: If you want to say, that a particular step needs a text document on the input port, content-types="text/*" can be used, because it includes text/xml. And there is no way to exclude "text/xml" and "text/html", which are XML documents.
Two thoughts at the 4 April editorial call:
So, "text" could be a shortcut for "text/* -text/xml -text/html" for example.