Closed mamund closed 4 years ago
I personally like making it a property for XML DESCRIPTORS. This is more aesthetics than anything because a new tag could make the XML kind of ugly.
<alps version="1.0">
<title>Contact Profile</title>
<descriptor id="contact" type="semantic">
<title>Contact</title>
<descriptor id="item" type="safe">
<title>Item</title>
<doc>A link to an individual contact.</doc>
</descriptor>
<descriptor id="fullName" type="semantic">
<title>Full Name</title>
</descriptor>
<descriptor id="email" type="semantic">
<title>Email</title>
</descriptor>
<descriptor id="phone" type="semantic">
<title>Phone</title>
</descriptor>
</descriptor>
</alps>
I like the TITLE tag directly under ALPS, though. It would end up looking something like this.
<alps version="1.0">
<title>Contact Profile</title>
<descriptor id="contact" type="semantic" title="Contact">
<descriptor id="item" type="safe" title="Item">
<doc>A link to an individual contact.</doc>
</descriptor>
<descriptor id="fullName" type="semantic" title="Full Name" />
<descriptor id="email" type="semantic" title="Email" />
<descriptor id="phone" type="semantic" title="Phone" />
</descriptor>
</alps>
yes -- the <title>
tag is well-known in HTML, too. it can easily be treated differerently than using <doc>
in a special way, too.
i also prefer to not create overrides of existing elements for other uses.
added the TITLE element as a child of ALPS. this does not meet the need of single-string attributes for DESCRIPTOR, LINK, or DOC, tho. new issue?
follow up to #75
add TITLE element to allow naming things for humans to read (also for document generation).
and
also consider making TITLE a property for XML DESCRIPTORS: